Error establishing a database connection

Hi Mike,
1. Assuming your version was previously working, and now is giving you this message?
2. First things to check:
a. Is the database really up? (can you check it using your host’s phpMyadmin or something?)
b. Did the database user / password / dbname change?
c. Did your wp-config.php file change (which as db user, pwd, dbname etc.)
Paul

Hi Paul…

1. Yep, everything was fine until yesterday.
2. a. Database is at least in-place. I can see it via ftp and there doesn’t appear to be a problem viewing it via hosting company website.
2. b. The password had changed, but I’ve since created a new one.
2. c. The last modification date on the wp-config.php file was May 26, and everything was fine from then until yesterday.

So, as far as I can tell, the only thing that’s different is the password for the database. I’m just wondering why, after several hours, that I’m still unable to login.

Thanks, Paul.

Mike

2. b. The password had changed, but I’ve since created a new one.

Does that password MATCH what’s in wp-config?

I try entering the password that is in wp-config and I am denied access. Then I change the password using my lame hosting company’s equally lame ‘hosting dashboard’ and try to login again using the new password, and I am still denied access.

My apologies; I may be giving confusing information, so please let me clarify:

When I attempt to login to my site’s WordPress dashboard, my browser doesn’t even display the WordPress login screen where I would enter my username and password. That’s when I get ‘Error establishing a database connection’.

However, when I attempt to manage my site’s database on my ‘hosting dashboard’ (within my hosting company’s website), a login screen is displayed but it rejects the password that matches the password in the wp-config.php file, and it also rejects new passwords I create.

So sorry for the confusion.

Bear in mind that the password should be for the SQL account. That may not (and really should not) be the same as your host’s dashboard password.

Did you make a special SQL ID for your databases?

Bear in mind that the password should be for the SQL account. That may not (and really should not) be the same as your host’s dashboard password.

I didn’t think they were the same, either. All along, my ftp client used a different password than that of my SQL account. When things went bonkers yesterday, I thought I had unwittingly screwed something up. So that’s when I began playing with the passwords, hoping to land on the right one.

HOWEVER… a friend pointed out earlier today that the whole problem might be caused by the hosting company. And, sure enough, within the last 10 minutes, the whole problem disappeared and everything seems to be back to normal. (I’ve logged in successfully three times while composing this post.)

Having read last Friday that WordPress 3.2 was about to be released, I asked my hosting company if their SQL and php apps met the requirements for WordPress 3.2 and their answer was very vague. Now I know why.

Thank you all for trying to help me. I appreciate it very much. I’m so sorry that – due to my lame hosting company – your time was wasted.

Yeah, it’s okay ?? Glad the host fixed it.