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.
managed SSL certificate PROVISIONING stuck load balancerGoogle-managed certificate provisioning faileddomainStatus: FAILED_NOT_VISIBLEcertificate status PROVISIONING_FAILED 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
- Fix the A/AAAA records for the LB IP
- Check status:
gcloud compute ssl-certificates describe CERT - Disable proxying and wait
Detailed fix by platform
Shell
gcloud compute ssl-certificates describe CERT --global --format="yaml(managed)"
How to diagnose
- DNS — Points to LB?
- Status — FAILED_NOT_VISIBLE?
- 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:
Similar errors
Most viewed in Google Cloud / Firebase
- Missing or insufficient permissions Firestore: FirebaseError: [code=permission-denied]: Missing or insufficient permissions
- Container failed to start Cloud Run: The user-provided container failed to start and listen on the port defined provided by the PORT=8080 environment variable
- 409: The resource already exists Compute Engine: ERROR: (gcloud.compute.instances.create) Could not fetch resource: The resource 'projects/p/zones/z/instances/vm-1' already exists
Other ways to find it
Where this error sits
Origin: Platform & cloud. Errors that are often confused with or caused by this one (click to open):
🧠 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.
Report a correction or suggest an improvement
Last updated 18 Nov 2026