Submitted by bentrafford on Mon, 01/02/2012 - 16:47
When I try to install Wordpress via the script installers, it fails with this error:
Database connection failed : DBI connect failed : Access denied for user 'bentrafford'@'localhost' (using password: YES) 1360.
However, logging via the command line "mysql -u bentrafford -p" succeeds.
"bentrafford" is the domain owner, and the password for the virtual server is the same as the password I'm using at the command line to access MySQL.
I should note that I changed the MySQL password with Usermin, as it didn't reflect the domain owner password, and was breaking some PHP/MySQL code I'd written.
Help!
Status:
Closed (fixed)
Comments
Submitted by JamieCameron on Mon, 01/02/2012 - 19:07 Comment #1
If you login to Virtualmin as the domain owner and go to Edit Databases -> your database -> Manage Database, does it report problems connecting? If so, this indicates that the MySQL password for the user isn't what Virtualmin expects it to be, or what the IP-based access control has been messed up somehow..
Submitted by bentrafford on Mon, 01/02/2012 - 19:27 Comment #2
It reports no issues.
Submitted by JamieCameron on Mon, 01/02/2012 - 20:15 Comment #3
When you say you changed the MySQL password with Usermin, how did you do that exactly? This may have caused the password to get out of sync with what Virtualmin expects.
The fix would be to set the MySQL password at Edit Databases -> Passwords to what is actually working for MySQL.
Submitted by bentrafford on Mon, 01/02/2012 - 21:04 Comment #4
I don't see "Passwords" in "Edit Databases."
I changed the password with Webmin, by going to Webmin->Servers->MySQL Database Server->User Permissions->bentrafford->Password->Set To->mypassword
Submitted by andreychek on Mon, 01/02/2012 - 21:15 Comment #5
If you go into "Edit Databases", which tabs do you see?
Normally, you'd see Databases, Usernames, Passwords, Import Database, and Remote Hosts.
Submitted by bentrafford on Mon, 01/02/2012 - 21:28 Comment #6
I see the problem. I was in a subserver, which didn't show all those options. I found it at the parent server level, and it fixed my problem. Thank you!
(PS: It does seem kinda clunky to have multiple locations to change MySQL in the same management system, especially when they don't update each other. Perhaps something to consider for a future release?)