chrome

Chrome Network Error Codes

Network error codes displayed by Chromium-based browsers (Chrome, Edge, Brave, etc.) when a request fails. They appear in the browser's error page and in DevTools as the net::ERR_* string.

32 codes

references source.chromium.org/chromium/chromium/src/+/main:net/base/net_error_list.h

· All codes 32 codes

ERR_ABORTED Operation aborted An operation was aborted, usually by the user. For example, the user closed the tab or navigated away before the request completed.
ERR_ADDRESS_UNREACHABLE Address unreachable The IP address is unreachable. There is no route to the host, or an intermediate router reported the destination as unreachable.
ERR_BLOCKED_BY_ADMINISTRATOR Blocked by administrator The request was blocked by a system administrator policy, enterprise management software, or parental controls.
ERR_BLOCKED_BY_CLIENT Blocked by client The request was blocked by a browser extension or content script. Ad blockers, privacy extensions, and content security policy extensions commonly trigger this error.
ERR_CERT_AUTHORITY_INVALID Certificate authority invalid The server's certificate was issued by an untrusted certificate authority. The CA is not in the browser's trust store, the certificate is self-signed, or the issuer chain is incomplete.
ERR_CERT_COMMON_NAME_INVALID Certificate common name invalid The server's certificate does not match the hostname. The Subject Alternative Names (SANs) or Common Name (CN) on the certificate do not include the requested domain.
ERR_CERT_DATE_INVALID Certificate date invalid The server's certificate has expired or is not yet valid. Check the certificate's validity period and ensure the system clock is correct.
ERR_CERT_INVALID Certificate invalid The server's certificate is malformed, has an invalid signature, or violates the X.509 standard in a way that makes it unacceptable.
ERR_CERT_REVOKED Certificate revoked The server's certificate has been revoked by the issuing certificate authority, indicating the certificate is no longer trusted.
ERR_CERTIFICATE_TRANSPARENCY_REQUIRED Certificate Transparency required The server's certificate is not logged in any Certificate Transparency log. Chrome requires CT logging for all publicly-trusted certificates issued after April 2018.
ERR_CONNECTION_ABORTED Connection aborted The connection was aborted. The connection attempt timed out waiting for the server to accept, or the connection was dropped before data transfer completed.
ERR_CONNECTION_CLOSED Connection closed The connection was closed. The server closed the TCP connection before sending a complete response.
ERR_CONNECTION_FAILED Connection failed The connection attempt failed. The network-layer connection could not be established for a reason not covered by a more specific error code.
ERR_CONNECTION_REFUSED Connection refused The server actively refused the connection. No process is listening on the target port, or a firewall is rejecting the connection with a TCP RST. Common when a local development server is not running.
ERR_CONNECTION_RESET Connection reset The connection was reset. The server sent a TCP RST packet, abruptly terminating the connection. Often caused by a server crash, firewall rule, or the server rejecting the request mid-stream.
ERR_CONNECTION_TIMED_OUT Connection timed out The connection attempt timed out. The server did not respond to the TCP SYN within the allowed time. Common when the server is overloaded, unreachable, or behind a firewall that silently drops packets.
ERR_CONTENT_DECODING_FAILED Content decoding failed Failed to decode the response body. The Content-Encoding header (e.g. gzip, br) does not match the actual encoding of the response body.
ERR_EMPTY_RESPONSE Empty response The server closed the connection without sending any data. The server accepted the TCP connection but sent no HTTP response bytes.
ERR_FAILED Generic failure A generic failure occurred. This is a catch-all error for network failures that don't have a more specific code.
ERR_HTTP2_PROTOCOL_ERROR HTTP/2 protocol error The server violated the HTTP/2 protocol. This can occur when an HTTP/2 server sends a malformed frame, an invalid stream state transition, or other protocol violations.
ERR_INTERNET_DISCONNECTED Internet disconnected The device is not connected to the internet. The network interface is down or there is no route to the internet.
ERR_INVALID_RESPONSE Invalid response The server returned an invalid or unrecognised HTTP response. The response could not be parsed as a valid HTTP message.
ERR_INVALID_URL Invalid URL The URL is malformed and cannot be parsed. Check for illegal characters, missing schemes, or other syntax errors.
ERR_NAME_NOT_RESOLVED Name not resolved The hostname could not be resolved via DNS. The domain name does not exist, the DNS server is unreachable, or the device has no network connectivity.
ERR_NETWORK_CHANGED Network changed The network configuration changed while the request was in progress. The device switched networks (e.g. Wi-Fi to cellular) or a network interface was reconfigured.
ERR_PROXY_CONNECTION_FAILED Proxy connection failed Could not connect to the configured proxy server. The proxy is unreachable or not accepting connections.
ERR_SSL_CLIENT_AUTH_CERT_NEEDED SSL client certificate needed The server requires a client certificate for mutual TLS authentication, but none was provided or selected.
ERR_SSL_PROTOCOL_ERROR SSL protocol error An SSL protocol error occurred. The TLS handshake failed due to a protocol violation, incompatible configuration between client and server, or a malformed SSL record.
ERR_SSL_VERSION_OR_CIPHER_MISMATCH SSL version or cipher mismatch The client and server could not agree on a TLS protocol version or cipher suite. The server may require a newer (or older) TLS version or a cipher not supported by the client.
ERR_TIMED_OUT Timed out An operation timed out. The server or proxy did not respond within the allowed time.
ERR_TOO_MANY_REDIRECTS Too many redirects The server sent too many redirects (Chrome's limit is 20). This usually indicates a redirect loop between two or more URLs.
ERR_TUNNEL_CONNECTION_FAILED Tunnel connection failed Failed to establish an HTTP CONNECT tunnel through a proxy server. The proxy rejected the CONNECT request or returned an error response.