Error map
417 HTTP 417 Expectation Failed
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 400 Bad Request
The server could not understand the request because its syntax, headers or body are malformed or invalid.
Chrome: No internet — There is something wrong with the proxy server. ERR_TUNNEL_CONNECTION_FAILED
Chrome asked a proxy to open a tunnel (HTTPS CONNECT) to the website and the proxy refused or could not reach it.
Upload error: File type not allowed / unsupported file type
The upload was rejected because the file’s type — extension, MIME type or actual content — isn’t on the allowed list.
Upload error: File too large (LIMIT_FILE_SIZE / file exceeds maximum upload size)
The uploaded file is larger than the limit set by the API, framework or server.
WordPress: Sorry, you are not allowed to upload this file type / Sorry, this file type is not permitted for security reasons
WordPress blocked the upload because the file extension/MIME type isn’t in its allowed list (SVG, JSON, WEBP on old versions, fon…
HTTP 411 Length Required
The server refuses a request with a body but no Content-Length header.
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…
HTTP 407 Proxy Authentication Required
A proxy between you and the server requires credentials before it will forward your request.
Upload error: checksum mismatch (BadDigest / Content-MD5 did not match / XAmzContentSHA256Mismatch)
The server computed a different checksum for the data it received than the one your client declared, so it rejected the upload as…
Cloudflare Error 1040 / 1041: Invalid request header modification
A Transform Rule tried to set or remove a request header that Cloudflare doesn’t allow to be modified, or produced an invalid val…
Cloudflare 413 Request Entity Too Large (upload over the plan limit)
The request body is larger than Cloudflare allows through the proxy — 100 MB on Free/Pro, 200 MB Business, 500 MB Enterprise defa…
Two steps away (36)
HTTP 401 Unauthorized
The request has no valid authentication credentials — you need to log in or send a valid token.
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).
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 511 Network Authentication Required
A captive portal (hotel, airport, office Wi-Fi) is intercepting your traffic until you log in or accept its terms.
ERR_CONNECTION_RESET: This site can’t be reached — The connection was reset
The connection to the website was cut off mid-way — by the server, a firewall/antivirus, a VPN/proxy, or network equipment.
Chrome: Unable to connect to the proxy server. ERR_PROXY_CONNECTION_FAILED
Chrome is configured to use a proxy but cannot connect to it — the proxy is down or the setting is wrong (often left over from a…
HTTP 415 Unsupported Media Type
The server refuses the request because the body’s Content-Type isn’t one it accepts.
WordPress: The link you followed has expired
Usually an upload (theme, plugin, media) larger than PHP’s upload/post limits — WordPress receives an empty request and shows thi…
WordPress: Sorry, you are not allowed to access this page.
Your user role lacks the capability for that admin screen — or the database table prefix / user capabilities are out of sync afte…
PHP upload error 1: The uploaded file exceeds the upload_max_filesize directive in php.ini
The uploaded file is bigger than PHP’s upload_max_filesize, so PHP discarded it.
API Error: Too many concurrent requests (concurrency limit reached)
You have more requests in flight at once than the API allows for your key — even if your requests-per-minute rate is fine.
API Error: Job / operation not found or expired (async task ID unknown)
The status URL or job ID for an asynchronous operation (export, import, render, batch) doesn’t exist any more, or never existed.
NotAllowedError: play() failed because the user didn't interact with the document first.
The browser blocked media autoplay with sound until the user interacts with the page.
S3 EntityTooLarge: Your proposed upload exceeds the maximum allowed size
A single PUT can be at most 5 GB (and presigned POST policies can set lower limits); larger files must use multipart upload.
WordPress: Unable to create directory wp-content/uploads/2026/10. Is its parent directory writable by the server?
PHP can’t write to wp-content/uploads — wrong ownership/permissions, a wrong upload path, full disk, or open_basedir restrictions.
Refused to load the script because it violates the following Content Security Policy directive
The page’s Content-Security-Policy doesn’t allow that script, style, image or connection source.
Warning: session_start(): Session cannot be started after headers have already been sent
session_start() ran after output was sent, so PHP can’t set the session cookie.
Unexpected characters at the top of the page / headers already sent by BOM
A UTF-8 byte-order mark (BOM) at the start of a PHP file is sent as output, breaking headers, JSON and images.
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…
HTTP 505 HTTP Version Not Supported
The server doesn’t support the HTTP protocol version used in the request.
HTTP 504 Gateway Timeout
A proxy or gateway waited too long for the upstream server to respond and gave up.
Cloudflare Error 524: A Timeout Occurred
Cloudflare connected to the origin, but the origin didn’t send an HTTP response within 100 seconds.
HTTP 304 Not Modified
The cached copy is still valid, so the server sends no body and the client reuses its cache.
Gradle: Could not resolve all files for configuration / Could not resolve dependency
Gradle couldn’t download a dependency — wrong coordinates/version, missing repository, offline mode, or network/proxy issues.
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…
fatal: unable to access 'https://github.com/…': Could not resolve host: github.com
DNS lookup for the Git host failed from this machine.
npm ERR! code EINTEGRITY — sha512 integrity checksum failed
A downloaded package’s hash doesn’t match the integrity value in package-lock.json — a corrupted cache, a changed tarball, or a l…
WordPress Media: “HTTP error.” when uploading images
The upload request failed on the server — memory or timeout during image processing, upload size limits, ModSecurity, or Imagick…
WordPress: Post-processing of the image failed likely because the server is busy or does not have enough resources
The image uploaded but WordPress couldn’t generate its resized versions — memory/CPU limits or Imagick problems.
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 416 Range Not Satisfiable
The client asked for a byte range (Range: bytes=…) that lies outside the file — usually a resumed download of a file that changed…
Cloudflare Error 1035 / 1036: Invalid request rewrite (invalid URI path / query string)
A Transform Rule (URL rewrite) produced an invalid path or query string.
Too many open files (EMFILE)
The process hit its file-descriptor limit — sockets, files and pipes all count.
Lambda: Request must be smaller than 6291456 bytes for the InvokeFunction operation (RequestEntityTooLargeException)
The event payload (or response) is over Lambda’s 6 MB synchronous limit (256 KB for async invocations).
Lambda: Unzipped size must be smaller than 262144000 bytes
The function code plus layers exceed Lambda’s 250 MB unzipped limit for zip deployments.
Map another error
Popular: 500403400ORA-009331064Critical errorFileNotFoundException assemblyTypeError