Error map
net::ERR_CONTENT_LENGTH_MISMATCH Chrome DevTools: net::ERR_CONTENT_LENGTH_MISMATCH — body shorter than the Content-Length header
Browser · layer 1, On your device
Centre: this error. First ring: errors it is linked with (9). Outer ring: what those are linked with. Colours show the layer of a request each error belongs to. Click any dot to re-centre the map on it; hover to follow its connections. The centre dot opens the error page.
Directly related (9)
HTTP 411 Length Required
The server refuses a request with a body but no Content-Length header.
Chrome: This page isn’t working — example.com didn’t send any data. ERR_EMPTY_RESPONSE
The server accepted the connection but closed it without sending any HTTP response — a crash, timeout or misconfigured proxy on t…
Chrome: This page isn’t working — example.com redirected you too many times. ERR_TOO_MANY_REDIRECTS
The page keeps redirecting to itself or in a loop, so the browser gives up after about 20 redirects.
Chrome: This page isn’t working — example.com is unable to handle this request. ERR_HTTP2_PROTOCOL_ERROR
The HTTP/2 connection broke a protocol rule — a server, proxy or CDN sent an invalid or oversized frame/header, or closed the str…
Chrome DevTools: net::ERR_INCOMPLETE_CHUNKED_ENCODING 200 (OK) — response cut off midway
The server started sending a chunked response with status 200 and then stopped before the final chunk, so Chrome reports the tran…
Chrome: This page isn’t working — sent an invalid response. ERR_CONTENT_DECODING_FAILED
The response claims to be compressed (gzip/brotli) but cannot be decompressed — it was double-compressed, truncated or not compre…
Chrome: This site can’t be reached — server IP address could not be found. DNS_PROBE_FINISHED_NXDOMAIN
The DNS server answered that the domain name does not exist (NXDOMAIN) — a typo, an expired or unregistered domain, a missing DNS…
Chrome: No internet — DNS_PROBE_FINISHED_NO_INTERNET (DNS probe finished, no internet)
Chrome’s built-in DNS probe could not reach any DNS server, so the device effectively has no working internet or DNS.
Browser: This network requires you to sign in — captive portal (hotel, airport, café Wi-Fi) blocking HTTPS sites
The Wi-Fi needs a login or acceptance page first; until you complete it, secure sites fail with certificate or connection errors.
Two steps away (24)
HTTP 400 Bad Request
The server could not understand the request because its syntax, headers or body are malformed or invalid.
HTTP 413 Content Too Large (Request Entity Too Large)
The request body is bigger than the server is willing to accept — usually a file upload over the configured limit.
Refused to load the script because it violates the following Content Security Policy directive
The page’s Content-Security-Policy doesn’t allow that script, style, image or connection source.
HTTP 502 Bad Gateway
A proxy or gateway (Nginx, load balancer, CDN) got an invalid response — or no response — from the upstream server behind it.
Nginx 444 No Response (connection closed without response)
An Nginx-specific code: the server deliberately closed the connection without sending anything — a rule is dropping the request.
ERR_CONNECTION_RESET: This site can’t be reached — The connection was reset
The connection to the website was cut off mid-way — by the server, a firewall/antivirus, a VPN/proxy, or network equipment.
HTTP 301 Moved Permanently
The resource has a new permanent URL; clients and search engines should use the address in the Location header from now on.
HTTP 302 Found (Temporary Redirect)
The resource is temporarily at another URL; clients should keep using the original URL for future requests.
HTTP 303 See Other
A redirect telling the client to fetch the result from another URL with GET — used after a form POST so refreshing doesn’t resubm…
HTTP 431 Request Header Fields Too Large
The request headers — almost always cookies — exceed the server’s size limit.
HTTP 505 HTTP Version Not Supported
The server doesn’t support the HTTP protocol version used in the request.
HTTP 100 Continue
An interim response telling the client to go ahead and send the request body — normal when the client sent Expect: 100-continue.
PHP Fatal error: Maximum execution time of 30 seconds exceeded
The script ran longer than `max_execution_time` and PHP stopped it.
HTTP 406 Not Acceptable
The server can’t produce a response in any format listed in the request’s Accept headers.
Chrome: Aw, Snap! Something went wrong while displaying this webpage. Error code: STATUS_ACCESS_VIOLATION / SIGILL / Out of Memory
A Chrome tab crashed — out of memory, a faulty extension, a graphics/driver issue or a very heavy page.
HTTP 408 Request Timeout
The server closed the connection because the client took too long to send the complete request.
TypeError: Failed to fetch / NetworkError when attempting to fetch resource
The browser couldn’t complete the request at the network level — CORS, DNS, offline, blocked mixed content, or the server refused…
API Request Timed Out (ETIMEDOUT / ReadTimeout / timeout of 30000ms exceeded)
The client gave up waiting — either for the connection to open or for the response to arrive.
Error: socket hang up / read ECONNRESET
The other side closed the TCP connection abruptly while your client was still using it.
Error: getaddrinfo ENOTFOUND host / Name or service not known
DNS lookup for the hostname failed — the name is wrong, doesn’t exist, or this machine can’t resolve it.
net::ERR_BLOCKED_BY_CLIENT
A browser extension (ad blocker, privacy tool) blocked the request.
HTTP 407 Proxy Authentication Required
A proxy between you and the server requires credentials before it will forward your request.
net::ERR_CONNECTION_REFUSED (This site can't be reached — refused to connect)
The browser reached the host but nothing was listening on that port.
NET::ERR_CERT_AUTHORITY_INVALID (Your connection is not private)
The site’s certificate isn’t signed by a CA the browser trusts — self-signed, missing intermediates, or intercepted by a proxy.
Map another error
Popular: 4035004000xC000007BTypeErrorCritical error404NullPointerException