Common WordPress errors and how to fix them

A safe first response to WordPress errors

A WordPress error can come from PHP code, a plugin or theme conflict, the database, the web server, permissions, resource limits or an interrupted update. The safest first step is to preserve evidence rather than changing several things at once.

Before editing files or the database, take a complete backup of both. Do not delete wp-config.php or WordPress core files in an attempt to force the site back online.

1. Copy the exact error. Keep the full message, file path, line number and HTTP status if one is shown.
2. Write down what changed. Note recent plugin, theme, WordPress, PHP, DNS, hosting or code changes and roughly when the problem began.
3. Check the WordPress recovery mode email. A critical error can trigger an email to the site administrator with details about the failing component and a recovery link.
4. Check the hosting status and server logs. A 500 error or unavailable database is not always caused by WordPress itself.
5. Reverse the most recent relevant change where it is safe to do so. If a newly changed plugin is clearly involved, disable or roll back that component rather than making unrelated changes across the site.

If you need debugging information, WordPress provides WP_DEBUG and WP_DEBUG_LOG, but its own documentation recommends using debugging tools on development or staging installations. On a live site, logging should be enabled only as long as necessary and errors should not be displayed publicly.

How to use the WordPress error library

The library below groups errors by the part of WordPress they affect, including critical and fatal errors, database problems, server and hosting faults, login issues, updates, plugins, PHP code, media uploads and email.

Choose the error that most closely matches the wording on your screen or in the server log. Each entry explains what the message means, the common causes, sensible checks and the point at which further investigation is safer than trial and error.

If you have a long PHP error or do not recognise the message, use the free WordPress error finder above the relevant tool page. File paths are particularly useful. For example, an error containing wp-content/plugins/plugin-name/ gives you a specific plugin to investigate, while a path inside wp-content/themes points towards theme code.

Treat that path as evidence, not a verdict. PHP reports where execution failed, but the underlying trigger might be another plugin, an incompatible PHP version, exhausted memory or unexpected data passed from elsewhere in the site.

For a site that remains unavailable after basic checks, see our emergency website fix information. For recurring maintenance and technical issues, see WordPress support.