How to Read WordPress Error Messages

Your site goes down, you check it, and instead of your homepage you see a blank white screen, or a wall of red text, or a message about the database. The instinct is panic. The reality is that WordPress error messages are usually more specific and more useful than they look — you just have to know what you’re reading.

Here’s what the common ones actually mean, and the first three things to check before you open a support ticket.

The White Screen of Death

You load your site and get nothing — a completely blank white page, no error text, no content, nothing. This is the most alarming-looking error precisely because it gives you no information at all.

What’s actually happening: a PHP fatal error occurred, but your site’s error display settings are hiding the message from view (which is the correct, secure default for a live site — you don’t want error details visible to random visitors). The error happened, WordPress stopped executing, and nothing rendered.

The first three things to check:

1. Did you just update or install a plugin or theme? This is the cause in the significant majority of white screen cases. If you updated something right before the site went white, that’s almost certainly the trigger.
2. Enable WP_DEBUG temporarily to see the actual error. In your wp-config.php file, find the line that says define('WP_DEBUG', false); and change it to define('WP_DEBUG', true);. Reload your site — you should now see the actual error message instead of a blank screen. Turn this back to false once you’re done troubleshooting — leaving debug mode on a live site exposes error details to anyone visiting.
3. If you can’t get into WordPress admin at all, rename the suspect plugin’s folder via File Manager or FTP (in wp-content/plugins/, add anything to the folder name like -disabled). WordPress will automatically deactivate a plugin whose folder it can’t find, often restoring access immediately.

“Error Establishing a Database Connection”

This means WordPress successfully started loading but couldn’t reach the database — the place where all your content, settings, and configuration actually live. Without it, WordPress has nothing to build a page from.

The first three things to check:

1. Are the database credentials in wp-config.php correct? If you recently changed a database password, migrated hosts, or restored from a backup, mismatched credentials are the most common cause.
2. Is the database server itself running? This is rare on managed hosting but worth ruling out — check your hosting status page or contact support to confirm the database service is up.
3. Is the database possibly corrupted? Less common, but a corrupted database table can produce this exact error. In cPanel, phpMyAdmin has a “Repair” function under a database’s operations that can fix minor corruption.

If none of these resolve it, this is a good candidate for opening a support ticket — database-level issues are often faster to diagnose from the server side than from WordPress’s front end.

PHP Fatal Error Messages (the Ones With Actual Text)

Sometimes instead of a white screen, you get an actual error message with red or orange text, something like:

Fatal error: Uncaught Error: Call to undefined function some_function() in /home/user/public_html/wp-content/plugins/some-plugin/file.php on line 47

This is actually good news compared to the white screen — you’re being told exactly what broke and where. Breaking down what this tells you:

• “Fatal error” — something stopped execution entirely, which is why the page failed to load.
• The specific error type (Uncaught Error, Call to undefined function, etc.) — describes the category of problem. “Undefined function” usually means a plugin is trying to call code that doesn’t exist, often because of a version mismatch or a missing dependency.
• The file path — tells you exactly which plugin or theme file caused it. In the example above, it’s a plugin called “some-plugin.”
• The line number — the exact line in that file where things broke.

The first three things to check:

1. Identify the plugin or theme from the file path — the folder name right after wp-content/plugins/ or wp-content/themes/ tells you exactly what’s responsible.
2. Check if that plugin/theme has a pending update or was recently updated. Compatibility breaks between WordPress core, PHP versions, and specific plugins are the most common source of fatal errors like this.
3. Deactivate that specific plugin (via File Manager rename if you can’t access wp-admin, or through the plugins screen if you can) and see if the site recovers. If it does, you’ve confirmed the cause — check for an updated version of the plugin, or find an alternative if it’s abandoned.

“This Site Can’t Provide a Secure Connection” or SSL-Related Errors

This isn’t a WordPress error specifically — it’s your browser refusing to connect because something is wrong with the SSL certificate. We covered SSL certificates in depth in this post, but the short version for troubleshooting: check whether your certificate has expired, and if you recently changed hosting or DNS, whether the certificate matches the domain being requested.

The General Troubleshooting Order That Applies to Almost Everything

Regardless of which specific error you’re looking at, the same sequence resolves the vast majority of WordPress problems:

1. What changed recently? An update, a new plugin, a theme customization, a hosting change — the timing almost always points at the cause.
2. Check the error message for a file path. If one is present, it tells you exactly where to look.
3. Isolate by deactivating. Turn off the suspect plugin or switch to a default theme temporarily. If the error resolves, you’ve found your culprit.

If you’ve worked through this and you’re still stuck, or you can’t access your site at all to attempt any of these steps, open a support ticket with whatever error text you saw, even if it looked like gibberish to you. That text is exactly what we need to diagnose it quickly.

The short version: A white screen means a hidden fatal error — enable WP_DEBUG to see it. A database connection error means WordPress can’t reach its database — check credentials first. A fatal error with actual text is telling you exactly which file and line broke — that’s the easiest one to fix yourself. In almost every case, the question “what changed recently” points straight at the cause.