{"id":1605,"date":"2026-09-03T16:58:46","date_gmt":"2026-09-03T11:28:46","guid":{"rendered":"https:\/\/cpanelfree.com\/blog\/how-to-fix-error-establishing-database-connection-wordpress\/"},"modified":"2026-09-03T17:01:34","modified_gmt":"2026-09-03T11:31:34","slug":"how-to-fix-error-establishing-database-connection-wordpress","status":"publish","type":"post","link":"https:\/\/cpanelfree.com\/blog\/how-to-fix-error-establishing-database-connection-wordpress\/","title":{"rendered":"How to Fix Error Establishing a Database Connection in WordPress (5 Steps)"},"content":{"rendered":"
\n

\n Quick Answer:<\/strong> The “Error Establishing a Database Connection”<\/em> screen occurs when WordPress cannot communicate with its MySQL\/MariaDB database. To fix it: 1)<\/strong> Verify database credentials in wp-config.php<\/code> (DB_NAME, DB_USER, DB_PASSWORD, DB_HOST), 2)<\/strong> Verify your MySQL server daemon is active and running (sudo systemctl restart mariadb<\/code>), 3)<\/strong> Enable native WordPress repair mode (define('WP_ALLOW_REPAIR', true);<\/code>), and 4)<\/strong> Check for exhausted server memory.\n <\/p>\n<\/div>\n

What Causes the WordPress Database Connection Error?<\/h2>\n

WordPress relies entirely on PHP communicating with MySQL over TCP\/socket connections to pull site titles, post content, active theme settings, and user credentials. If authentication fails, the database daemon crashes due to memory exhaustion, or table indexes become corrupted, WordPress cannot render any HTML and serves the emergency error screen.<\/p>\n

Step 1: Check Database Credentials in wp-config.php<\/h2>\n

Open your root wp-config.php<\/code> file via cPanel File Manager or SSH and inspect the four database constants:<\/p>\n

\/\/ ** MySQL settings - You can get this info from your web host ** \/\/\ndefine( 'DB_NAME', 'cpanelfree_wpdb' );\ndefine( 'DB_USER', 'cpanelfree_wpuser' );\ndefine( 'DB_PASSWORD', 'SecurePassword123!' );\ndefine( 'DB_HOST', 'localhost' );<\/pre>\n
Common Pitfall:<\/strong> In cPanel, database and user names are prefixed with your account username (e.g. cpanelfree_dbname<\/code>). Ensure the prefix is included in wp-config.php<\/code>.<\/p>\n
Step 2: Test Database Login via Linux Terminal \/ phpMyAdmin<\/h2>\n
Test if MySQL accepts the credentials defined in wp-config.php<\/code>:<\/p>\n
mysql -u cpanelfree_wpuser -p'SecurePassword123!' -h localhost cpanelfree_wpdb<\/pre>\n
If access is denied, re-assign user permissions in cPanel under MySQL Databases > Add User to Database<\/strong> with ALL PRIVILEGES<\/em>.<\/p>\n
Step 3: Verify MySQL Server Daemon Status<\/h2>\n
On cloud VPS or dedicated servers, verify that the MySQL\/MariaDB process has not crashed due to memory exhaustion:<\/p>\n
sudo systemctl status mariadb  # or sudo systemctl status mysql\nsudo systemctl restart mariadb<\/pre>\n
Step 4: Repair Corrupted Tables with Native WordPress Repair<\/h2>\n
If the error displays “One or more database tables are unavailable”<\/em> in \/wp-admin\/<\/code>, enable WordPress repair mode by adding this line to wp-config.php<\/code> right above “That’s all, stop editing!”<\/em>:<\/p>\n
define('WP_ALLOW_REPAIR', true);<\/pre>\n
Navigate in your browser to https:\/\/yourdomain.com\/wp-admin\/maint\/repair.php<\/code> and click Repair and Optimize Database<\/strong>. (Remember to remove the line from wp-config.php once complete to prevent public access).<\/em><\/p>\n
Step 5: Check Free Disk Space and Memory Swapping<\/h2>\n
A full hard drive or exhausted RAM pool prevents MySQL from writing temporary tables or PID lock files. Check available disk space:<\/p>\n
df -h\nfree -m<\/pre>\n
\n
\n        \ud83d\udd17<\/span> Recommended Related Technical Guides:
\n    <\/h3>\n