SSL certificate domain status FAILED_NOT_VISIBLE

[SerhiiMarchuk]

I set up the next components for my project: Cloud DNS, classic Application Load Balancer and Cloud Run, with custom domain. I try to add compute engine google-managed SSL certificate to load balancer for https connection.

I followed the next instructions:

• created lb like here
• created and added to lb ssl certificate like here
• added record to Cloud DNS (A, AAAA, CNAME and CA types)
• changed domain nameservers in my account of domain provider

All checks show that all is fine (dig +trace domain, nslookup domain, gcloud compute target-https-proxies describe). I waited 72 hours (as describe in documentation). 

But I still have certificate status PROVISIONING and domain status FAILED_NOT_VISIBLE.

What didn't I do? Or what I did wrong?

[diannemcm]

Hi @SerhiiMarchuk,

Welcome to Google Cloud Community!

By the looks of it, you may have the necessary steps placed on your project, however, any of the following might be the possible workarounds and root causes for this kind of error/status for you to verify:

• The domain's DNS record doesn't resolve to the IP address of the Google Cloud load balancer. To resolve this issue, update the DNS records to point to your load balancer's IP address.
• The SSL certificate isn't attached to the load balancer's target proxy. To resolve this issue, update your load balancer configuration.
• The frontend ports for the global forwarding rule do not include port 443 for an SSL proxy load balancer. This can be resolved by adding a new forwarding rule with port 443.

Reference: Troubleshoot SSL certificates

In case you are using cloud CDN in front of your Load Balancer, you should not use Load Balancer Authorization, as the certificate will fail to renew, you should use DNS Authorization. See Domain authorization for Google-managed certificates and Create a DNS authorization as a guide.

Also, just a reminder to kindly double check your Domain settings as this may solely affect your provisioning process.

If the issue still persists and you need further assistance, you can file a ticket with our Google Cloud support.

I hope the above information is helpful.