Error map

custom domain Firebase Hosting custom domain: SSL certificate pending / needs setup (DNS records)

Google Cloud / Firebase · layer 6, Platform & cloud

Open the full error page →

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

custom domain — Firebase Hosting custom domain: SSL certificate pending / needs setup (DNS records) (Google Cloud / Firebase)custom doma…Domain 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…CAA record forbids issuance — Let's Encrypt/CA: CAA record for example.com prevents issuance (SSL / TLS)CAA record forbids …Firebase Hosting: Page Not Found on refresh (SPA routes) — Firebase Hosting: Page Not Found — This file does not exist and there was no 404.html or index.html found in the document root (Google Cloud / Firebase)Firebase Hosting: P…Google-managed cert — Google-managed SSL certificate stuck in PROVISIONING / FAILED_NOT_VISIBLE on the HTTPS load balancer (Google Cloud / Firebase)Google-managed certrewrites — Firebase Hosting rewrite to a function returns 404 (wrong function name or region) (Google Cloud / Firebase)rewritesdomain mapping — Cloud Run domain mapping stuck: certificate provisioning pending (CertificatePending) (Google Cloud / Firebase)domain mappingManagedCertificate — GKE ManagedCertificate stuck Provisioning / FailedNotVisible (domain doesn't point to the load balancer) (Google Cloud / Firebase)ManagedCertificatehosting — Firebase Hosting deploy: Could not find site / hosting target not configured (Google Cloud / Firebase)hostingcache — Firebase Hosting serves old files after deploy (CDN cache and Cache-Control headers) (Google Cloud / Firebase)cachePending 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 podsudo: unable to resolve host — sudo: unable to resolve host <hostname>: Name or service not known (Linux)sudo: unable to res…Temporary failure in name resolution — ping: google.com: Temporary failure in name resolution (Linux)Temporary failure i…523 — Cloudflare Error 523: Origin is unreachable (Cloudflare)523Minified React error — Error: Minified React error #31; visit https://react.dev/errors/31 for the full message (React)Minified React errorFirebase CLI: Authentication Error: Your credentials are no longer valid — Firebase CLI: Error: Authentication Error: Your credentials are no longer valid. Please run firebase login --reauth (Google Cloud / Firebase)Firebase CLI: Authe…Firebase: Your project must be on the Blaze (pay-as-you-go) plan — 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 (Google Cloud / Firebase)Firebase: Your proj…ERR_NAME_NOT_RESOLVED — net::ERR_NAME_NOT_RESOLVED (This site can't be reached — server IP address could not be found) (JavaScript)ERR_NAME_NOT_RESOLV…IPv6 enabled but broken: slow connections / Happy Eyeballs — Networking: Sites load slowly or hang for seconds — broken IPv6 (AAAA resolves, IPv6 route missing) falling back to IPv4 (Networking)IPv6 enabled but br…dig: status: SERVFAIL (DNSSEC validation failed) — Networking: dig: ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL — resolver failed to answer (DNSSEC validation or upstream failure) (Networking)dig: status: SERVFA…Cloud Run 403: Your client does not have permission to get URL — Cloud Run: Error: Forbidden — Your client does not have permission to get URL / from this server (Google Cloud / Firebase)Cloud Run 403: Your…deploy — Firebase Functions deploy failed: Node runtime/engine unsupported or build error (Google Cloud / Firebase)deployHttpsError — Firebase callable function error: FirebaseError: internal (unhandled exception in the function) (Google Cloud / Firebase)HttpsErrorCloud Run 503: The request failed because the instance had an error — Cloud Run: 503 Service Unavailable — The request was aborted because there was no available instance (Google Cloud / Firebase)Cloud Run 503: The …Container memory limit exceeded — Cloud Run: Memory limit of 512 MiB exceeded with 530 MiB used. Consider increasing the memory limit (Google Cloud / Firebase)Container memory li…Cloud Run 504: The request has been terminated because it has reached the maximum request timeout — Cloud Run: 504 Gateway Timeout — The request has been terminated because it has reached the maximum request timeout (Google Cloud / Firebase)Cloud Run 504: The …gke-gcloud-auth-plugin not found — kubectl: error: executable gke-gcloud-auth-plugin not found — it looks like you are trying to use a client-go credential plugin that is not installed (Google Cloud / Firebase)gke-gcloud-auth-plu…DNS lookups take 5 seconds (timeout then retry) — Networking: Every connection pauses about 5 seconds — resolv.conf nameserver timeout, then fallback to the next DNS server (Networking)DNS lookups take 5 …dig: status: REFUSED (recursion not available) — Networking: dig: status: REFUSED / recursion requested but not available — the DNS server won't resolve queries for you (Networking)dig: status: REFUSE…App Engine — App Engine deploy failed: invalid app.yaml (runtime not supported / entrypoint / handlers) (Google Cloud / Firebase)App Enginebackend spec — Firebase deploy: User code failed to load. Cannot determine backend specification (Google Cloud / Firebase)backend specproject — Firebase CLI: Failed to get Firebase project / Error: Not authorized, or HTTP Error 403 on project (Google Cloud / Firebase)project404 — 404 on JS/CSS assets after a new deploy (HTTP)404CDN cache — CDN or browser serving stale content after a deploy (HTTP)CDN cacheCloud CDN — Cloud CDN not caching: cache misses because of Set-Cookie, Cache-Control or missing cache mode (Google Cloud / Firebase)Cloud CDN

