Error map

Cookie Cookie expires immediately or never because of clock skew or a wrong Expires date

HTTP · layer 2, Network

Open the full error page →

Centre: this error. First ring: errors it is linked with (8). 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.

Cookie — Cookie expires immediately or never because of clock skew or a wrong Expires date (HTTP)CookieClock skew too great — Kerberos: Clock skew too great (KRB_AP_ERR_SKEW) (Authentication)Clock skew too great400 — 400 Bad Request: Request Header Or Cookie Too Large (HTTP)400Cookie — Cookie is set but not sent back (Domain, Path or Secure mismatch) (HTTP)CookieCookie — Third-party cookies blocked (embedded login, iframe or widget fails) (HTTP)CookieSet-Cookie — Cookie rejected: SameSite=None requires the Secure attribute (HTTP)Set-CookieSet-Cookie — Set-Cookie ignored on cross-origin fetch (missing credentials / CORS credentials) (HTTP)Set-CookieCORS — CORS: wildcard '*' not allowed when the request's credentials mode is 'include' (HTTP)CORSclock — Certificate error caused by a wrong device clock (NET::ERR_CERT_DATE_INVALID, "your clock is ahead/behind") (SSL / TLS)clockjwt not active — NotBeforeError: jwt not active (nbf claim in the future) (Authentication)jwt not activeinvalid two-factor code — Two-factor (TOTP) code invalid / Invalid verification code (authenticator app time drift) (Authentication)invalid two-factor …Illegal arguments: undefined, string — bcrypt error: Illegal arguments: undefined, string / data and salt arguments required / data and hash arguments required (Authentication)Illegal arguments: …400 — HTTP 400 Bad Request (HTTP)400Headers already sent — Warning: Cannot modify header information - headers already sent (PHP)Headers already sent411 — HTTP 411 Length Required (HTTP)411431 — HTTP 431 Request Header Fields Too Large (HTTP)431Python not found — Python was not found; run without arguments to install from the Microsoft Store (Python)Python not foundCookies are blocked — WordPress login: Error: Cookies are blocked or not supported by your browser. You must enable cookies to use WordPress. (WordPress)Cookies are blockedSameSite cookie blocked — This Set-Cookie was blocked because it had the "SameSite=Lax" attribute but came from a cross-site response / SameSite=None requires Secure (Authentication)SameSite cookie blo…ExpiredToken — AWS: ExpiredToken — The security token included in the request is expired (AWS)ExpiredTokenNoCredentialsError — AWS: Unable to locate credentials / Could not load credentials from any providers (AWS)NoCredentialsErrorSignatureDoesNotMatch — AWS: SignatureDoesNotMatch / InvalidClientTokenId — the request signature we calculated does not match (AWS)SignatureDoesNotMat…CORS — CORS Error: No 'Access-Control-Allow-Origin' header is present (API)CORSUnrecognizedClientException — UnrecognizedClientException: The security token included in the request is invalid (AWS)UnrecognizedClientE…CORS wildcard with credentials — ASP.NET Core: The CORS protocol does not allow specifying a wildcard (any) origin and credentials at the same time (.NET)CORS wildcard with …ERR_CERT_DATE_INVALID — NET::ERR_CERT_DATE_INVALID (certificate expired) (JavaScript)ERR_CERT_DATE_INVAL…SEC_ERROR_EXPIRED_CERTIFICATE — Firefox: Peer's Certificate has expired. Error code: SEC_ERROR_EXPIRED_CERTIFICATE (SSL / TLS)SEC_ERROR_EXPIRED_C…verify error:num=10: certificate has expired — OpenSSL: verify error:num=10:certificate has expired — notAfter=Jan 1 00:00:00 2025 GMT (SSL / TLS)verify error:num=10…

Directly related (8)

Clock skew too greatAuthentication

Kerberos: Clock skew too great (KRB_AP_ERR_SKEW)

