How to fix a 500 internal server error on your website
What a 500 error means, how to find the real cause in server logs, and step-by-step fixes for the most common triggers across WordPress and custom sites.
A calm, step-by-step guide to diagnosing and fixing a blank white WordPress page, from recovery mode and debug logs to plugins, themes and memory limits.
A blank white WordPress page usually means a PHP error stopped the page loading, most often caused by a plugin or theme conflict, an update that went wrong, a PHP version mismatch or running out of memory. Check for WordPress's recovery mode email, turn on debug logging to see the error, then disable plugins and switch themes to find the culprit. Always take a backup before changing files.
Few things are as alarming as visiting your website and seeing nothing but white. The good news: the "white screen of death" is usually fixable in minutes once you find the cause. Work through these steps in order.
Since version 5.2, WordPress detects many fatal errors and emails the site administrator a link to "recovery mode." This lets you log in with the faulty plugin or theme paused and fix it from the dashboard. Check the admin email inbox, including spam.
Edit wp-config.php (via your host's file manager or SFTP) and enable debug logging:
Reload the page, then open the debug log. The error message usually names the plugin, theme or file causing the problem. Turn debugging off again when finished.
If the error points to a plugin, or you can't see an error:
Then update, replace or remove the problem plugin, or contact its developer.
If plugins aren't the cause, the theme may be. Rename your active theme's folder in wp-content/themes. WordPress will fall back to a default theme if one is installed. If the site loads, the theme has a problem, often a recent edit to functions.php.
"Allowed memory size exhausted" errors mean PHP ran out of memory. You can raise WordPress's limit with the WP_MEMORY_LIMIT setting in wp-config.php, but your host's server limit may also need increasing. Heavy plugins are often the underlying cause, so consider replacing them.
Old plugins may break on newer PHP versions, and new plugins may require newer PHP. Check your host's control panel for the PHP version and error logs. Switching versions can help temporarily, but update code to support current, supported PHP versions.
If WordPress's debug log shows nothing, your host's error logs may. A related problem, the 500 error, often shares causes; see our guide to fixing 500 internal server errors.
Caching plugins, server caches and CDNs can keep serving a blank page after the problem is fixed. Clear them all, then check in a private browser window.
Plugins that load only in the dashboard can cause admin-only white screens. Follow the same steps. If you see a database error instead, read our guide to fixing "error establishing a database connection".
Our maintenance and support team fixes broken WordPress sites quickly and keeps them updated safely. Our CMS development team cleans up problematic plugins and themes, and our web development team can rebuild fragile sites on a more stable foundation.
Usually a PHP fatal error from a plugin or theme conflict, a failed update, a PHP version mismatch or exhausted memory.
Usually not. The content is in the database; the white screen is typically caused by code. Still, take a backup before making changes.
Yes. Use your host's file manager or SFTP to enable debugging and disable plugins or themes.
This guide is general information, not legal, tax or financial advice, and details such as prices, features and rules can change. Product and company names mentioned are trademarks of their respective owners and are used only to identify those products; UK Technology Hub is not affiliated with or endorsed by them.
Tell us about your project and get a free, fixed quote.
Get a free quoteWhat a 500 error means, how to find the real cause in server logs, and step-by-step fixes for the most common triggers across WordPress and custom sites.
What this WordPress error means and how to fix it, from checking database credentials and server status to repairing tables and handling traffic spikes.
Why redirect loops happen, how to trace them, and how to fix the common causes, from HTTPS and CDN settings to www rules and CMS URLs.