Error map
ERR_CONTENT_DECODING_FAILED Chrome: This page isn’t working — sent an invalid response. ERR_CONTENT_DECODING_FAILED
Browser · layer 1, On your device
Centre: this error. First ring: errors it is linked with (7). 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 (7)
HTTP 406 Not Acceptable
The server can’t produce a response in any format listed in the request’s Accept headers.
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 DevTools: net::ERR_CONTENT_LENGTH_MISMATCH — body shorter than the Content-Length header
The server promised a number of bytes in `Content-Length` and sent a different number, so Chrome treats the download as corrupted.
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.
Two steps away (20)
HTTP 400 Bad Request
The server could not understand the request because its syntax, headers or body are malformed or invalid.
HTTP 403 Forbidden
The server understood the request but refuses to authorize it — you (or the server process) are not allowed to access this resour…
HTTP 415 Unsupported Media Type
The server refuses the request because the body’s Content-Type isn’t one it accepts.
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.
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.
HTTP 411 Length Required
The server refuses a request with a body but no Content-Length header.
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.
Blue Screen: MEMORY_MANAGEMENT (Stop code 0x0000001A)
Windows detected a severe memory-management error — commonly faulty RAM, unstable memory settings or a bad driver.
RangeError: Invalid array length
An array was created or resized with a negative, fractional or enormous length.
Chrome: Page Unresponsive — The following page(s) have become unresponsive. You can wait for them to become responsive or exit the page(s)
A tab is stuck in a busy loop or waiting on something heavy, so Chrome offers to wait or kill it.
Map another error
Popular: 4035004000xC000007BTypeErrorCritical error404NullPointerException