Error map
Cache-Control CDN not caching: Cache-Control private / no-cache / Set-Cookie on the response
HTTP · layer 2, Network
Centre: this error. First ring: errors it is linked with (11). 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 (11)
Cloudflare Error 520: Web Server Returned an Unknown Error
Cloudflare connected to your origin, but the origin returned an empty, unknown or invalid response.
CloudFront: 403 ERROR — The request could not be satisfied
CloudFront refused or couldn’t serve the request — wrong alternate domain/certificate, blocked by origin access settings, a WAF/g…
Cloudflare not caching: cf-cache-status DYNAMIC / BYPASS / MISS every time
Cloudflare isn’t caching the response — HTML isn’t cached by default, and cookies or Cache-Control headers from the origin preven…
Networking: DNS changed but the domain still resolves to the old IP — TTL and resolver caching ("propagation")
You updated a DNS record, but resolvers and devices keep serving the old answer until its TTL expires.
Cloud CDN not caching: cache misses because of Set-Cookie, Cache-Control or missing cache mode
Responses keep missing the CDN cache, so every request reaches the origin.
404 on JS/CSS assets after a new deploy
The page loads old HTML that points to hashed asset files the new deploy removed.
CDN or browser serving stale content after a deploy
Users still see the old CSS, JS or HTML after you released a new version.
Conditional requests always return 200 (ETag/Last-Modified never matches)
The client sends If-None-Match or If-Modified-Since, but the server never answers 304, so the full body is re-downloaded every ti…
Cache hit rate collapses: Vary: Cookie or Vary: * on responses
A Vary header makes caches store a separate copy per cookie or header value, so almost nothing is served from cache.
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.
Back/forward cache blocked by Cache-Control: no-store (stale or reloaded page on Back)
Pressing Back reloads the page from scratch instead of restoring it instantly, or shows stale/old data.
Two steps away (27)
HTTP 500 Internal Server Error
The server hit an unexpected condition — usually an unhandled exception or misconfiguration in the application.
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.
Cloudflare Error 521: Web Server Is Down
Cloudflare couldn’t connect to your origin — the connection was refused.
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 403 Forbidden
The server understood the request but refuses to authorize it — you (or the server process) are not allowed to access this resour…
AccessDeniedException: User: arn:aws:iam::... is not authorized to perform: service:Action on resource: ...
The IAM user or role making the call has no permission for that action on that resource — the message names both.
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.
ACM certificate stuck in Pending validation
ACM is waiting to see the DNS (or email) validation record — it wasn’t created, was created in the wrong DNS zone, or has a typo.
dial tcp: lookup registry-1.docker.io: no such host / Temporary failure in name resolution during docker build
DNS isn’t working for the Docker daemon or inside build containers, so pulls and package downloads fail.
DNS not working inside a Kubernetes pod (could not resolve host / nslookup: can't resolve)
Pods can’t resolve service names or external hosts — CoreDNS is down, blocked by NetworkPolicy, or the upstream resolver fails.
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.
Google Cloud Load Balancing: 502 Bad Gateway — jsonPayload.statusDetails: failed_to_connect_to_backend / backend_connection_closed_before_data_sent_to_client
The load balancer couldn't get a valid response from your backend and returned 502.
GKE Ingress stuck: Error syncing to GCP — load balancer not created / NEG not found
The Ingress controller can't create or update the Google Cloud load balancer, so the Ingress has no address or routes.
HTTP 404 Not Found
The server can’t find anything at the requested URL.
ChunkLoadError: Loading chunk 123 failed.
A lazily loaded JavaScript chunk couldn’t be downloaded — usually because a new deployment removed the old hashed files.
Laravel: Illuminate\Database\Eloquent\ModelNotFoundException: No query results for model [App\Models\Post] 5
`findOrFail`, `firstOrFail` or route-model binding couldn't find a record, so Laravel returns a 404.
Laravel: LogicException: Unable to prepare route [dashboard] for serialization. Uses Closure.
`php artisan route:cache` failed because a route uses a closure, which can't be cached.
Laravel: RuntimeException: The /var/www/bootstrap/cache directory must be present and writable.
Laravel can't write its compiled cache files because the folder is missing or has the wrong permissions/owner.
Laravel: Be right back. / 503 Service Unavailable after php artisan down
The application is in maintenance mode — after `php artisan down` (or a failed deploy) it was never brought back up.
Resumed download restarts from zero (If-Range validator mismatch)
A download manager tries to resume, but the server sends the full file again because the validator no longer matches.
Brotli/gzip compression not applied (large uncompressed responses)
Responses are sent uncompressed, so pages are slower and bandwidth higher than necessary.
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…
405 Method Not Allowed on OPTIONS (CORS preflight)
The browser's CORS preflight (OPTIONS) request is rejected, so the real request never gets sent.
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.
ERR_CACHE_MISS: Confirm Form Resubmission
You pressed Back/Refresh on a page that was the result of a form POST, so the browser asks before sending the form again.
Map another error
Popular: 500400403ORA-009331064Critical errorFileNotFoundException assemblyTypeError