Error map

Cache-Control Back/forward cache blocked by Cache-Control: no-store (stale or reloaded page on Back)

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.

Cache-Control — Back/forward cache blocked by Cache-Control: no-store (stale or reloaded page on Back) (HTTP)Cache-Contr…ERR_CACHE_MISS — ERR_CACHE_MISS: Confirm Form Resubmission (Browser)ERR_CACHE_MISSDomain still resolves to the old IP (DNS propagation/cache) — Networking: DNS changed but the domain still resolves to the old IP — TTL and resolver caching ("propagation") (Networking)Domain still resolv…404 — 404 on JS/CSS assets after a new deploy (HTTP)404CDN cache — CDN or browser serving stale content after a deploy (HTTP)CDN cacheETag — Conditional requests always return 200 (ETag/Last-Modified never matches) (HTTP)ETagVary — Cache hit rate collapses: Vary: Cookie or Vary: * on responses (HTTP)VaryVary: Origin — CORS responses cached for the wrong origin (missing Vary: Origin) (HTTP)Vary: OriginCache-Control — CDN not caching: Cache-Control private / no-cache / Set-Cookie on the response (HTTP)Cache-ControlFailed to fetch — TypeError: Failed to fetch / NetworkError when attempting to fetch resource (JavaScript)Failed to fetchuncontrolled to controlled — Warning: A component is changing an uncontrolled input to be controlled (React)uncontrolled to con…QuotaExceededError — QuotaExceededError: Failed to execute 'setItem' on 'Storage': Setting the value exceeded the quota (JavaScript)QuotaExceededErrorPending validation — ACM certificate stuck in Pending validation (AWS)Pending validationlookup registry-1.docker.io: no such host — dial tcp: lookup registry-1.docker.io: no such host / Temporary failure in name resolution during docker build (Docker)lookup registry-1.d…DNS in pod — DNS not working inside a Kubernetes pod (could not resolve host / nslookup: can't resolve) (Kubernetes)DNS in pod404 — HTTP 404 Not Found (HTTP)404ChunkLoadError — ChunkLoadError: Loading chunk 123 failed. (JavaScript)ChunkLoadErrorNo query results for model — Laravel: Illuminate\Database\Eloquent\ModelNotFoundException: No query results for model [App\Models\Post] 5 (Laravel)No query results fo…520 — Cloudflare Error 520: Web Server Returned an Unknown Error (Cloudflare)520The request could not be satisfied — CloudFront: 403 ERROR — The request could not be satisfied (AWS)The request could n…cf-cache-status: DYNAMIC — Cloudflare not caching: cf-cache-status DYNAMIC / BYPASS / MISS every time (Cloudflare)cf-cache-status: DY…304 — HTTP 304 Not Modified (HTTP)304If-Range — Resumed download restarts from zero (If-Range validator mismatch) (HTTP)If-RangeAccept-Encoding — Brotli/gzip compression not applied (large uncompressed responses) (HTTP)Accept-EncodingCloud CDN — Cloud CDN not caching: cache misses because of Set-Cookie, Cache-Control or missing cache mode (Google Cloud / Firebase)Cloud CDNCORS — CORS Error: No 'Access-Control-Allow-Origin' header is present (API)CORS405 — 405 Method Not Allowed on OPTIONS (CORS preflight) (HTTP)405CORS on errors — CORS error hides the real failure: Access-Control-Allow-Origin is missing on 4xx/5xx responses (HTTP)CORS on errors

Directly related (8)

ERR_CACHE_MISSBrowser

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.

Domain still resolves to the old IP (DNS propagation/cache)Networking

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.

404HTTP

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 cacheHTTP

CDN or browser serving stale content after a deploy

Users still see the old CSS, JS or HTML after you released a new version.

ETagHTTP

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…

VaryHTTP

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.

Vary: OriginHTTP

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.

Cache-ControlHTTP

CDN not caching: Cache-Control private / no-cache / Set-Cookie on the response

The response tells shared caches not to store it, so the CDN passes every request to your origin.

Two steps away (19)

Failed to fetchJavaScript

TypeError: Failed to fetch / NetworkError when attempting to fetch resource

The browser couldn’t complete the request at the network level — CORS, DNS, offline, blocked mixed content, or the server refused…

uncontrolled to controlledReact

Warning: A component is changing an uncontrolled input to be controlled

An input’s `value` started as `undefined` (uncontrolled) and later became a defined value (controlled), or vice versa.

QuotaExceededErrorJavaScript

QuotaExceededError: Failed to execute 'setItem' on 'Storage': Setting the value exceeded the quota

localStorage/sessionStorage is full (about 5 MB per origin) or storage is disabled.

Pending validationAWS

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.

lookup registry-1.docker.io: no such hostDocker

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 in podKubernetes

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.

404HTTP

HTTP 404 Not Found

The server can’t find anything at the requested URL.

ChunkLoadErrorJavaScript

ChunkLoadError: Loading chunk 123 failed.

A lazily loaded JavaScript chunk couldn’t be downloaded — usually because a new deployment removed the old hashed files.

No query results for modelLaravel

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.

520Cloudflare

Cloudflare Error 520: Web Server Returned an Unknown Error

Cloudflare connected to your origin, but the origin returned an empty, unknown or invalid response.

The request could not be satisfiedAWS

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…

cf-cache-status: DYNAMICCloudflare

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…

304HTTP

HTTP 304 Not Modified

The cached copy is still valid, so the server sends no body and the client reuses its cache.

If-RangeHTTP

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.

Accept-EncodingHTTP

Brotli/gzip compression not applied (large uncompressed responses)

Responses are sent uncompressed, so pages are slower and bandwidth higher than necessary.

Cloud CDNGoogle Cloud / Firebase

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.

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…

405HTTP

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 on errorsHTTP

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.