Error Establishing a Database Connection: What It Means

"Error establishing a database connection" means WordPress loaded far enough to run, but it can't reach the database where all your posts, pages, and settings live. Think of the database as a filing cabinet and WordPress as the person who needs to open it. This error means the key doesn't work, the cabinet is jammed, or the room it's in is locked. The three real causes are wrong login credentials, a corrupted database, or the host's database server being down.

Before you change anything, make a backup of your files and database if you possibly can. Editing configuration or running a repair is safe when done right, but a backup means a mistake costs you nothing.

Check your database credentials in wp-config.php

This is the first thing to check, especially if the error appeared right after you moved hosts, cloned the site, or reset a password. WordPress stores its database login details in a file called wp-config.php in your site's root folder, reachable through your host's file manager or FTP. Four values have to match exactly what your host assigned:

• DB_NAME, the name of the database.
• DB_USER, the database username.
• DB_PASSWORD, that user's password.
• DB_HOST, usually 'localhost' but some hosts use a specific server address.

Log into your hosting control panel, find the database section (often labeled MySQL Databases), and compare each value against what's in wp-config.php. A single wrong character will break the connection. During a migration, DB_HOST is the usual culprit, because it changes between hosts. Correct any mismatch, save the file, and reload your site.

Try WordPress's built-in database repair

If the credentials are correct and the error is intermittent, or you see a message mentioning the database may be corrupt, WordPress has a repair tool built in. Add this line to wp-config.php, just above the line that says "That's all, stop editing": define('WP_ALLOW_REPAIR', true);

Then visit yoursite.com/wp-admin/maint/repair.php in your browser. You'll get a page with a repair button and a repair-and-optimize button. Run it, let it finish, then delete that line from wp-config.php right away. Leaving repair mode enabled is a security risk because anyone can access that page without logging in.

Rule out the host's database server

If your credentials are right and repair didn't help, the problem may not be your site at all. The database runs on a server, and that server can be down, overloaded, or hitting its connection limit. Two quick checks tell you: look at your host's status page for a reported incident, and, if you're technical, use your host's phpMyAdmin to try opening the database directly. If phpMyAdmin also can't connect, the server side is at fault. This is common on budget shared hosting during traffic spikes, and it often clears on its own once load drops.

When the database server is the problem, there's nothing to fix in your own files. Open a support ticket with your host, tell them phpMyAdmin can't connect either, and let them restart or move your database.

Knowing when to hand it off

Editing wp-config.php and running the repair tool are both within reach for a careful owner. But if you've confirmed the credentials, run the repair, and the error persists, or if it keeps coming back every few days, the underlying cause is deeper: a genuinely corrupt table the built-in tool can't fix, a database outgrowing its plan, or a host that keeps overloading. That's repetitive, fiddly work that's easy to make worse. If your site is also how customers reach you, the downtime cost outweighs the savings of doing it yourself. Bring in someone who can work in the database safely.

How we keep this from taking your site down

This error is one of the classic reasons a site goes dark, and it's covered under the broader category of things that break a live site that we walk through on our website problems page. On our maintenance plans, starting at $99 a month, we keep off-site backups so a corrupt database is an afternoon to restore rather than a disaster, we monitor uptime so we catch the error before your customers do, and we handle host tickets and migrations so credentials never get left mismatched. We're a Seattle-area studio and we've been fixing WordPress since 2011, so this is familiar ground.