Error map
Google-managed cert Google-managed SSL certificate stuck in PROVISIONING / FAILED_NOT_VISIBLE on the HTTPS load balancer
Google Cloud / Firebase · layer 6, Platform & cloud
Centre: this error. First ring: errors it is linked with (12). 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 (12)
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.
Networking: VPN connected but internal names like db.corp.local don't resolve — split DNS / 127.0.0.53 stub resolver not using the VPN DNS
The VPN works by IP, but internal hostnames fail because queries still go to your normal DNS server.
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.
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.
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.
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 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.
ORA-12545: Connect failed because target host or object does not exist
The host name in the connect descriptor can't be resolved or doesn't exist.
Cloud Run domain mapping stuck: certificate provisioning pending (CertificatePending)
A custom domain mapped to Cloud Run never gets a certificate.
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.
Two steps away (36)
connect: Network is unreachable (ENETUNREACH)
The host has no route to the destination network — no default gateway, interface down, or trying IPv6 without IPv6 connectivity.
ERR_CONNECTION_TIMED_OUT: This site can’t be reached — example.com took too long to respond
The browser waited for the server but got no response — the server is down/unreachable, a firewall drops traffic, or DNS points t…
Chrome: This site can’t be reached — The webpage at https://… might be temporarily down. ERR_ADDRESS_UNREACHABLE
The computer has no route to the server’s IP address — often an IPv6 problem, a wrong local-network address, or a VPN routing iss…
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.
Networking: Server reachable from the internet but not from inside the LAN via its public IP — NAT loopback / hairpin NAT not working
Devices on your own network can't use the router's public address to reach a server that is also on that network.
Networking: VPN is connected but I can't reach the internal network — missing routes, split tunnel or overlapping subnets
The tunnel is up, but traffic for the office/VPC subnets isn't sent through it or comes back the wrong way.
Error: getaddrinfo ENOTFOUND host / Name or service not known
DNS lookup for the hostname failed — the name is wrong, doesn’t exist, or this machine can’t resolve it.
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.
NotAllowedError: play() failed because the user didn't interact with the document first.
The browser blocked media autoplay with sound until the user interacts with the page.
SSL: CERTIFICATE_VERIFY_FAILED / unable to get local issuer certificate
The client couldn’t verify the server’s TLS certificate chain, so it refused the HTTPS connection.
fatal: unable to access 'https://…': SSL certificate problem: unable to get local issuer certificate
Git doesn’t trust the HTTPS server’s certificate — corporate proxy, self-hosted Git with an internal CA, or outdated CA bundle.
fatal: unable to access 'https://github.com/…': Could not resolve host: github.com
DNS lookup for the Git host failed from this machine.
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…
Cloudflare HTTP 530 (with Error 1016 Origin DNS error / 1033 tunnel error)
Cloudflare returns 530 together with a 1xxx error; the 1xxx code (usually 1016 or 1033) tells you the real cause.
Cloudflare Error 1000: DNS points to prohibited IP
A proxied DNS record points at a Cloudflare IP address, creating a loop.
Cloudflare Error 1001: DNS resolution error
Cloudflare received the request but the hostname isn’t set up on Cloudflare (or the domain was just added and not active yet).
Cloudflare Error 1002: DNS points to Prohibited IP / Restricted
A record points to a private, reserved or Cloudflare IP that Cloudflare won’t proxy to.
Cloudflare Error 1003: Direct IP access not allowed
The request went to a Cloudflare IP address directly (or with a Host header for a domain not on Cloudflare).
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.
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…
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.
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.
java.net.UnknownHostException: api.example.com
DNS resolution failed for the hostname.
cURL error 6: Could not resolve host: api.example.com
PHP cURL couldn’t resolve the hostname via DNS.
ORA-00001: unique constraint (SCHEMA.PK_X) violated
An insert/update duplicated a value in a unique or primary key constraint.
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.
Error from server: admission webhook "validate.nginx.ingress.kubernetes.io" denied the request
A validating admission webhook (ingress-nginx, Gatekeeper/OPA, Kyverno) inspected your object and rejected it; the reason follows…
GKE/Kubernetes: Pod unschedulable — 0/3 nodes are available: 3 Insufficient cpu
The scheduler found no node with enough free CPU/memory for the pod's resource requests.
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.
Map another error
Popular: 500400403ORA-009331064Critical errorFileNotFoundException assemblyTypeError