You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi there—I've been using Bitnami for my Mattermost server for years. In general, things mostly just work (thank you).
But whenever there's the smallest hitch, Bitnami docs are outdated, flawed, or simply nonexistent. The best resource for support used to be the community forum, which is now unfortunately defunct (see #133, #116 et.al.)
Today I find myself locked out of mysql on my Bitnami Mattermost install. Full access to the app itself via SSH and full access to the AWS instance it's been deployed to, yet I can't find a way to access my database.
The Bitnami docs for resetting the mysql password are either wrong, or outdated. Instructions seem to just fail without so much as an error message, which makes the issue hard to pinpoint. My install is completely standard and I practically never SSH into the server (I prefer to avoid it at all costs, that's why I'm using Bitnami), so I have strong doubts that this is an isolated case (though I might naturally be wrong).
This is not the first time I run into something like this: the community forums don't exist anymore for me to reference old posts, but I have already ran into similar issues with documentation. Back then, someone on the community forums helpfully pointed out the issue, and docs were eventually updated. To me, this kind of issues are a red flag for a developer tool, especially one with self-serve support: I don't trust Bitnami to troubleshoot issues anymore.
I hope that you'll take a look at the docs I shared above and see if anything should be fixed, for the sake of other Bitnami users in the future. Unfortunately I won't be using it anymore, and can't recommend it as a tool.
The text was updated successfully, but these errors were encountered:
I restarted mysql with /opt/bitnami/ctlscript.sh restart mysql, and could then log into the DB with mysql -u root (no password prompt) and reset my password using the following:
FLUSH PRIVILEGES;
ALTERUSER'root'@'localhost' IDENTIFIED BY 'MyNewPass';
Thank you for taking the time to report this and post your solution. I'll create a task on our side to review and improve that guide. Sorry for the inconvenience.
Describe your suggestion as much as you can
Hi there—I've been using Bitnami for my Mattermost server for years. In general, things mostly just work (thank you).
But whenever there's the smallest hitch, Bitnami docs are outdated, flawed, or simply nonexistent. The best resource for support used to be the community forum, which is now unfortunately defunct (see #133, #116 et.al.)
Today I find myself locked out of mysql on my Bitnami Mattermost install. Full access to the app itself via SSH and full access to the AWS instance it's been deployed to, yet I can't find a way to access my database.
The Bitnami docs for resetting the mysql password are either wrong, or outdated. Instructions seem to just fail without so much as an error message, which makes the issue hard to pinpoint. My install is completely standard and I practically never SSH into the server (I prefer to avoid it at all costs, that's why I'm using Bitnami), so I have strong doubts that this is an isolated case (though I might naturally be wrong).
This is not the first time I run into something like this: the community forums don't exist anymore for me to reference old posts, but I have already ran into similar issues with documentation. Back then, someone on the community forums helpfully pointed out the issue, and docs were eventually updated. To me, this kind of issues are a red flag for a developer tool, especially one with self-serve support: I don't trust Bitnami to troubleshoot issues anymore.
I hope that you'll take a look at the docs I shared above and see if anything should be fixed, for the sake of other Bitnami users in the future. Unfortunately I won't be using it anymore, and can't recommend it as a tool.
The text was updated successfully, but these errors were encountered: