WordPress Database Error: 6 PROVEN Fixes That Actually Work (2026)

One moment your WordPress site is working perfectly. The next, every single visitor — including you — sees this:

“Error establishing a database connection.”

No homepage. No blog posts. No admin dashboard. Just one line of text and a completely inaccessible site.

A WordPress database error is one of the most alarming problems you can encounter — because unlike a plugin conflict or a slow page, it takes your entire site offline instantly. But here is the important thing to understand before you panic: your content is safe. Every post, page, and setting is still sitting in your database exactly where you left it. WordPress simply cannot reach it right now.

This guide covers every cause of a WordPress database error, the exact fixes in the right order, and how to make sure it never brings your site down again.

The WordPress database error message — “Error establishing a database connection” — takes the entire site offline including the wp-admin dashboard

What Is the WordPress Database Error?

Every WordPress site runs on two separate systems working together: PHP files that handle your site’s logic and templates, and a MySQL database that stores all your content — posts, pages, comments, user accounts, plugin settings, and theme options.

Every time someone visits a page on your site, WordPress runs PHP code that connects to MySQL, pulls the relevant content, and assembles it into the page the visitor sees. When that connection fails, WordPress has nothing to display. The result is a WordPress database error — a blank page with a single error message and a completely inaccessible site.

What makes a WordPress database error particularly disorienting is that it affects both your frontend and your wp-admin simultaneously. You cannot access your dashboard to troubleshoot from inside WordPress — everything has to be fixed via cPanel, File Manager, or phpMyAdmin.

Why Does the WordPress Database Error Happen?

Quick Diagnosis — Which Type Do You Have?

Fix 1: Check Your Database Credentials in wp-config.php

This is the first thing to check for any WordPress database error — and it resolves the problem in 70% of cases. Your database credentials are stored in a file called wp-config.php in your site’s root directory. If any of the four key values are wrong, WordPress cannot connect to the database.

1. Open Hostinger hPanel → File Manager → public_html
2. Find wp-config.php → right-click → Edit
3. Look for these four lines near the top of the file

cPanel File Manager → wp-config.php → these four lines contain your database credentials — wrong values here cause the WordPress database error in 70% of cases

How to Verify Your Correct Credentials

1. Go to Hostinger hPanel → MySQL Databases
2. You will see your database name, username listed there
3. Compare exactly with what is in wp-config.php — they must match character for character
4. If the password is wrong — reset it in hPanel → MySQL Databases → change password → update wp-config.php with the new password
5. Save wp-config.php → refresh your site

Hostinger hPanel → MySQL Databases — your correct database name and username are listed here. Compare them exactly with what is in wp-config.php to fix the WordPress database error.

Fix 2: Check if the Database Server Is Down

If your credentials are correct but you are still seeing the WordPress database error, the MySQL server itself may be down or overloaded. This is a hosting-side issue — nothing you can fix from within WordPress.

1. Log into Hostinger hPanel
2. Check for any maintenance notices or server status alerts on the dashboard
3. Go to hPanel → MySQL Databases → phpMyAdmin — if phpMyAdmin loads and shows your database — the server is running fine and the issue is your credentials
4. If phpMyAdmin does not load — the MySQL server is down. Contact Hostinger support immediately with your domain name
5. While waiting — check hostingstatus.com for any reported Hostinger outages

Fix 3: Repair Corrupted Database Tables

A corrupted database is the second most common cause of a WordPress database error. This happens when database tables get damaged — usually after a plugin conflict, a failed update, or a sudden server crash mid-write. WordPress has a built-in repair tool that fixes this in one click.

Method 1 — WordPress Built-in Repair Tool (Easiest)

1. Open wp-config.php via cPanel File Manager
2. Add this line before the /* That’s all, stop editing! */ comment:

1. Save the file
2. Visit this URL in your browser: https://yourdomain.com/wp-admin/maint/repair.php
3. Click Repair Database — WordPress will scan and fix all corrupted tables
4. After repair is complete — go back to wp-config.php and remove the WP_ALLOW_REPAIR line immediately
5. Refresh your site — the database error should be resolved

WordPress built-in database repair tool — visit /wp-admin/maint/repair.php after adding WP_ALLOW_REPAIR to wp-config.php — fixes corrupted tables causing the the error

Method 2 — phpMyAdmin Repair (More Control)

