Chromium Error Reference
1 model · 3 error codes
Browse Chromium error code collections, meanings, and related context across the current corpus.
About Chromium Error Reference
Chromium-based browsers (Google Chrome, Microsoft Edge, Brave, Vivaldi, Opera) share a common network stack that surfaces a specific set of error codes when web requests fail. These errors, prefixed with ERR_, provide detailed diagnostic information about DNS resolution, TCP connection, SSL/TLS handshake, and HTTP protocol failures.
Unlike standard HTTP status codes which are generated by a remote server, Chromium network errors occur before the HTTP response is successfully received and parsed. They represent the browser's own perspective of why a connection could not be established or completed. For example, an ERR_CONNECTION_REFUSED means the server's machine actively rejected the initial TCP connection, meaning no HTTP communication even started.
FixerCode documents 3 Chromium error codes across 1 model. Each entry explains the network phase where the failure occurred, what the browser measured, and how to differentiate client-side network issues from server-side configuration faults.
Select Your Model 1
Frequently Asked Questions
A Chromium network error (like ERR_CONNECTION_REFUSED) indicates a failure at the network transport layer before a successful HTTP response was received. It means the browser's network stack encountered a problem with DNS, TCP, TLS, or an invalid protocol state.
No. HTTP status codes (like 404 or 500) are sent by the server after a successful connection. Chromium errors (ERR_*) are generated by the browser itself when it cannot reach the server, establish a secure connection, or parse the server's response.
Any browser built on the Chromium engine will surface these exact errors. This includes Google Chrome, Microsoft Edge, Brave, Vivaldi, Opera, and Arc. Safari (WebKit) and Firefox (Gecko) have their own distinct network error codes for the same underlying network failures.