Error establishing a database connection- WORKED FINE FOR MONTHS

contact your host and verify that what is in your wp-config.php is what you need to be using.

Maybe when you get it back up, you want to upgrade, and install askimet too.

Youre behind on upgrades, and you have a lot of spam comments according to google’s cache.

I was paid to create this website, and I told the owner how to maintain it. However, she never logged in, never updated or asked how to update. I used to go in sometimes and clear the spam because I still reference it in my portfolio, and it looks bad for both of us to show off a blog filled with spam.

However, it’s been months since I have made any changes. I don’t have access to the passwords of the hosting account anymore. The owner now lives in another state, and it’s going to be a true nightmare to figure all this out. I was hoping for an easier solution- all I have access to is FTP.

I understand that it’s an older version of WordPress, but that doesn’t mean it’s okay to break itself.

I understand that it’s an older version of WordPress, but that doesn’t mean it’s okay to break itself.

Did I say that? no. I didnt even infer it.

The site doesnt work because its NOT making the mysql connection, just like the error says.

WordPress doesnt break that stuff — the host does, or the site owner does.

Like I said above,

contact your (the/whatever) host and verify that what is in your wp-config.php is what you need to be using.

I’m sorry if I sounded a little too angry there, but I am very frustrated right now. I thought I had lost all the passwords but I just found them (miraculously).

I’ve discovered that the DB_HOST name listed on GoDaddy was not the same as the one in my wp-config file, but even after I updated the wp-config file, I still get the same error. I’ve also tried using ‘localhost,’ with the same results.

See if the following video helps.

https://educhalk.org/blog/?p=148

Note: Godaddy doesn’t allow localhost in the DB_HOST, but you should be able to look at the properties of your database in the control panel to see what this value should be.

It’s got to be something has changed with the host, because I haven’t made any changes to the database name or password. I contacted GoDaddy and we’ll see what they say.

Okay, I figured it out.
Another web designer accessed the database and changed the password.
So simple, so very very simple. *kicks self*

So simple, so very very simple. *kicks self*

Glad you got it fixed. It’s nearly always the simple stuff that causes the most headache and just for future readers of this thread, it’s nearly always one of those entries in wp-config.php that causes the error connecting to database problem.