• 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.

Issue WordPress cloning attempt fails with 'mysqlcheck: Got error: 1045'

Steg

New Pleskian
Server operating system version
Ubuntu 22.04
Plesk version and microupdate number
Obsidian 18.0.50.2
I'm trying to clone a site into a new subdomain and am getting the following error:

Code:
mysqlcheck: Got error: 1045: Access denied for user 'xxxx'@'localhost' (using password: YES) when trying to connect

I wasn't able to locate any threads or KB articles on this. Anyone got any ideas?
 
I could not find anything specific on this situation, but recently there have been some threads that discussed issues when "skip-name-resolve" in /etc/my.cnf was on, because in that case "localhost" cannot be resolved to "127.0.0.1", and if the necessary permission sets in the "user" table of the database are missing for "localhost" as a name, but only refer to "127.0.0.1", access will be denied. You can test if it works by setting "skip-name-resolve = 0" and restarting the database afterwards. If it works, fine, if it does not work, revert to the previous setting.
 
Looks like the main file is actually in /etc/mysql/. However, I don't see skip-name-resolve in any of the .conf files.
 
Could you please add skip_name_resolve = off to my.cnf and restart the database? Does the issue persist?
 
Anyone got another theory?

Would it be easier if I had the client submitted an official support ticket?
 
Yes, please. It has something to do with permissions, but if it is not the host name resolution, it needs to be checked on the server what it is.
 
Back
Top