RegisterLogin
WordPress Troubleshooting

How to Fix 'Error Establishing a Database Connection' in WordPress

A complete technical guide to troubleshooting and fixing the dreaded 'Error Establishing a Database Connection' issue in WordPress.

Nextgen Support•
How to Fix 'Error Establishing a Database Connection' in WordPress

One of the most terrifying, yet incredibly common issues a WordPress site owner can face is the dreaded “Error Establishing a Database Connection” white screen. Unlike a 404 error where parts of your site might still work, this error completely takes down your entire website—both the frontend and the wp-admin dashboard.

In this comprehensive technical guide, we will break down exactly why this error occurs and walk through the step-by-step troubleshooting process to bring your WordPress site back online.

What Causes the Database Connection Error?

WordPress is written in PHP and utilizes a MySQL (or MariaDB) database to store practically everything—your posts, pages, user metadata, site options, and plugin settings. Every time a page loads, PHP executes the WordPress core files, which in turn connect to the database to fetch the necessary content.

If PHP cannot successfully authenticate and connect to the MySQL server, it throws the fatal Error Establishing a Database Connection.

This communication breakdown typically occurs due to one of three reasons:

  1. Incorrect Database Credentials in the wp-config.php file.
  2. Corrupted Database Tables.
  3. Unresponsive Database Server (MySQL service is down or overloaded).

Step 1: Verify Your wp-config.php Credentials

The absolute most common cause of this error—especially after migrating a website or changing a database password in cPanel—is mismatched credentials in the WordPress configuration file.

Connect to your server via FTP, SSH, or your host’s File Manager, and open the wp-config.php file located in the root of your WordPress installation.

Check the following four definitions:

// The name of the database for WordPress
define( 'DB_NAME', 'database_name_here' );

// MySQL database username
define( 'DB_USER', 'username_here' );

// MySQL database password
define( 'DB_PASSWORD', 'password_here' );

// MySQL hostname
define( 'DB_HOST', 'localhost' );

How to verify:

  • Log into your hosting control panel (like cPanel or Plesk).
  • Navigate to the MySQL Databases section.
  • Confirm that the DB_NAME and DB_USER precisely match what is listed.
  • Pro Tip: If you are using cPanel, database names and users are often prefixed with your cPanel username (e.g., cpaneluser_dbname).
  • Reset the database user’s password and update the DB_PASSWORD field just to be absolutely sure.
  • For DB_HOST, localhost works 99% of the time, but if you are on a specific cloud infrastructure (like AWS RDS), you may need the exact endpoint URL.

Step 2: Repair a Corrupted Database

If your credentials are correct, your database might be corrupted. A strong indicator of corruption is if you see the “Error Establishing a Database Connection” on the frontend, but when you try to access wp-admin, you see a different error, such as: “One or more database tables are unavailable. The database may need to be repaired.”

WordPress has a built-in automated repair feature. To enable it, open your wp-config.php file again and add the following line just above /* That's all, stop editing! Happy publishing. */:

define( 'WP_ALLOW_REPAIR', true );

Next, navigate to the following URL in your web browser (replace example.com with your domain):

https://example.com/wp-admin/maint/repair.php

Click the Repair Database button. Once the repair process finishes, check your site.

[!CAUTION] As soon as the repair is complete, you must remove the define('WP_ALLOW_REPAIR', true); line from your wp-config.php file. Leaving it active allows anyone to hit that URL and run database repair operations on your server without logging in.

Step 3: Check Your Database Server (MySQL Service)

If your credentials are correct and the database isn’t corrupted, the MySQL server itself might be down. This happens frequently on cheap, shared hosting environments where sudden traffic spikes consume all available RAM, causing the operating system (OOM killer) to shut down the MySQL process to save the server.

How to diagnose:

  • Can you log into phpMyAdmin from your hosting control panel? If phpMyAdmin fails to load or shows a connection timeout, your database server is down.
  • If you have SSH access to your VPS or Dedicated Server, run the following command to check the MySQL service status:
sudo systemctl status mysql
# OR for MariaDB
sudo systemctl status mariadb

If it shows as failed or inactive, restart the service:

sudo systemctl restart mysql

The Long-Term Solution

If your MySQL server is frequently crashing due to high traffic or complex database queries (like WooCommerce filtering), it means you have outgrown your current hosting resources. It is highly recommended to upgrade to a robust Virtual Private Server (VPS) or our optimized WordPress Hosting plans, which allocate dedicated CPU and RAM specifically for your database operations, ensuring maximum uptime.