1. Go to hPanel → MySQL Databases → phpMyAdmin
2. Click your WordPress database name in the left sidebar
3. Click Check All to select all tables
4. In the dropdown at the bottom — select Repair table
5. Click Go — phpMyAdmin runs repair on every table
6. Refresh your site after the repair completes

phpMyAdmin → select all tables → Repair table — fixes corrupted database tables that cause the the issue message

Fix 4: Fix Too Many Database Connections

When too many visitors hit your site simultaneously — or when a plugin opens database connections without properly closing them — MySQL runs out of available connections. Every new request after that point returns a database error until connections free up.

1. Add this line to wp-config.php to enable error logging and confirm this is the cause:

1. Check /wp-content/debug.log — if you see Too many connections — this is confirmed
2. Go to Plugins → Installed Plugins — deactivate all plugins → test if the error clears
3. Reactivate plugins one by one — the plugin that causes the error to return is opening unclosed database connections
4. Contact Hostinger support to temporarily increase your MySQL connection limit if traffic spikes are the cause
5. Consider upgrading your hosting plan if your site traffic has grown — shared hosting plans have lower MySQL connection limits than Business or Cloud plans

Fix 5: Fix this error After Migration

Moving your WordPress site to a new domain or hosting provider is one of the most reliable triggers of a the error. Two things typically go wrong: the database credentials change on the new host, or the site URL stored in the database still points to the old domain.

Step 1 — Update Credentials in wp-config.php

Follow Fix 1 above — verify that the DB_NAME, DB_USER, DB_PASSWORD, and DB_HOST in wp-config.php match the new hosting environment exactly. On a new host, all four values are different from your previous host.

Step 2 — Fix Site URL in wp-config.php

If credentials are correct but the error persists, add these two lines to wp-config.php temporarily:

Replace yournewdomain.com with your actual domain. Once your site loads — go to Settings → General and update both URL fields there permanently. Then remove these two lines from wp-config.php.

Fix 6: Replace Corrupted WordPress Core Files

In rare cases — after a malware infection or a badly failed update — the WordPress core files themselves become corrupted, breaking the connection between WordPress and the database. The fix is to replace the core files with a fresh copy without touching your content.

1. Download the latest WordPress version from wordpress.org/download/
2. Unzip the downloaded file on your computer
3. Delete the wp-content folder from the unzipped files — this protects your themes, plugins, and uploads
4. Delete the wp-config.php file from the unzipped files — this protects your database credentials
5. Upload the remaining files to your public_html via cPanel File Manager → overwrite existing files when prompted
6. Refresh your site — fresh core files should resolve the this issue

How to Prevent the issues

• Daily automated backups: UpdraftPlus free tier backs up your database to Google Drive daily. A database backup is your fastest recovery option for any database error — restore takes minutes instead of hours of manual troubleshooting.
• Never edit wp-config.php without a backup: Any manual edit to wp-config.php that introduces a typo in your database credentials instantly triggers a database error. Always keep a copy of your current working wp-config.php before making any changes.
• Update plugins one at a time: Bulk plugin updates occasionally cause database table conflicts. Update one plugin at a time, testing your site after each update — the moment a database error appears, you know exactly which plugin caused it.
• Check Core Web Vitals after recovery: A database error can temporarily impact your site’s performance signals. Read Fix INP in WordPress and Fix LCP in WordPress to restore your scores after fixing the error.
• Install WP-Optimize: This free plugin cleans your database — removing post revisions, spam comments, transients, and orphaned data that accumulate over time and increase corruption risk. Run it monthly.
• Monitor database size: hPanel → MySQL Databases shows your database size. A rapidly growing database on a shared hosting plan can hit resource limits and trigger connection errors. Clean regularly and upgrade hosting if needed.

The Bottom Line

A this error is one of the most alarming WordPress problems — but it is almost always caused by one of a small number of fixable issues. Start with Fix 1: verify your database credentials in wp-config.php. This single step resolves the vast majority of the errors within minutes.

If credentials are correct, check whether the MySQL server is down, repair any corrupted tables using WordPress’s built-in repair tool, and work through the remaining fixes in order. Between these six fixes, virtually every database connection error is recoverable without data loss.

The real lesson from any database error is preparation: daily automated backups, careful plugin update practices, and regular database cleaning reduce both the frequency and the recovery time of any future database issues significantly.

Related Articles

Frequently Asked Questions