Error map
Set-Cookie Cookie rejected: SameSite=None requires the Secure attribute
HTTP · layer 2, Network
Centre: this error. First ring: errors it is linked with (7). 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 (7)
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…
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.
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.
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-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.
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.
Cookie expires immediately or never because of clock skew or a wrong Expires date
A cookie vanishes right after login, or stays when it shouldn't, because the browser and server clocks disagree.
Two steps away (17)
AWS: ExpiredToken — The security token included in the request is expired
Temporary AWS credentials (STS/SSO/assumed role) have expired.
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 431 Request Header Fields Too Large
The request headers — almost always cookies — exceed the server’s size limit.
HTTP 400 Bad Request
The server could not understand the request because its syntax, headers or body are malformed or invalid.
Warning: Cannot modify header information - headers already sent
You called `header()`, `setcookie()` or `session_start()` after output had already been sent to the browser.
HTTP 411 Length Required
The server refuses a request with a body but no Content-Length header.
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.
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…
Console: SecurityError: Failed to read the 'localStorage' property from 'Window': Access is denied for this document
The page cannot use `localStorage` because cookies/site data are blocked, it runs in a sandboxed iframe, or the browser is in a r…
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…
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.
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.
405 Method Not Allowed on OPTIONS (CORS preflight)
The browser's CORS preflight (OPTIONS) request is rejected, so the real request never gets sent.
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.
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.
Map another error
Popular: 500400403ORA-009331064Critical errorFileNotFoundException assemblyTypeError