Error map
cache Firebase Hosting serves old files after deploy (CDN cache and Cache-Control headers)
Google Cloud / Firebase · layer 6, Platform & cloud
Centre: this error. First ring: errors it is linked with (10). 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 (10)
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.
Firebase Hosting: Page Not Found — This file does not exist and there was no 404.html or index.html found in the document root
A single-page app route returns 404 when opened directly or refreshed, because Firebase Hosting looks for a real file at that pat…
App Engine deploy failed: invalid app.yaml (runtime not supported / entrypoint / handlers)
`gcloud app deploy` rejects the configuration or the app fails its health check after deploy.
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.
Firebase Hosting custom domain: SSL certificate pending / needs setup (DNS records)
The custom domain stays in "Needs setup" or the certificate is pending because DNS doesn't match the required records.
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.
Firebase Hosting deploy: Could not find site / hosting target not configured
`firebase deploy --only hosting` can't resolve the site or target in firebase.json.
Firebase Functions deploy failed: Node runtime/engine unsupported or build error
`firebase deploy --only functions` fails because of the Node version, dependency or build step.
Firebase deploy: User code failed to load. Cannot determine backend specification
The CLI couldn't execute your `functions` source to discover which functions it defines, so nothing is deployed.
Two steps away (28)
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.
Error: Minified React error #31; visit https://react.dev/errors/31 for the full message
A production React build threw an error whose message was shortened to a number.
Firebase CLI: Error: Authentication Error: Your credentials are no longer valid. Please run firebase login --reauth
The Firebase CLI's saved login expired or was revoked.
Firebase CLI: Error: Your project my-app must be on the Blaze (pay-as-you-go) plan to complete this command. Required API cloudbuild.googleapis.com can't be enabled until the upgrade is complete
Deploying Cloud Functions needs the Blaze plan because it relies on Cloud Build and Artifact Registry.
Cloud Run: The user-provided container failed to start and listen on the port defined provided by the PORT=8080 environment variable
Cloud Run started your container, but nothing listened on $PORT within the startup timeout — the app crashed, listens on another…
Google Cloud: 403 This API method requires billing to be enabled. Please enable billing on project and retry
The project has no active billing account, and the API/service needs one.
Cloud Functions: Build failed: function.js does not exist / npm install failed with exit code 1 (Cloud Build step)
The deployment's build step (Cloud Build) failed, so no new function version was created.
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.
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…
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.
Let's Encrypt/CA: CAA record for example.com prevents issuance
The domain's DNS CAA records do not list the certificate authority you asked, so the CA must refuse.
Cloud Run domain mapping stuck: certificate provisioning pending (CertificatePending)
A custom domain mapped to Cloud Run never gets a certificate.
GKE ManagedCertificate stuck Provisioning / FailedNotVisible (domain doesn't point to the load balancer)
Google can't validate the domain because DNS doesn't reach the Ingress's IP, so the certificate never becomes Active.
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.
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…
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.
Firebase CLI: Failed to get Firebase project / Error: Not authorized, or HTTP Error 403 on project
The CLI can't find or access the project you passed, so deploy and use commands fail.
TypeError: f() takes 1 positional argument but 2 were given
A function was called with more positional arguments than it accepts — very often a method missing `self`.
TypeError: f() missing 1 required positional argument: 'x'
A function was called without a required parameter.
Terraform: Error: Invalid function argument — Invalid value for "list" parameter: list of string required / Call to function "lookup" failed
A built-in function got a wrong type/value (empty list, missing key, wrong type).
Cloud Functions: Provided module can't be loaded / Function failed on loading user code. This is likely due to a bug in the user code
The function started but could not import/initialise your code, so every invocation fails.
Cloud Functions: Error: Cannot find module 'X' (dependency missing at runtime)
The deployed function can't load a module that works locally.
Firebase Hosting rewrite to a function returns 404 (wrong function name or region)
A `rewrites` rule pointing at Cloud Functions or Cloud Run doesn't reach the service.
Map another error
Popular: 500400403ORA-009331064Critical errorFileNotFoundException assemblyTypeError