10 articles
Knowledge Base
WordPress Errors
10 articles in the WordPress Errors category.
- WordPress 404 pages — SEO impact and the fix workflow WordPress 404s do not directly hurt rankings, but the side effects do. How to find them, when to redirect vs let them 404, and what to ship for the 404 template.
- WordPress 404 troubleshooting: the deep diagnostic for missing-page errors WordPress 404s come from six different layers, each with its own fix. This walks through diagnosing a WordPress 404 from rewrite rules to CDN edge caches.
- WordPress 500 Internal Server Error: the full diagnostic chain A WordPress 500 can come from PHP, the web server, a plugin fatal, or a filesystem permission. Here is the order to diagnose a WordPress 500, layer by layer.
- WordPress 502 Bad Gateway: diagnosing the upstream failure A WordPress 502 means the web server could not get a usable response from PHP. Here is the diagnostic chain for a WordPress 502, from FPM socket to PHP segfault.
- WordPress 503 Service Unavailable: causes and full diagnostic A WordPress 503 is the polite signal that the server is too busy or in maintenance mode. Here is what triggers a WordPress 503, how to confirm, and how to clear it.
- WordPress 504 Gateway Timeout: finding the request that hung A WordPress 504 means a request took longer than the server was willing to wait. Here is the diagnostic chain for a WordPress 504, from FPM timeouts to slow database queries.
- WordPress browser console errors during page load: a diagnostic guide WordPress front-end pages often log silent console errors that break interactions. Here is how to read WordPress console errors and trace each to the plugin or theme that caused it.
- Reading WordPress error logs: Apache, Nginx, PHP-FPM, and debug.log A WordPress incident touches four separate logs. This walks through where each WordPress log lives, what shape its lines take, and the order you read them in during a real outage.
- Rebuilding WordPress from a confirmed compromise to verified-clean prod The site is compromised, the customer wants it back online. Rebuilding on the same host with the same database is the most common way to ship reinfection. Here is the ordered path that does not.
- Responding to a published CVE on an active WordPress plugin A CVE drops for a plugin you have active on 30 sites. Decision tree for patch, replace, or disable — plus the comms template that goes out before exploit POCs land.