Error map
custom domain Firebase Hosting custom domain: SSL certificate pending / needs setup (DNS records)
Google Cloud / Firebase · layer 6, Platform & cloud
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.
Directly related (9)
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.
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 — 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 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.
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.
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.
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 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)
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.
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.
ping: google.com: Temporary failure in name resolution
The Linux host can’t resolve domain names — no working DNS server is configured or reachable.
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…
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.
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.
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.
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: 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.
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 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 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…
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 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.
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.
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.
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 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.
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.
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.
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.
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.
Map another error
Popular: 500400403ORA-009331064Critical errorFileNotFoundException assemblyTypeError