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

**Code:** `Google-managed cert` · **Category:** Google Cloud / Firebase · **Seen on:** Google Cloud

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

## 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?

---
Source: [WhatIsMyError](https://whatismyerror.com/errors/gcp/load-balancer-ssl-certificate-provisioning-failed-not-visible)
