Database connection failed : DBI connect failed : Access denied for user 'user'@'localhost' (using password: YES) 1433.

Submitted by Vince42 on Tue, 07/11/2017 - 15:18 Pro Licensee

I tried to install WordPress on a new domain, which usually works like charm.

In this case the domain name either might have been too long or the "double extension" like "co.uk" gave a problem resulting in "database connection failed".

I shortened the user name, deleted the database, checked the database access ("ALL" rights from localhost) - but I am still getting the error.

This brings me to the following questions:

  • What happened?
  • Is this a known error, which I could circumvent prior to installation?
  • How can I fix my issue now?

Thank you very much in advance!

Status: 
Active

Comments

Submitted by JamieCameron on Tue, 07/11/2017 - 16:25

Is the username longer than 16 characters?

Submitted by Vince42 on Tue, 07/11/2017 - 16:30 Pro Licensee

Initially the domain name has been shortened to "longdomainname.co." and I shortened it afterwards to "longdomainname" which currently has only twelve characters.

Submitted by andreychek on Tue, 07/11/2017 - 18:55

What happens if you go in and reset the database password (in Edit Databases -> Passwords), does it work for you after that?

Submitted by JamieCameron on Wed, 07/12/2017 - 01:09

Does this still happen if you create a new test domain with a shorter name, and see if it can access MySQL?

Submitted by Vince42 on Wed, 07/12/2017 - 17:06 Pro Licensee

@andreychek: I specified a new password and afterwards the script ran through - thank you! @Jamie: The script usually runs fine on all servers.

Now: how did this hickup happen? Shouldn't the script shorten the username and make use of the already set password? Why does it fail after changing the user name to a shorter version? Why did I have to specify a new password?

Submitted by JamieCameron on Wed, 07/12/2017 - 22:58

Ok, maybe the password is the issue. Did it contain any special (non-alphanumeric) characters?

Submitted by Vince42 on Wed, 07/19/2017 - 15:57 Pro Licensee

After I set up the virtual server I did not specify anything. I just said "MySQL allowed". When running the script it somehow hung - and after setting a new user name and password manually, everything worked.

I am just wondering why the default install script was not able to cope with the long domain name and the default password.

Submitted by JamieCameron on Wed, 07/19/2017 - 19:49

Did you enter a password when creating the domain though, and if so did it contain any special characters?

Submitted by Vince42 on Thu, 07/20/2017 - 14:39 Pro Licensee

Oh, sorry, I misunderstood your question in the first place. The password was characters, numbers and an exclamation mark - nothing too exotic.

Submitted by JamieCameron on Thu, 07/20/2017 - 20:05

I wonder if there is some password character that's triggering this problem on your system, like the exclamation mark? Some versions of MySQL have problems with some password characters (notably, backslashes)

Submitted by Vince42 on Fri, 07/21/2017 - 15:02 Pro Licensee

Well, as I assigned the same password afterwards manually, I doubt that the exclamation mark could have caused the problem. Ah, well - let's close this and hope for the best with the next long domain name. ;)

Submitted by JamieCameron on Fri, 07/21/2017 - 19:20

Ok ... if you can figure out some consistent trigger for this bug (like a long domain name or password), please let us know.

Submitted by aplima on Tue, 01/09/2018 - 08:23

I had this problem with a domain. The problem was that the password had a $ in it. Changed the password, problem solved.