WordPress — Crashes & Errors
Fatal errors, white screens, memory exhaustion, and the silent failures that leave your site broken without warning.
PHP deprecation warnings after PHP 8.x upgrade — what to fix first
You upgraded WordPress to PHP 8.x. The site loads.…
Read guide →
WordPress 500 internal server error — how to find the cause in logs
You open your WordPress site and the browser shows nothing but a sterile message: > 500 Internal Server Error No stack trace. No plugin name. No clue. The admin…
Read guide →
WordPress fatal error — how to find what crashed your site
You hit your homepage and get a white screen, a generic "There has been a critical error on this website" message, or a hard HTTP 500. Admin is locked out the s…
Read guide →
WordPress memory_limit exhausted — how to detect it before it crashes the site
Your WordPress admin shows a half-rendered page.…
Read guide →
WordPress PHP fatal — the causal chain from warning, to update, to fatal
You're staring at a WordPress fatal you didn't cause. The site worked at 14:02; it's white-screened at 14:05.…
Read guide →
WordPress PHP warning spike — finding the plugin or file causing the flood
Yesterday your PHP error log was 4 MB. This morning it is 1.2 GB and still growing. You SSH in, run du -sh /var/log/php-fpm/, and watch the number tick upward i…
Read guide →
WordPress REST API broken after a plugin update — finding which endpoint regressed
Your WordPress block editor is a spinner. The Gutenberg sidebar shows "Updating failed. The response is not a valid JSON response." A user opens /wp-admin/post-…
Read guide →
WordPress white screen of death — how to debug without admin access
You load your site and there is nothing. No header, no logo, no error, no 500 page. Just a flat white rectangle in the browser. View source shows an empty body,…
Read guide →
