Error Establishing a Database Connection in WordPress

If you see “Error establishing a database connection” in WordPress, it usually means your website can no longer properly connect to the database that stores its content, settings, users, and core site information.

It is one of the more serious WordPress problems because when the database connection fails, the site often becomes partly or fully unusable. Pages may stop loading, the admin area may be inaccessible, and from a visitor’s point of view the site can look completely broken.

For a small business website, that can mean missed enquiries, lost trust, and a website that suddenly stops doing its job.

This guide explains what the error means, the most common causes, what to check first, and when it makes sense to get help through my WordPress fixes or broader website fixes service.

What does “Error establishing a database connection” actually mean?

In simple terms, WordPress is trying to load the website, but it cannot successfully connect to the database it depends on.

The database holds things like:

• pages and posts
• theme and plugin settings
• user accounts
• site configuration
• WooCommerce products and orders
• forms and submissions
• menus, widgets, and other website data

If WordPress cannot connect to that database, it has nothing reliable to load from. That is why the site often shows a blank error message rather than a normal page.

Common signs of this problem

This issue usually appears as one of the following:

• the site shows Error establishing a database connection
• both the front end and WordPress admin stop working
• the homepage fails to load at all
• the site was working normally and then suddenly failed
• the error appeared after a hosting change, migration, update, or manual edit
• the site has had other performance or server issues recently

Sometimes the front end fails while parts of the admin still work. Sometimes everything goes down at once.

1. The database login details may be wrong

One of the most common causes is incorrect database credentials in the WordPress configuration file.

WordPress uses the wp-config.php file to connect to the database. If the database name, username, password, or host details are wrong, the connection can fail completely.

This sometimes happens after:

• moving hosting
• changing database users
• restoring a backup
• editing files manually
• cloning or migrating the site
• changing environment settings without updating WordPress properly

If even one of those details is incorrect, the database connection may break.

2. The database server may be down or overloaded

Sometimes the problem is not WordPress at all. It is the database server.

If the database server is unavailable, overloaded, restarting, or struggling under resource pressure, WordPress may not be able to connect even if the login details are correct.

This is more likely when:

• the hosting is underpowered
• the site has traffic spikes
• other websites on shared hosting are causing strain
• there are wider server issues
• the hosting provider is having a temporary outage

In that case, the site may come back on its own later, but it is still a serious issue because it points to instability.

3. The website may have corrupt database tables

Another possible cause is database corruption.

If one or more database tables become corrupted, WordPress may fail to load properly and throw a database connection error. This can happen after:

• interrupted updates
• failed restores
• hosting/server issues
• plugin conflicts
• file corruption
• database errors that were left unresolved

Sometimes WordPress gives a clearer repair-related message. Other times it just shows the general database connection error.

4. The database host setting may be wrong

This is slightly different from having the wrong database username or password.

The database host setting tells WordPress where the database actually lives. In many setups this is just localhost, but not always. Some hosting providers use a different value.

If the site has been moved, copied, restored, or manually configured, the host setting may no longer match reality.

That can cause WordPress to fail even when the rest of the credentials look correct.

5. A recent migration or website move may have broken the connection

This error often appears after a site move.

For example:

• moving from one host to another
• restoring from backup
• cloning a staging site to live
• switching domains
• changing server environments
• importing a database manually

That is because migrations involve multiple moving parts: files, databases, login credentials, paths, domain settings, and configuration details.

If even one part is missed, the site may no longer be able to connect properly.

If the problem appeared after a change like that, the timing is usually a strong clue.

6. A plugin, update, or broader site problem may have triggered it

This is not the most common cause, but it does happen.

Sometimes the database error appears alongside wider WordPress issues caused by:

• plugin conflicts
• failed updates
• broken maintenance routines
• corrupted files
• server-side PHP problems
• sites that have been patched together over time

If the problem started after a plugin or site update, it is worth checking Why WordPress Websites Break After Plugin Updates and What to Check First When a WordPress Website Breaks.

