certificate stuck in PROVISIONING status

More than 36 hours ago, I created a bucket, a load balancer and I configured the load balancer with a new managed certificate. I also configured my DNS settings to point to the IP address of the load balancer. Indeed dig www.mydomain.com returns this IP address. But the certificate remains in PROVISIONING status and the description is “The Google-managed certificate has been created and Google Cloud is working with the Certificate Authority to sign it”. Accessing this URL in the browser returns Error code: SSL_ERROR_NO_CYPHER_OVERLAP.

The only thing that is off is that I created 3 subdomains for this certificate: www.mydomain.com, app.mydomain.com and api.mydomain.com. For now, only the www is working (i.e. just a static website on a new Google bucket) and indeed it’s shown as ACTIVE and the other 2 are FAILED_NOT_VISIBLE. Do I need to delete the failed 2 until I have them up and running just to make the www to work, or is it something completely different?

I wasn’t getting any responses, so I re-configured the ssl cert without the 2 subdomains that weren’t ready. Sure enough, it worked in 30 minutes after the new setup. Hope this helps another poor schmuck that is trying to follow incomplete Google documentation.

1 Like