The client’s clock differs from the domain controller’s by more than 5 minutes, so Kerberos tickets are rejected.

400HTTP

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.

CookieHTTP

Cookie is set but not sent back (Domain, Path or Secure mismatch)

The browser accepted a Set-Cookie but doesn't attach it to later requests, so login or state is lost.

CookieHTTP

Third-party cookies blocked (embedded login, iframe or widget fails)

Browsers block cookies set by another site, so embedded logins, payment frames and trackers stop working.

Set-CookieHTTP

Cookie rejected: SameSite=None requires the Secure attribute

A cookie marked SameSite=None without Secure is dropped by modern browsers.

Set-CookieHTTP

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.

CORSHTTP

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.

clockSSL / TLS

Certificate error caused by a wrong device clock (NET::ERR_CERT_DATE_INVALID, "your clock is ahead/behind")

The site's certificate is valid, but the computer's date or time is wrong, so the browser thinks it is expired or not yet valid.

Two steps away (19)

jwt not activeAuthentication

NotBeforeError: jwt not active (nbf claim in the future)

The token’s nbf (not before) time is in the future for the verifying server — usually clock skew between servers.

invalid two-factor codeAuthentication

Two-factor (TOTP) code invalid / Invalid verification code (authenticator app time drift)

The 6-digit authenticator code is rejected — usually because the phone’s or server’s clock is off, or the secret was enrolled twi…

Illegal arguments: undefined, stringAuthentication

bcrypt error: Illegal arguments: undefined, string / data and salt arguments required / data and hash arguments required

bcrypt.compare/hash received undefined — the password field or stored hash wasn’t passed.

400HTTP

HTTP 400 Bad Request

The server could not understand the request because its syntax, headers or body are malformed or invalid.

Headers already sentPHP

Warning: Cannot modify header information - headers already sent

You called `header()`, `setcookie()` or `session_start()` after output had already been sent to the browser.

411HTTP

HTTP 411 Length Required

The server refuses a request with a body but no Content-Length header.

431HTTP

HTTP 431 Request Header Fields Too Large

The request headers — almost always cookies — exceed the server’s size limit.

Python not foundPython

Python was not found; run without arguments to install from the Microsoft Store

Windows ran the Microsoft Store “App execution alias” instead of a real Python installation.

Cookies are blockedWordPress

WordPress login: Error: Cookies are blocked or not supported by your browser. You must enable cookies to use WordPress.

WordPress’s test cookie wasn’t returned on login — often a siteurl/home or domain mismatch, caching of wp-login.php, or headers a…

SameSite cookie blockedAuthentication

This Set-Cookie was blocked because it had the "SameSite=Lax" attribute but came from a cross-site response / SameSite=None requires Secure

The browser refused to store or send an auth/session cookie because of SameSite or Secure rules — so logins don’t “stick” across…

ExpiredTokenAWS

AWS: ExpiredToken — The security token included in the request is expired

Temporary AWS credentials (STS/SSO/assumed role) have expired.

NoCredentialsErrorAWS

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.

SignatureDoesNotMatchAWS

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…

CORSAPI

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…

UnrecognizedClientExceptionAWS

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…

CORS wildcard with credentials.NET

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.

ERR_CERT_DATE_INVALIDJavaScript

NET::ERR_CERT_DATE_INVALID (certificate expired)

The site’s certificate has expired (or isn’t valid yet) — or the device clock is wrong.

SEC_ERROR_EXPIRED_CERTIFICATESSL / TLS

Firefox: Peer's Certificate has expired. Error code: SEC_ERROR_EXPIRED_CERTIFICATE

Firefox found an expired certificate in the chain presented by the server.

verify error:num=10: certificate has expiredSSL / TLS

OpenSSL: verify error:num=10:certificate has expired — notAfter=Jan 1 00:00:00 2025 GMT

OpenSSL's verification found a certificate in the chain whose validity period has ended.