WordPress
WordPress white screen: how to troubleshoot safely
A blank WordPress page gives you almost no information in the browser, which is why the next useful place to look is the server-side error path. The goal is to find the first failing component without turning one outage into several changes at once.
Check the HTTP status and error logs
A blank page with HTTP 500 points toward a server-side application failure. Review PHP and web-server logs at the exact request time. A successful HTTP response with no content suggests a different application path than a hard server error.
Look at the last change
Plugin updates, theme changes, PHP version changes, edited code, deployments, and exhausted disk space are common starting points. If the site failed immediately after a known change, test or roll back that change before touching unrelated settings.
Disable components methodically when needed
If logs point toward a plugin or theme and the dashboard is unavailable, use a safe control-panel or filesystem method to isolate one component at a time. Keep notes so you can reverse each diagnostic change.
Do not leave debugging output exposed
Detailed errors can reveal paths, configuration, or other information to visitors. Use server logs for diagnosis and return production error display to a safe state after the incident.