The white page, or WSOD (White Screen of Death), is one of the most frustrating problems: your site displays a completely empty screen, with no error message. The server often responds with a 200 code, fooling basic monitoring tools.
This problem is usually caused by a fatal PHP error with error display disabled. Without access to logs, diagnosis becomes a guessing game. This guide shows you how to enable the necessary information.
Main Causes of WSOD
- Fatal PHP error: Syntax error, missing class, insufficient memory. PHP execution stops abruptly.
- Incompatible plugin/theme: An update broke compatibility. Very common on WordPress.
- Memory limit reached: The script exceeds configured memory_limit and is killed.
- Corrupted .htaccess: Invalid rewrite rules can cause silent errors.
Diagnosis Steps
- Enable PHP errors: Add display_errors = On and error_reporting = E_ALL in php.ini or .htaccess.
- Check logs: Check PHP error_log and Apache/Nginx logs for the exact error.
- WordPress debug mode: Enable WP_DEBUG and WP_DEBUG_LOG in wp-config.php to see errors.
Solutions
- Disable plugins: Rename the plugins folder via FTP to disable all, then reactivate one by one.
- Increase memory: Set memory_limit = 256M in php.ini or WP_MEMORY_LIMIT in wp-config.php.
- Restore .htaccess: Delete .htaccess and let WordPress regenerate it via Settings > Permalinks.
Frequently Asked Questions
Why does server return 200 if page is empty?
HTTP code is sent before PHP execution. If error occurs after, 200 is already sent but content is empty.
How to avoid WSOD after updates?
Test updates in staging first. Keep recent backups. Update regularly to avoid version jumps.
Can MoniTao detect a WSOD?
Yes, with content verification. Configure a check to verify presence of an expected element on the page.
Should I keep display_errors enabled in production?
No, it's a security risk. Use error_log to record errors to a file without displaying them to visitors.
Ready to Sleep Soundly?
Start free, no credit card required.