Error map
102 HTTP 102 Processing
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 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…
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 423 Locked
The resource is locked, so the change was refused — common with WebDAV files and some APIs that lock records during processing.
HTTP 424 Failed Dependency
The request failed because another action it depended on failed — part of a WebDAV multi-step operation or a batch.
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.
Two steps away (36)
HTTP 504 Gateway Timeout
A proxy or gateway waited too long for the upstream server to respond and gave up.
Warning: Cannot modify header information - headers already sent
You called `header()`, `setcookie()` or `session_start()` after output had already been sent to the browser.
CORS Error: No 'Access-Control-Allow-Origin' header is present
The browser blocked a cross-origin request because the server’s response didn’t include the CORS headers allowing your site’s ori…
no space left on device (Docker / Linux)
The disk (or inode table) is full — Docker images, build cache, logs and volumes are common culprits.
HTTP 413 Content Too Large (Request Entity Too Large)
The request body is bigger than the server is willing to accept — usually a file upload over the configured limit.
HTTP 429 Too Many Requests
You’ve hit a rate limit — too many requests in a given time window. Slow down and retry later.
HTTP 411 Length Required
The server refuses a request with a body but no Content-Length header.
HTTP 505 HTTP Version Not Supported
The server doesn’t support the HTTP protocol version used in the request.
HTTP 428 Precondition Required
The server requires a conditional request (If-Match / If-Unmodified-Since) to prevent lost updates, and you didn’t send one.
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…
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.
API Error: Resource already exists (ALREADY_EXISTS / resource_already_exists / 409)
The create request was refused because an object with the same unique identity — name, email, external ID — already exists.
HTTP 422 Unprocessable Content
The request is well-formed, but the data fails validation (e.g. invalid email, missing required field).
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 207 Multi-Status
A WebDAV response that carries several independent status codes in one XML body.
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 201 Created
The request succeeded and a new resource was created, normally returned after POST or PUT.
HTTP 400 Bad Request
The server could not understand the request because its syntax, headers or body are malformed or invalid.
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.
HTTP 202 Accepted
The server accepted the request for processing, but the work is not finished yet.
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.
HTTP 203 Non-Authoritative Information
The request worked, but a proxy changed the response, so the content may differ from the origin's.
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.
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).
Map another error
Popular: 500400403ORA-009331064Critical errorFileNotFoundException assemblyTypeError