Thank you. Our team dig more through the main.log, it looks like the database (MariaDB) password is successfully reset on each startup. Possible that when trying to authenticate, it still tries with some old password. To continue troubleshooting, you could try to manually login to MariaDB using Docker. To do this:
-
Open Docker Desktop while DevKinsta is running
-
Select devkinsta_db container and attach a shell to it (see picture below)
-
In the shell, log in with
mysql: mysql -u root -p<HERE_THE_PASSWORD_FROM_DK_UI>
- make sure there is not space after the -p -
If successful, the user should see something like the below screenshot.
-
If successful, run some command like
SHOW DATABASES
; which should provide a similar output as shown in this screenshot.
If this is unsuccessful however, that means the password on DevKinsta UI is never the one that can be used to login to the MySQL server. In such a case, what we can do is stop DK and all the containers, and try to reset the password manually. This, however, requires a quite advanced user comfortable with CLI and stuff. At this point, it is just easier to to back up your site/s and remove the containers, volumes and files and start from scratch.
To try to reset the password manually:
-
Stop the MariaDB container.
-
Start a new mariadb container on the same volume, without privileges (something like
docker run --name devkinsta_reset_mariadb_root -v devkinsta_db_data:/var/lib/mysql/ -d mariadb:10.5.5 mysqld --skip-grant-tables
). -
This is basically identical to DevKinsta’s MariaDB container, with the exception that it does not require login. So even if it prompts for user/password, any random value will work.
-
Alter the root user:
USE mysql;
FLUSH PRIVILEGES;
ALTER USER 'root'@'localhost' IDENTIFIED BY 'ENTER_THE_NEW_PASS_HERE';
FLUSH PRIVILEGES;
- Remove the temp container:
docker rm devkinsta_reset_mariadb_root -f
- Start the real DK MariaDB container.
I hope it helps!