This error is sometimes one symptom of a wider site failure rather than an isolated database problem.

7. Your hosting account may have hit limits or been suspended

On lower-cost or neglected hosting setups, a site can sometimes lose database access because the account has hit resource limits or has been suspended.

That can happen due to:

• excessive usage
• overdue billing
• malware or security flags
• server account restrictions
• too many processes or database connections

The result may look like a WordPress issue, but the real cause is the hosting environment.

8. The website may have deeper server or file problems

In some cases, the database error is just the visible surface of a larger technical issue.

For example:

• damaged core files
• server configuration problems
• broken permissions
• failed updates
• incomplete restores
• multiple technical issues happening together

That is why you should avoid assuming the database is always the only problem.

If the site has also shown other symptoms such as being slow, unstable, or partially broken, it may be worth reviewing Why Your WordPress Website Is Slow and What Might Be Causing It and Why Your WordPress Website Shows a Critical Error.

What to check first

If you see Error establishing a database connection in WordPress, this is the order I would usually work through it:

1. Check whether it affects the whole site

Test both the front end and the WordPress admin area.

If both are failing, that points more strongly to a wider connection problem rather than a single page issue.

2. Ask whether anything changed recently

Think about whether the error appeared after:

• a migration
• a hosting change
• a backup restore
• a plugin update
• a server edit
• a domain or site configuration change

Recent changes often explain this type of problem.

3. Check hosting status

Look for hosting alerts, outages, suspensions, or database-related warnings.

If the server or hosting environment is the problem, WordPress itself may not be the real cause.

4. Review the database credentials in wp-config.php

Make sure the database name, username, password, and host are all correct.

This is one of the most common points of failure.

5. Check whether the database itself is reachable

If available, use your hosting panel or database management tools to confirm the database exists and is accessible.

6. Look for wider site instability

If the site has also had email issues, critical errors, performance problems, or update problems, the database error may be part of a broader technical breakdown.

7. Avoid random edits if you are unsure

This is important.

A database connection issue is not something to “poke at” without a plan. Guesswork can make the problem worse, especially if backups, credentials, or configuration files are handled badly.

Why this matters more than it seems

For many small businesses, the website is not just an online brochure.

It may handle:

• contact form enquiries
• online orders
• service information
• lead generation
• customer trust
• search visibility

If a database error takes the website offline, all of that can stop instantly.

That is why this issue matters. It is not just a technical inconvenience. It can directly affect leads, sales, and credibility.

When this is likely to be urgent

This problem should usually be treated as urgent if:

• the whole website is down
• the admin area is inaccessible
• the site generates leads or bookings
• the website is used for ecommerce
• the issue appeared after a migration or major change
• there is no recent confirmed backup
• the hosting setup already felt unstable before the error appeared

In those situations, the goal should not be to experiment. It should be to diagnose the real cause properly and restore stability.

When to get help

If you are seeing Error establishing a database connection and you are not fully confident with hosting, WordPress configuration files, and database setup, it usually makes more sense to get the issue diagnosed properly than to start guessing.

That is especially true if:

• the site is important to the business
• the error appeared after a move or update
• you are not sure whether the problem is hosting, database, or WordPress-related
• the site has had multiple issues recently
• you want the website restored without risking extra damage

If the issue is WordPress-specific, my WordPress fixes service is the best starting point. If the problem is broader and tied to hosting, configuration, or general website setup, my wider website fixes service may be more suitable.

Final thought

Seeing Error establishing a database connection in WordPress usually means the site has lost access to one of the most important parts of its setup.

Sometimes the cause is simple, like incorrect credentials. Sometimes it is hosting instability, a migration problem, database corruption, or a wider technical issue.

The important thing is not to panic, but also not to treat it lightly.

A working website depends on a reliable database connection. If that connection fails, the business impact can be far bigger than the error message makes it seem.

Fixing the root cause properly matters much more than trying random quick fixes. If you need practical help, take a look at my WordPress fixes service, check my website pricing, or get in touch.