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.

Exact message you may see managed SSL certificate PROVISIONING stuck load balancerGoogle-managed certificate provisioning faileddomainStatus: FAILED_NOT_VISIBLEcertificate status PROVISIONING_FAILED
Seen on: Google Cloud

Meaning

Create an A (and AAAA if IPv6) record pointing the domain at the LB's frontend IP, remove conflicting records, make sure the forwarding rule uses port 443 with the cert attached, and keep proxies (Cloudflare orange cloud) off while provisioning. It may take up to 60 minutes; FAILED_NOT_VISIBLE means DNS isn't pointing correctly.

Common causes

  • DNS doesn't point to the LB IP
  • Extra AAAA record to another host
  • CDN/proxy in front
  • CAA records blocking Google
  • Certificate not attached to the target proxy

⚡ Quick fix

  1. Fix the A/AAAA records for the LB IP
  2. Check status: gcloud compute ssl-certificates describe CERT
  3. Disable proxying and wait

Detailed fix by platform

Shell

  1. gcloud compute ssl-certificates describe CERT --global --format="yaml(managed)"

How to diagnose

  1. DNS — Points to LB?
  2. Status — FAILED_NOT_VISIBLE?
  3. Attached — To proxy?

🔧 Still not fixed?

Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:

Where this error sits

Origin: Platform & cloud. Errors that are often confused with or caused by this one (click to open):

CAA record forbids issuance — Let's Encrypt/CA: CAA record for example.com prevents issuance (SSL / TLS)CAA record forbids is…Cloud Armor — Cloud Armor returns 403 Forbidden: request blocked by a security policy rule (Google Cloud / Firebase)Cloud ArmorCloud CDN — Cloud CDN not caching: cache misses because of Set-Cookie, Cache-Control or missing cache mode (Google Cloud / Firebase)Cloud CDNcustom domain — Firebase Hosting custom domain: SSL certificate pending / needs setup (DNS records) (Google Cloud / Firebase)custom domaindig: 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: REFUSED …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: SERVFAIL…domain mapping — Cloud Run domain mapping stuck: certificate provisioning pending (CertificatePending) (Google Cloud / Firebase)domain mappingERR_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_RESOLVEDGoogle-ma…

Explore the map of this error Full error map →

🧠 Still stuck? Analyze your error

Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.

💬 What worked for others

No tips yet — did something else fix this for you?

Share what worked for you

Tips are checked by an editor before they appear. Links are removed.