Error map
405 405 Method Not Allowed on OPTIONS (CORS preflight)
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)
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…
Console: SecurityError: Failed to execute 'toDataURL' / 'getImageData' on 'HTMLCanvasElement': Tainted canvases may not be exported
You drew an image from another origin onto a canvas without CORS permission, so the browser blocks reading pixels back out.
Browser: Access to XMLHttpRequest at 'https://api.example.com' from origin 'http://localhost:3000' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header — Laravel
The browser blocked a cross-origin call to your Laravel API because the response lacks the right CORS headers.
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).
CORS: Private Network Access preflight blocked (public site calling localhost/intranet)
Chrome blocks a public website from reaching a private IP, localhost or intranet service without explicit permission.
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.
Set-Cookie ignored on cross-origin fetch (missing credentials / CORS credentials)
The API sends a cookie, but a cross-origin fetch/XHR doesn't store or send it.
Axios "Network Error" with no response (CORS, DNS, offline or mixed content)
Axios shows a generic Network Error and `error.response` is undefined, so there is no status code to inspect.
HEAD request returns a different status or headers than GET
Monitors and link checkers using HEAD see errors (405, 404, different length), while GET works in the browser.
CORS: Response to preflight request doesn't pass access control check: no HTTP ok status
The browser's OPTIONS preflight got an error status (401, 403, 404, 405, 500) instead of 2xx.
CORS: Request header field is not allowed by Access-Control-Allow-Headers in preflight response
Your request adds a custom header (Authorization, X-Api-Key, Content-Type: application/json) the server didn't list as allowed.
CORS: wildcard '*' not allowed when the request's credentials mode is 'include'
The server answered `Access-Control-Allow-Origin: *`, but credentialed requests (cookies, Authorization) require an exact origin.
Two steps away (31)
AWS S3: AccessDenied (403) when calling GetObject / PutObject
An IAM policy, bucket policy, ACL/ownership setting, Block Public Access or KMS key policy denied the S3 request.
HTTP 401 Unauthorized
The request has no valid authentication credentials — you need to log in or send a valid token.
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…
NotAllowedError: Failed to execute 'writeText' on 'Clipboard': Document is not focused.
The Clipboard API refused to write — the page isn’t focused, there was no user gesture, or the context isn’t secure.
Chrome DevTools: net::ERR_FAILED — a request failed with no specific reason (CORS, extension, mixed content or network)
ERR_FAILED is Chrome’s catch-all for a failed request. In DevTools it very often hides a CORS rejection, an extension, or a block…
Chrome: Aw, Snap! Something went wrong while displaying this webpage. Error code: STATUS_ACCESS_VIOLATION / SIGILL / Out of Memory
A Chrome tab crashed — out of memory, a faulty extension, a graphics/driver issue or a very heavy page.
Laravel/PHP 8: ErrorException: Attempt to read property "name" on null
You accessed a property on a value that is `null`, typically an empty relationship or a query that found nothing.
Laravel: Illuminate\Http\Exceptions\ThrottleRequestsException: Too Many Attempts. / 429 Too Many Requests
Laravel's rate limiter blocked the client for exceeding the allowed requests per minute.
Laravel Sanctum: {"message":"Unauthenticated."} 401 on API / SPA requests
A request to a `auth:sanctum` route had no valid token or session, so Laravel returned 401.
HTTP 400 Bad Request
The server could not understand the request because its syntax, headers or body are malformed or invalid.
HTTP 404 Not Found
The server can’t find anything at the requested URL.
HTTP 501 Not Implemented
The server doesn’t support the functionality (usually the HTTP method) needed to fulfil the request.
Mixed Content: The page was loaded over HTTPS, but requested an insecure resource
An HTTPS page tried to load a script, API or image over plain HTTP, and the browser blocked (or warned about) it.
Chrome: ERR_SSL_KEY_USAGE_INCOMPATIBLE — the certificate's key usage doesn't allow the negotiated cipher
The server's certificate Key Usage extension does not permit the key exchange used (typically an RSA certificate missing `keyEnci…
CORS error hides the real failure: Access-Control-Allow-Origin is missing on 4xx/5xx responses
The browser reports a CORS error, but the real problem is a server error (500, 401, 404) whose response carries no CORS headers.
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…
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.
AWS: ExpiredToken — The security token included in the request is expired
Temporary AWS credentials (STS/SSO/assumed role) have expired.
AWS: Unable to locate credentials / Could not load credentials from any providers
The AWS CLI/SDK found no credentials in any place it looks — env vars, profile files, SSO cache or an instance/task role.
AWS: SignatureDoesNotMatch / InvalidClientTokenId — the request signature we calculated does not match
AWS rejected the request signature — wrong secret key, wrong region, clock skew, or a presigned URL used differently from how it…
CORS: Redirect is not allowed for a preflight request
The server answered the OPTIONS preflight with a redirect, which browsers refuse to follow.
CORS: The 'Access-Control-Allow-Origin' header contains multiple values
The response carries the CORS header twice (or a comma-separated list), which browsers reject.
CORS responses cached for the wrong origin (missing Vary: Origin)
A cache or CDN stored a CORS response for one origin and served it to another, so some sites get blocked.
Script error. (at line 0) — cross-origin error details hidden
An error happened in a script from another origin, and the browser hid the details.
Nginx/Apache: ModSecurity: Access denied with code 403 (phase 2). Matched "Operator GE matched 5 at TX:anomaly_score"
The ModSecurity WAF (OWASP Core Rule Set) blocked the request as suspicious.
HTTP 102 Processing
An interim WebDAV response saying the server accepted a long-running request and is still working on it.
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.
UnrecognizedClientException: The security token included in the request is invalid
The access key or session token isn’t recognised — wrong/deleted key, a session token missing for temporary credentials, or a reg…
ASP.NET Core: The CORS protocol does not allow specifying a wildcard (any) origin and credentials at the same time
The CORS policy uses AllowAnyOrigin() together with AllowCredentials(), which browsers forbid.
400 Bad Request: Request Header Or Cookie Too Large
The server rejected the request because its headers, usually accumulated cookies, are bigger than it allows.
Map another error
Popular: 500400403ORA-009331064Critical errorFileNotFoundException assemblyTypeError