• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Resolved After upgrade to MariaDB 10.6 (from 10.5) Backup results in error

Jürgen_T

Regular Pleskian
Server operating system version
Ubuntu 20.04.4 LTS
Plesk version and microupdate number
Plesk Obsidian v18.0.44
After upgrade from MariaDB 10.5 to 10.6 the Plesk-Backup does not get access to the DB. It shows the following error message:

Unable to make database dump. Error: Failed to exec mysqldump: Exit code: 2: WARNING: Forcing protocol to TCP due to option specification. Please explicitly state intended protocol. mysqldump: Got error: 1045: "Access denied for user 'admin'@'127.0.0.1' (using password: YES)" when trying to connect

I followed already a related post:


but without success.

Is there any idea how to solve this?
 
I found a solution but I am not sure how good it is. I checked the existig user in my DB and found admin@localhost . Obviously this should be sufficient to get access as user admin at 107.0.0.1 but it did not. So I created a 2nd user admin@107.0.0.1 - both with same passwords and now the backup works again.

If somebody has an idea for a seperate solution so I could get rid of one of the 2 admin-accounts I would be glad to hear.
 
The comment by mow finally helped. I found two entries in the jungle of all relevant conf-files for MariaDB where I only tested one with on/off i.e. without leading # and with #. Now I tested to get rid of both entries skip-name-resolve, dropped the 2nd user admin@127.0.0.1 again and ... everything works without problems.

So the issue is solved!
 
Back
Top