Resolved Access denied for user 'admin'@'localhost' after dist-upgrade

[Edi Duluman]

Server operating system version

Debian 11

Plesk version and microupdate number

Plesk Obsidian 18.0.65 Update #1

Hi. I have a very urgent issue. Everything went smoothly with the dist-upgrade from Debian 10 to Debian 11. Everything is now up and running, however, I can't get access to the mysql server for some reason.

I found a resolution in Plesk KB's asking me to add skip-grant-tables to [mysqld] in /etc/mysql/my.cnf which does indeed "fix" the issue by letting me at least get access to the plesk admin panel. However, a side-effect being that all databases for my sites show as "empty" ... see attached picture.



Running the folllowing command returns an error as well:

MYSQL_PWD="$(cat /etc/psa/.psa.shadow)" mysql --silent --skip-column-names -h localhost -P 3306 -u admin -e 'SELECT VERSION()'

ERROR 1698 (28000): Access denied for user 'admin'@'localhost'

I've also ran the following commands after adding skip-name-resolve to [mysqld] in /etc/mysql/my.cnf

root@agency ~ # MYSQL_PWD=$(cat /etc/psa/.psa.shadow) mysql -uadmin -h ::1
ERROR 1130 (HY000): Host '::1' is not allowed to connect to this MariaDB server

root@agency ~ # MYSQL_PWD=$(cat /etc/psa/.psa.shadow) mysql -uadmin -h 127.0.0.1
ERROR 1130 (HY000): Host '127.0.0.1' is not allowed to connect to this MariaDB server

root@agency ~ # MYSQL_PWD=$(cat /etc/psa/.psa.shadow) mysql -uadmin -h localhost
ERROR 1698 (28000): Access denied for user 'admin'@'localhost'

However, if I add skip-grant-tables the above commands obviously work, but none of the sites can connect to their specific databases as they are "not found" anymore.

Please advise ... I'm not sure what to do.

 

[Martin Dias]

Hi,

How did you do the dist upgrade?

In any case you can try:

https://support.plesk.com/hc/en-us/articles/12377966359319-Unable-to-access-Plesk-GUI-Access-denied-for-user-admin-localhost-using-password-YES

 

[Edi Duluman]

Hi. It is now fixed. I tried every resolution I could find. However, I ended up just paying for Plesk's support plan, which is just 10 USD per month and it's money well spent.

All in all, what happened was that during the upgrade guide from Debian 10 to Debian 11, as shown in step number 13, the guide does NOT state anything about any database version check, and so it basically installed MariaDB 10.5 while I had MariaDB 10.11 already installed. It overwritten the current config and so Plesk was trying to connect to this new "empty" database instead.

I spent 2 days trying to figure out what was happening, because I could see artifacts from the old database, but big shoutout to Vincent at Plesk's Technical Support, who managed to sort my mistake out.

Please pay attention to the commands Plesk offers in their Resolutions, this should NOT be there, or at least there should be a note where you need to replace the command with whatever version of the software you have.