Web Error Codes

Browse common web errors such as 404, 500, 502, DNS failures, Chrome crashes, and WordPress database connection errors.

404 Not Found

Diagnose a 404 Not Found by checking the URL, deleted files, broken routes, redirects, permalinks, and server configuration.

Find the cause of a 500 Internal Server Error by checking logs, recent deploys, plugins, PHP failures, permissions, and rollback options.

Fix Chrome Aw, Snap! crashes by isolating extensions, profile corruption, cache issues, hardware acceleration, and device-specific problems.

Diagnose a 502 Bad Gateway by checking the proxy, CDN, upstream app, PHP-FPM, timeouts, and server logs before changing DNS.

Resolve DNS_PROBE_FINISHED_NXDOMAIN by checking domain records, nameservers, resolver cache, DNS propagation, and browser/network settings.

Fix the WordPress database connection error by checking wp-config.php, database credentials, MySQL/MariaDB health, and hosting changes.

Fix a WordPress 500 error by checking plugins, themes, PHP memory, debug logs, .htaccess, permissions, and recent changes.

Fix nginx 502 errors by checking upstream health, sockets, proxypass targets, PHP-FPM, timeouts, and nginx error logs.

Troubleshoot a WordPress 502 by checking PHP-FPM, overloaded plugins, theme changes, cache/CDN layers, hosting limits, and logs.

Check a 502 Bad Gateway in Chrome by separating local browser or network symptoms from a real website-side gateway outage.