How to Fix the WordPress White Screen of Death (Blank Page, No Error)
Your WordPress site shows a completely blank page with no message. Find the hidden error in the logs, then rule out theme code, empty files, stale cache and opcache.
Field guides by topic
Fixes for WordPress errors: database connection problems, the critical error screen, white screens, login loops and broken updates.
Your WordPress site shows a completely blank page with no message. Find the hidden error in the logs, then rule out theme code, empty files, stale cache and opcache.
You enter the right password and land back on wp-login.php, or see “Cookies are blocked”. Trace the auth cookies, then fix URL, HTTPS proxy, cache and session problems.
Stuck on “Briefly unavailable for scheduled maintenance” or seeing “Update failed” or “Could not create directory”? Clear the update, then fix locks, ownership, disk space and downloads.
Seeing “Sorry, you are not allowed to access this page”, lost your admin role, your password, your 2FA device or tripped a security lockout? Get back in from the server, safely.
The block editor says “Updating failed” or “Publishing failed” because the REST API returned something other than JSON. Find what answered instead: a firewall, a redirect, a 404 or a PHP notice.
Google shows Japanese, pharmacy or casino pages under your domain that you never wrote. Find the cloaked spam, remove it at the source, then get the junk URLs dropped from Google.
Visitors land on a scam, dating or fake prize site, often only on mobile, only from Google or only once. Reproduce the conditional redirect, then remove it from the database, files or CDN.
Browsers show a red warning before your site loads. Confirm which blocklist flagged you, find the phishing kit or malware behind it, then get reviewed by Google and the other vendors.
You cleaned the site and the malware came back. Something survived: a backdoor, hidden admin, cron job, stolen password or unpatched plugin. Find it and prove the site is clean.
Your certificate is valid but was issued for a different name. Learn how to read the SAN list, fix www and subdomain gaps, and stop the server sending the wrong certificate.
Your certificate works but the padlock is missing or parts of the page fail to load. Find every http:// reference and fix it at the source, including builder data.
The TLS handshake fails before any certificate check. Find out whether port 443 speaks HTTP, has no certificate, or offers no shared TLS version or cipher.
Search the field manual
Or jump straight to a symptom
Press / to search from any page, Esc to close