Error map

EventSource EventSource keeps reconnecting (error event / server closes stream)

HTTP · layer 2, Network

Open the full error page →

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.

EventSource — EventSource keeps reconnecting (error event / server closes stream) (HTTP)EventSource401 — HTTP 401 Unauthorized (HTTP)401201 — HTTP 201 Created (HTTP)201203 — HTTP 203 Non-Authoritative Information (HTTP)203SSE — Server-Sent Events arrive all at once (proxy buffering / compression) (HTTP)SSE202 — HTTP 202 Accepted (HTTP)202WebSocket 1006 — WebSocket closed with code 1006 (abnormal closure) (HTTP)WebSocket 1006102 — HTTP 102 Processing (HTTP)102ImagePullBackOff — Kubernetes: ImagePullBackOff / ErrImagePull (Kubernetes)ImagePullBackOffAADSTS700016 — Azure AD (Entra ID): AADSTS700016 Application not found in the directory (Azure)AADSTS700016400 — HTTP 400 Bad Request (HTTP)400409 — HTTP 409 Conflict (HTTP)409200 — HTTP 200 OK (but something is still wrong) (HTTP)200506 — HTTP 506 Variant Also Negotiates (HTTP)506407 — HTTP 407 Proxy Authentication Required (HTTP)407304 — HTTP 304 Not Modified (HTTP)304417 — HTTP 417 Expectation Failed (HTTP)417chunked — Malformed chunked encoding (invalid chunk size / premature end) (HTTP)chunkedPROXY protocol — PROXY protocol error: broken header / unexpected data from the load balancer (HTTP)PROXY protocol405 — 405 Not Allowed when POSTing to a static page or file (nginx) (HTTP)405UnhandledPromiseRejection — Node.js: [UnhandledPromiseRejection] — This error originated either by throwing inside of an async function without a catch block (Node.js)UnhandledPromiseRej…await outside async — SyntaxError: await is only valid in async functions and the top level bodies of modules (JavaScript)await outside asyncAbortError — AbortError: The user aborted a request. / signal is aborted without reason (JavaScript)AbortErrorWebSocket failed — WebSocket connection to 'wss://x' failed (JavaScript)WebSocket failedWebSocket connection failed through Nginx (missing Upgrade headers) — Browser: WebSocket connection to 'wss://example.com/socket' failed: Error during WebSocket handshake: Unexpected response code: 400 (nginx proxy) (Nginx / Apache)WebSocket connectio…Idle connections silently dropped by firewall/NAT — Networking: Connection works, then fails after being idle — firewall/NAT idle timeout dropped the TCP session (use keepalive) (Networking)Idle connections si…507 — HTTP 507 Insufficient Storage (HTTP)507100 — HTTP 100 Continue (HTTP)100103 — HTTP 103 Early Hints (HTTP)103

Directly related (7)

Two steps away (21)

ImagePullBackOffKubernetes

Kubernetes: ImagePullBackOff / ErrImagePull

The node can’t pull the container image — wrong name/tag, missing registry credentials, or registry unreachable.

AADSTS700016Azure

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.

400HTTP

HTTP 400 Bad Request

The server could not understand the request because its syntax, headers or body are malformed or invalid.

409HTTP

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.

200HTTP

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…

506HTTP

HTTP 506 Variant Also Negotiates

The server's content-negotiation setup is circular, so it can't pick a representation.

407HTTP

HTTP 407 Proxy Authentication Required

A proxy between you and the server requires credentials before it will forward your request.

304HTTP

HTTP 304 Not Modified

The cached copy is still valid, so the server sends no body and the client reuses its cache.

417HTTP

HTTP 417 Expectation Failed

The server or a proxy can’t meet the Expect header in the request — almost always Expect: 100-continue.

chunkedHTTP

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 protocolHTTP

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.

405HTTP

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.

UnhandledPromiseRejectionNode.js

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.

await outside asyncJavaScript

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).

AbortErrorJavaScript

AbortError: The user aborted a request. / signal is aborted without reason

A fetch was cancelled through an AbortController (or the browser cancelled it).

WebSocket failedJavaScript

WebSocket connection to 'wss://x' failed

The browser couldn’t open (or keep) a WebSocket connection.

WebSocket connection failed through Nginx (missing Upgrade headers)Nginx / Apache

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.

Idle connections silently dropped by firewall/NATNetworking

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.

507HTTP

HTTP 507 Insufficient Storage

The server can’t store what’s needed to complete the request — the disk, quota or mailbox is full.

100HTTP

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.

103HTTP

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…