How to fix the WordPress white screen of death
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.
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 500 internal server error is a generic message meaning something went wrong on the server, without saying what. The real cause is in the server or application logs. Common triggers include faulty configuration files such as .htaccess, code errors after updates, wrong file permissions, exhausted memory, timeouts and crashed application processes. Check what changed recently, read the logs, then fix the specific error.
A 500 error is frustrating because it hides the details: the server knows what went wrong but isn't telling visitors, which is correct for security. Your job is to find the real error message and fix it.
Most 500 errors appear right after a change:
If you can identify the change, rolling it back is often the quickest fix.
The logs contain the actual error:
Look for errors at the time the 500 occurred. Messages like "PHP Fatal error," "permission denied" or "timeout" point to specific fixes.
A typo in .htaccess (Apache) or an Nginx configuration file can break the whole site. Restore a previous version, or temporarily rename .htaccess to test. On WordPress, saving permalinks regenerates a default .htaccess.
Syntax errors and fatal errors in plugins, themes or custom code. The log names the file and line. Fix the code, roll back the update or disable the plugin. For WordPress specifically, see our guide to the white screen of death, which shares many causes.
Files and folders with incorrect permissions can cause 500 errors, especially after migrations. Typical safe defaults on many Linux hosts are 644 for files and 755 for folders, but check your host's guidance. Never set permissions to 777.
Scripts running out of memory or hitting process limits fail with 500 errors. Increase limits if appropriate, but investigate heavy code or plugins.
Long-running requests, such as imports or slow external APIs, may exceed server time limits. Move heavy work to background jobs, optimise queries and add timeouts with graceful handling.
For Node.js, Python and other applications, the process may have crashed or failed to start. Check process managers and platform logs, and make sure environment variables and dependencies are present.
Applications often fail when required settings like database URLs or API keys are missing in the production environment. Check your hosting configuration.
After changing something, test in a private browser window and clear caches, including CDN caches. Check several pages and key functions such as forms and checkout.
Redirect problems can look like server errors to visitors; see our guide to fixing "too many redirects".
If only some pages fail, the problem is usually in code used by those pages: a specific template, plugin feature, form handler or API call. Compare working and failing pages, check logs for the failing URLs and test the components they share.
If errors began right after a deployment, roll back first to restore service, then investigate. Compare environment variables, dependency versions and configuration between the old and new releases. Continuous integration with automated tests catches many of these problems before they reach production.
Errors that come and go often point to resource limits, timeouts, overloaded databases or flaky external services. Monitor server resources and error rates over time, and look for patterns around traffic peaks or scheduled jobs.
Show a friendly error page that apologises, offers a way to contact you and suggests trying again shortly. Never expose technical details publicly.
Our maintenance and support team diagnoses and fixes server errors quickly. Our web development team sets up staging and safe deployments, and our web app developers add error monitoring to custom applications.
It can be either. Code and configuration changes are common causes, but server problems also happen. The logs tell you which.
Brief errors usually don't. Persistent 500 errors can cause search engines to crawl less and eventually drop pages.
Showing detailed errors publicly can reveal sensitive information. Details belong in private logs.
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 quoteA 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.
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.
What this WordPress error means and how to fix it, from checking database credentials and server status to repairing tables and handling traffic spikes.