Error map
EventSource EventSource keeps reconnecting (error event / server closes stream)
HTTP · layer 2, Network
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 401 Unauthorized
The request has no valid authentication credentials — you need to log in or send a valid token.
HTTP 201 Created
The request succeeded and a new resource was created, normally returned after POST or PUT.
HTTP 203 Non-Authoritative Information
The request worked, but a proxy changed the response, so the content may differ from the origin's.
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.
HTTP 202 Accepted
The server accepted the request for processing, but the work is not finished yet.
WebSocket closed with code 1006 (abnormal closure)
The WebSocket connection dropped without a proper close handshake.
HTTP 102 Processing
An interim WebDAV response saying the server accepted a long-running request and is still working on it.
Two steps away (21)
Kubernetes: ImagePullBackOff / ErrImagePull
The node can’t pull the container image — wrong name/tag, missing registry credentials, or registry unreachable.
Azure AD (Entra ID): AADSTS700016 Application not found in the directory
The client ID in your sign-in request doesn’t exist in the tenant you’re authenticating against.
HTTP 400 Bad Request
The server could not understand the request because its syntax, headers or body are malformed or invalid.
HTTP 409 Conflict
The request conflicts with the current state of the resource — e.g. a duplicate or an edit based on an outdated version.
HTTP 200 OK (but something is still wrong)
The request succeeded at the HTTP level — yet the page is blank, the data is wrong, or an error is hidden inside the response bod…
HTTP 506 Variant Also Negotiates
The server's content-negotiation setup is circular, so it can't pick a representation.
HTTP 407 Proxy Authentication Required
A proxy between you and the server requires credentials before it will forward your request.
HTTP 304 Not Modified
The cached copy is still valid, so the server sends no body and the client reuses its cache.
HTTP 417 Expectation Failed
The server or a proxy can’t meet the Expect header in the request — almost always Expect: 100-continue.
Malformed chunked encoding (invalid chunk size / premature end)
The body claims to use chunked transfer encoding, but the chunk sizes or terminator are wrong.
PROXY protocol error: broken header / unexpected data from the load balancer
A server expecting the PROXY protocol header received plain HTTP (or vice versa), so the connection is rejected.
405 Not Allowed when POSTing to a static page or file (nginx)
A form or request using POST was sent to a URL that is served as a static file, and nginx only allows GET and HEAD there.
Node.js: [UnhandledPromiseRejection] — This error originated either by throwing inside of an async function without a catch block
A promise rejected and nothing handled it; since Node 15 this crashes the process.
SyntaxError: await is only valid in async functions and the top level bodies of modules
await was used inside a function that isn’t async (or in a classic, non-module script).
AbortError: The user aborted a request. / signal is aborted without reason
A fetch was cancelled through an AbortController (or the browser cancelled it).
WebSocket connection to 'wss://x' failed
The browser couldn’t open (or keep) a WebSocket connection.
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.
HTTP 507 Insufficient Storage
The server can’t store what’s needed to complete the request — the disk, quota or mailbox is full.
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.
HTTP 103 Early Hints
An interim response that sends Link headers early so the browser can preload CSS, fonts or scripts while the server is still buil…
Map another error
Popular: 500400403ORA-009331064Critical errorFileNotFoundException assemblyTypeError