The comprehensive developer's guide to HTTP status codes, DNS issues, and platform-specific errors.
Why ErrorBase Exists
ErrorBase is built as a technical reference for developers and site owners who need accurate, structured explanations of internet errors. Every page is organized by root cause, not guesses, and follows a consistent troubleshooting framework used in real-world production environments.
Standardized messages indicating connection failures, server issues, or misconfigurations. We explain HTTP status codes, DNS failures, and platform-specific errors clearly.
How This Helps You
Every page follows a consistent structure:
Clear, plain-language explanations
Common causes (Server, Browser, Network)
Step-by-step troubleshooting guides
Who It Is For
Built for developers, sysadmins, and site owners. Whether debugging a production outage or fixing a personal site, get reliable, structured information fast.
Error Categories Explained
Organized into clearly defined categories to make navigation and troubleshooting easier. Common issues such as 502 Bad Gateway, DNS_PROBE_FINISHED_NXDOMAIN, 404 Not Found, or SSL Handshake Failed are documented with clear explanations and step-by-step fixes.
HTTP Errors
Standard server response codes (404, 502) indicating configuration or availability issues.
DNS Errors
Domain name resolution problems where a domain cannot be found or servers fail to respond.
SSL / TLS Errors
Secure connection failures due to certificate problems, expired credentials, or protocol mismatches.
Cloudflare Errors
Issues specific to Cloudflare’s network, origin server connectivity, or SSL handshakes.
Browser Errors
Client-side messages from Chrome/Firefox when connections fail, timeout, or are blocked.
Server Errors
Issues related to web server software (Apache, Nginx) caused by misconfigurations or backend failures.