Error map
201 HTTP 201 Created
HTTP · layer 2, Network
Centre: this error. First ring: errors it is linked with (12). 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 (12)
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 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 506 Variant Also Negotiates
The server's content-negotiation setup is circular, so it can't pick a representation.
Query string space encoded as + vs %20 (wrong values, 404 or signature mismatch)
A space appears as `+` in some places and `%20` in others, so values are decoded incorrectly or signatures don't match.
HTTP 425 Too Early
The server refuses to process a request that arrived as TLS 1.3 early data (0-RTT), because it could be replayed.
HTTP 218 This is fine (Apache)
A non-standard Apache status that some hosts use to let an error body pass through a proxy.
Both Content-Length and Transfer-Encoding headers present
A message has both framing headers, which HTTP says a sender must not do.
Response truncated: connection closed before the full body arrived
The server closed the connection early, so the client got only part of the response.
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.
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 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.
Two steps away (35)
HTTP 404 Not Found
The server can’t find anything at the requested URL.
SyntaxError: Unexpected token < in JSON at position 0
`JSON.parse()` / `response.json()` received something that isn’t JSON — very often an HTML error page.
GraphQL: Cannot query field "x" on type "Y"
The query asks for a field that doesn’t exist in the server’s schema (or isn’t available on that type).
MySQL ERROR 1062 (23000): Duplicate entry for key
An INSERT/UPDATE would create a duplicate value in a PRIMARY or UNIQUE key.
HTTP 400 Bad Request
The server could not understand the request because its syntax, headers or body are malformed or invalid.
HTTP 422 Unprocessable Content
The request is well-formed, but the data fails validation (e.g. invalid email, missing required field).
HTTP 500 Internal Server Error
The server hit an unexpected condition — usually an unhandled exception or misconfiguration in the application.
HTTP 406 Not Acceptable
The server can’t produce a response in any format listed in the request’s Accept headers.
HTTP 102 Processing
An interim WebDAV response saying the server accepted a long-running request and is still working on it.
API Error: Malformed JSON in request body (entity.parse.failed / JSON parse error)
The server couldn’t parse the request body as JSON, so it rejected the request before looking at any field.
404 because the URL is double-encoded (%2520 instead of %20)
A link contains %25 sequences, so the server looks for a file name with literal percent signs and finds nothing.
Cloudflare Error 525: SSL Handshake Failed
Cloudflare couldn’t complete a TLS handshake with your origin (SSL mode Full / Full strict).
Cloudflare Error 526: Invalid SSL Certificate
With SSL mode Full (strict), the origin’s certificate is expired, self-signed, or doesn’t match the hostname.
Chrome: This site can’t be reached — example.com unexpectedly closed the connection. ERR_CONNECTION_CLOSED
The server closed the connection before finishing the TLS handshake or sending a response — typical for HTTP/HTTPS port mix-ups,…
Apache: AH00558: apache2: Could not reliably determine the server's fully qualified domain name
A harmless startup warning: Apache has no global ServerName, so it guessed one from the host’s IP.
Apache: AH02240: Server should be SSL-aware but has no certificate configured / SSLCertificateFile: file '/etc/ssl/x.crt' does not exist or is empty
Apache cannot find the certificate or key file named in its configuration, or `SSLEngine on` is set without any certificate.
Apache: [ssl:warn] AH01909: example.com:443:0 server certificate does NOT include an ID which matches the server name
Apache's SSL virtual host name does not match any name inside the certificate it loads.
400 Bad Request: invalid character in header
A header contains a character the HTTP parser doesn't accept, such as a newline, a null byte or raw non-ASCII text.
HTTP request smuggling: Content-Length vs Transfer-Encoding mismatch
Two servers in a chain disagree about where a request ends, letting an attacker hide a second request inside the first.
Malformed chunked encoding (invalid chunk size / premature end)
The body claims to use chunked transfer encoding, but the chunk sizes or terminator are wrong.
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.
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.
Laravel: SQLSTATE[HY000] [2002] Connection refused (SQL: select * from sessions) / php_network_getaddresses: getaddrinfo failed
Laravel can't open a network connection to the database host and port from `.env`.
WebSocket connection to 'wss://x' failed
The browser couldn’t open (or keep) a WebSocket connection.
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).
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: 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…
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).
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.
Map another error
Popular: 500400403ORA-009331064Critical errorFileNotFoundException assemblyTypeError