Fixing Common WordPress Errors Print

These four errors cover the majority of WordPress problems, and all of them are fixable from cPanel.

White screen of death

A blank page usually means a PHP fatal error. To diagnose, add this to wp-config.php:

define('WP_DEBUG', true);
define('WP_DEBUG_LOG', true);
define('WP_DEBUG_DISPLAY', false);

Reload the page and read wp-content/debug.log. It names the exact file causing the failure — usually a plugin or theme. Rename that plugin’s folder in File Manager to disable it. Remove the debug lines when you are done.

Error establishing a database connection

• Check DB_NAME, DB_USER and DB_PASSWORD in wp-config.php against cPanel → MySQL Databases — remember the username prefix
• Confirm the user is assigned to the database with ALL PRIVILEGES
• DB_HOST should be localhost
• If the credentials are right, the database may be corrupt — repair it in phpMyAdmin, or open a ticket

500 Internal Server Error

1. Rename .htaccess to .htaccess.old, then re-save permalinks in WordPress to regenerate it.
2. Raise memory_limit to 256M under Select PHP Version.
3. Deactivate all plugins by renaming the wp-content/plugins folder, then re-enable them one at a time.
4. Switch temporarily to a default theme such as Twenty Twenty-Four.

508 Resource Limit Reached

Your account hit its entry-process or CPU ceiling. Enable caching, remove heavy plugins, block abusive bots, and consider a higher plan. See Understanding Resource Usage.

Locked out of wp-admin

Reset the password directly in phpMyAdmin: edit the row in wp_users, set user_pass and choose MD5 in the function dropdown. WordPress upgrades the hash on your next login.