Error map
WebSocket 1006 WebSocket closed with code 1006 (abnormal closure)
HTTP · layer 2, Network
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)
Browser: WebSocket connection to 'wss://example.com/socket' failed: Error during WebSocket handshake: Unexpected response code: 400 (nginx proxy)
Nginx isn't forwarding the `Upgrade`/`Connection` headers needed for WebSockets.
Networking: Connection works, then fails after being idle — firewall/NAT idle timeout dropped the TCP session (use keepalive)
A connection that sat idle was forgotten by a firewall or NAT device, so the next packet gets reset or vanishes.
WebSocket connection to 'wss://x' failed
The browser couldn’t open (or keep) a WebSocket connection.
HTTP 598 Network Read Timeout Error
A non-standard code some proxies use when the upstream didn't send data before the read timeout.
Server-Sent Events arrive all at once (proxy buffering / compression)
An EventSource stream shows nothing for a while, then delivers every event in a burst.
WebSocket handshake: Unexpected response code: 200 (expected 101)
The server answered the WebSocket upgrade request with a normal HTTP response instead of 101 Switching Protocols.
EventSource keeps reconnecting (error event / server closes stream)
The browser's EventSource reconnects again and again, hammering the server.
HTTP 599 Network Connect Timeout Error
A non-standard code some proxies and libraries use when they couldn't connect to the upstream in time.
504 Gateway Timeout from load balancer idle timeout (long request)
A request ran longer than the load balancer's idle timeout, so it was cut with a 504.
Two steps away (27)
HTTP 400 Bad Request
The server could not understand the request because its syntax, headers or body are malformed or invalid.
Cloudflare-branded 502 Bad Gateway / 504 Gateway Timeout ("cloudflare" footer)
A plain-looking 502/504 page with “cloudflare” at the bottom comes from Cloudflare’s network itself (or an origin response it cou…
Nginx: [error] upstream sent too big header while reading response header from upstream (502 Bad Gateway)
The backend's response headers (cookies, Set-Cookie, long headers) exceeded Nginx's proxy/fastcgi buffer size.
Cloudflare Error 1020: Access Denied
A Cloudflare firewall/WAF custom rule blocked the request — the visitor’s IP, country, user agent or request pattern matched a bl…
driver failed programming external connectivity on endpoint: iptables: No chain/target/match by that name
Docker’s iptables rules were wiped (firewalld/ufw reload, iptables flush) while Docker was running, so it can’t publish ports.
ssh: connect to host x port 22: Connection timed out
SSH packets get no reply — a firewall/security group drops them, the server is off, or the IP is wrong.
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…
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.
HTTP 407 Proxy Authentication Required
A proxy between you and the server requires credentials before it will forward your request.
HTTP 504 Gateway Timeout
A proxy or gateway waited too long for the upstream server to respond and gave up.
HTTP 511 Network Authentication Required
A captive portal (hotel, airport, office Wi-Fi) is intercepting your traffic until you log in or accept its terms.
HTTP 102 Processing
An interim WebDAV response saying the server accepted a long-running request and is still working on it.
HTTP 201 Created
The request succeeded and a new resource was created, normally returned after POST or PUT.
Malformed chunked encoding (invalid chunk size / premature end)
The body claims to use chunked transfer encoding, but the chunk sizes or terminator are wrong.
OpenSSL: error:14094410:SSL routines:ssl3_read_bytes:sslv3 alert handshake failure (SSL alert number 40)
The server aborted the handshake with alert 40 — no acceptable parameters (cipher, signature algorithm, client certificate or SNI…
OpenSSL: SSL alert number 112 — tlsv1 unrecognized name
The server did not recognise the hostname sent in SNI and rejected the handshake (or an alert/warning is logged).
Java: javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure
The server rejected the Java client's TLS offer — no shared protocol/cipher, SNI issue or a required client certificate.
HTTP 401 Unauthorized
The request has no valid authentication credentials — you need to log in or send a valid token.
HTTP 202 Accepted
The server accepted the request for processing, but the work is not finished yet.
HTTP 203 Non-Authoritative Information
The request worked, but a proxy changed the response, so the content may differ from the origin's.
Laravel: Symfony\Component\ErrorHandler\Error\FatalError: Maximum execution time of 30 seconds exceeded
A web request ran longer than PHP's `max_execution_time` and was killed.
Laravel: Symfony\Component\Process\Exception\ProcessTimedOutException: The process "npm run build" exceeded the timeout of 60 seconds
A subprocess launched via the `Process` class or `Process::run()` exceeded its allowed time.
Laravel: Illuminate\Http\Client\ConnectionException: cURL error 28: Operation timed out after 30001 milliseconds with 0 bytes received
The Laravel `Http::` client waited for a response longer than its timeout and gave up.
Cloudflare Error 524: A Timeout Occurred
Cloudflare connected to the origin, but the origin didn’t send an HTTP response within 100 seconds.
Networking: ping — Request timed out / 100% packet loss (host drops or filters ICMP)
No echo reply arrived in time: the host is down, unreachable, or simply ignores ping.
Networking: nc -vz hangs then times out — firewall silently DROPs packets (REJECT would answer "Connection refused")
A connection attempt gets no answer at all, which points to a firewall dropping the packets rather than a closed port.
Map another error
Popular: 500400403ORA-009331064Critical errorFileNotFoundException assemblyTypeError