Error map
SSE Server-Sent Events arrive all at once (proxy buffering / compression)
HTTP · layer 2, Network
Centre: this error. First ring: errors it is linked with (10). 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 (10)
nginx: [emerg] cannot load certificate key: BIO_new_file() failed (Permission denied) / open() failed (13: Permission denied)
nginx can't read the private key or certificate file, so it refuses to start or reload.
nginx: [emerg] SSL_CTX_set_cipher_list("...") failed — invalid ssl_ciphers string
The `ssl_ciphers` value contains a cipher or syntax OpenSSL doesn't accept, so nginx won't load the config.
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.
HTTP 201 Created
The request succeeded and a new resource was created, normally returned after POST or PUT.
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.
Certbot: The requested nginx plugin does not appear to be installed (or "No installers found")
certbot can't find the nginx/apache plugin, so it can't configure the web server automatically.
Malformed chunked encoding (invalid chunk size / premature end)
The body claims to use chunked transfer encoding, but the chunk sizes or terminator are wrong.
WebSocket closed with code 1006 (abnormal closure)
The WebSocket connection dropped without a proper close handshake.
EventSource keeps reconnecting (error event / server closes stream)
The browser's EventSource reconnects again and again, hammering the server.
HTTP 102 Processing
An interim WebDAV response saying the server accepted a long-running request and is still working on it.
Two steps away (28)
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
The docker CLI can’t talk to the Docker engine — it isn’t running, or your user can’t access the socket.
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…
Windows Error 0x80070005 (E_ACCESSDENIED): Access is denied
Windows refused an operation because the account or process lacks permission — seen in Windows Update, installers, Task Scheduler…
nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
Nginx (or another server) can’t listen on the port because another process already holds it — often Apache, another Nginx, or a s…
Nginx: upstream timed out (110: Connection timed out) while reading response header from upstream
Nginx waited longer than proxy_read_timeout (60 s default) for the backend (app server, PHP-FPM) to respond, then returned 504.
Nginx: nginx: [emerg] unknown directive "x" in /etc/nginx/sites-enabled/x:12 — configuration file test failed
Nginx found a directive it doesn’t know — a typo, a missing semicolon on the previous line, a directive from a module that isn’t…
HTTP 405 Method Not Allowed
The URL exists, but it doesn’t accept the HTTP method you used (e.g. POST to a GET-only route).
Nginx: [emerg] SSL_CTX_use_PrivateKey_file("/etc/ssl/server.key") failed (SSL: error:0B080074:x509 certificate routines:X509_check_private_key:key values mismatch)
The private key does not belong to the certificate configured in the server.
Nginx: [emerg] no "ssl_certificate" is defined for the "listen ... ssl" directive in /etc/nginx/sites-enabled/default:3
A server block listens with `ssl` but has no `ssl_certificate` and `ssl_certificate_key`.
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 400 Bad Request
The server could not understand the request because its syntax, headers or body are malformed or invalid.
Intermittent 502 caused by keep-alive timeout mismatch
The proxy reuses a connection the backend has just closed, so a random request fails with 502.
Wrong client IP: app sees the proxy/load balancer IP instead of the visitor
Logs, rate limits and geo rules all show one IP (the proxy) because the real client address is in a forwarded header.
Certbot: Failed to renew certificate example.com with error — The following certs could not be renewed: /etc/letsencrypt/live/example.com/fullchain.pem (failure)
`certbot renew` failed for one or more certificates, so they will expire if you don't fix it.
Certbot: Could not automatically find a matching server block for example.com. Set the `server_name` directive to use the Nginx installer
Certbot's Nginx plugin could not find a `server` block whose `server_name` matches the domain you requested.
Nginx: [warn] "ssl_stapling" ignored, no OCSP responder URL in the certificate "/etc/ssl/cert.pem"
OCSP stapling is enabled but the certificate (or chain file) contains no OCSP responder, so nginx can't staple a response.
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…
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.
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 401 Unauthorized
The request has no valid authentication credentials — you need to log in or send a valid token.
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