Directly related (9)

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.

CAA record forbids issuanceSSL / TLS

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.

Firebase Hosting: Page Not Found on refresh (SPA routes)Google Cloud / Firebase

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…

Google-managed certGoogle Cloud / Firebase

Google-managed SSL certificate stuck in PROVISIONING / FAILED_NOT_VISIBLE on the HTTPS load balancer

The certificate can't be issued because the domain doesn't resolve to the load balancer's IP.

rewritesGoogle Cloud / Firebase

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.

domain mappingGoogle Cloud / Firebase

Cloud Run domain mapping stuck: certificate provisioning pending (CertificatePending)

A custom domain mapped to Cloud Run never gets a certificate.

ManagedCertificateGoogle Cloud / Firebase

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.

hostingGoogle Cloud / Firebase

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.

cacheGoogle Cloud / Firebase

Firebase Hosting serves old files after deploy (CDN cache and Cache-Control headers)

Visitors still see the previous version because assets or HTML are cached by the browser or Hosting's CDN.

Two steps away (27)

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.

sudo: unable to resolve hostLinux

sudo: unable to resolve host <hostname>: Name or service not known

The machine’s hostname isn’t in /etc/hosts (or DNS), so sudo prints this warning — usually after changing the hostname.

Temporary failure in name resolutionLinux

ping: google.com: Temporary failure in name resolution

The Linux host can’t resolve domain names — no working DNS server is configured or reachable.

523Cloudflare

Cloudflare Error 523: Origin is unreachable

Cloudflare can’t find a network route to your origin server — the DNS record points to a wrong/unroutable IP or the origin networ…

Minified React errorReact

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: Authentication Error: Your credentials are no longer validGoogle Cloud / Firebase

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: Your project must be on the Blaze (pay-as-you-go) planGoogle Cloud / Firebase

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.

ERR_NAME_NOT_RESOLVEDJavaScript

net::ERR_NAME_NOT_RESOLVED (This site can't be reached — server IP address could not be found)

DNS couldn’t resolve the hostname in the browser.

IPv6 enabled but broken: slow connections / Happy EyeballsNetworking

Networking: Sites load slowly or hang for seconds — broken IPv6 (AAAA resolves, IPv6 route missing) falling back to IPv4

The client prefers IPv6, but the IPv6 path is broken, so every connection waits for a timeout before using IPv4.

dig: status: SERVFAIL (DNSSEC validation failed)Networking

Networking: dig: ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL — resolver failed to answer (DNSSEC validation or upstream failure)

The DNS resolver couldn't get a valid answer, often because DNSSEC signatures are broken or the authoritative servers fail.

Cloud Run 403: Your client does not have permission to get URLGoogle Cloud / Firebase

Cloud Run: Error: Forbidden — Your client does not have permission to get URL / from this server

The Cloud Run service requires authentication and the caller has no valid identity token or the `roles/run.invoker` role.

deployGoogle Cloud / Firebase

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.

HttpsErrorGoogle Cloud / Firebase

Firebase callable function error: FirebaseError: internal (unhandled exception in the function)

A callable function threw a non-`HttpsError` exception, so the client only sees a generic `internal` error.

Cloud Run 503: The request failed because the instance had an errorGoogle Cloud / Firebase

Cloud Run: 503 Service Unavailable — The request was aborted because there was no available instance

Cloud Run could not serve the request: no instance was ready, instances crashed, or the service hit its max-instances/concurrency…

Container memory limit exceededGoogle Cloud / Firebase

Cloud Run: Memory limit of 512 MiB exceeded with 530 MiB used. Consider increasing the memory limit

The container used more memory than the Cloud Run service allows, so the instance was terminated.

Cloud Run 504: The request has been terminated because it has reached the maximum request timeoutGoogle Cloud / Firebase

Cloud Run: 504 Gateway Timeout — The request has been terminated because it has reached the maximum request timeout

The request ran longer than the service's request timeout (default 5 minutes, max 60), so Cloud Run closed it.

gke-gcloud-auth-plugin not foundGoogle Cloud / Firebase

kubectl: error: executable gke-gcloud-auth-plugin not found — it looks like you are trying to use a client-go credential plugin that is not installed

kubectl needs the `gke-gcloud-auth-plugin` binary to authenticate to GKE, and it is missing from PATH.

DNS lookups take 5 seconds (timeout then retry)Networking

Networking: Every connection pauses about 5 seconds — resolv.conf nameserver timeout, then fallback to the next DNS server

The first DNS server in the list isn't answering, so each lookup waits out a timeout before trying the next one.

dig: status: REFUSED (recursion not available)Networking

Networking: dig: status: REFUSED / recursion requested but not available — the DNS server won't resolve queries for you

The DNS server answered, but its policy refuses to look up names for your address.

App EngineGoogle Cloud / Firebase

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.

backend specGoogle Cloud / Firebase

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.

projectGoogle Cloud / Firebase

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.

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.

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.