# SSL

**URL:** <https://discuss.google.dev/t/ssl/182454>\
**Category:** Serverless Applications\
**Tags:** gke\
**Created:** [February 24, 2025, 1:37pm UTC](https://discuss.google.dev/t/ssl/182454 "2025-02-24T13:37:48Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![x86\_128](https://d3byx8b92xw3lq.cloudfront.net/user_avatar/discuss.google.dev/x86_128/32/212_2.png) [@x86\_128](https://discuss.google.dev/u/x86_128)\
**Post date:** [February 24, 2025, 1:37pm UTC](https://discuss.google.dev/t/ssl/182454/1 "2025-02-24T13:37:48Z")

</div>

Helllo,  
I’ve created ceertificate, but it’s status: PROVISIONING for 2 hours.

```auto
gcloud compute ssl-certificates describe mcrt-94a7195a-0f1d-4c85-b67f-fb16fda2bf5f
creationTimestamp: '2025-02-24T03:17:40.212-08:00'
id: '7909269187352193979'
kind: compute#sslCertificate
managed:
domainStatus:
[app.apis-charlieai-ml.com](http://app.apis-charlieai-ml.com/): FAILED_NOT_VISIBLE
domains:
- [app.apis-charlieai-ml.com](http://app.apis-charlieai-ml.com/)
status: PROVISIONING
name: mcrt-94a7195a-0f1d-4c85-b67f-fb16fda2bf5f
selfLink: [https://www.googleapis.com/compute/v1/projects/charlie-ai/global/sslCertificates/mcrt-94a7195a-0f1d-4c85-b67f-fb16fda2bf5f](https://www.googleapis.com/compute/v1/projects/charlie-ai/global/sslCertificates/mcrt-94a7195a-0f1d-4c85-b67f-fb16fda2bf5f)
type: MANAGED

```

Can you help me?

---

<div class="post-metadata">

**Author:** ![debolek](https://d3byx8b92xw3lq.cloudfront.net/user_avatar/discuss.google.dev/debolek/32/315_2.png) [@debolek](https://discuss.google.dev/u/debolek)\
**Post date:** [February 24, 2025, 2:58pm UTC](https://discuss.google.dev/t/ssl/182454/2 "2025-02-24T14:58:41Z")

</div>

The FAILED\_NOT\_VISIBLE status indicates that the domain is not visible to the Google Cloud Certificate Authority. To resolve this issue:

1. Verify that the DNS records are correctly configured and pointing to the correct IP address.

2. Check DNS propagation to ensure that the changes have propagated globally.

3. Verify domain ownership in Google Search Console.

4. 
  1. **A Record** :

  2. **CNAME Record** (if applicable):

Use the dig command to verify the DNS configuration: dig [app.apis-charlieai-ml.com](http://app.apis-charlieai-ml.com)

Ensure that the output shows the correct IP address.

1. Recreate the SSL Certificate  
If the DNS records were incorrect and you have updated them, you might need to delete the existing SSL certificate and create a new one:

Delete the Existing SSL Certificate:

gcloud compute ssl-certificates delete mcrt-94a7195a-0f1d-4c85-b67f-fb16fda2bf5f

Crerate a new ssl certificate

gcloud compute ssl-certificates create mcrt-94a7195a-0f1d-4c85-b67f-fb16fda2bf5f   
–domains=[app.apis-charlieai-ml.com](http://app.apis-charlieai-ml.com)

I hope this will help

---

<div class="post-metadata">

**Author:** ![talk2patel](https://d3byx8b92xw3lq.cloudfront.net/user_avatar/discuss.google.dev/talk2patel/32/171536_2.png) [@talk2patel](https://discuss.google.dev/u/talk2patel)\
**Post date:** [February 24, 2025, 4:30pm UTC](https://discuss.google.dev/t/ssl/182454/3 "2025-02-24T16:30:09Z")

</div>

There are a number of possible reasons for this. Refer to the SSL certificate troubleshooting guide: [https://cloud.google.com/load-balancing/docs/ssl-certificates/troubleshooting](https://cloud.google.com/load-balancing/docs/ssl-certificates/troubleshooting)

 ![talk2patel_1-1740414452318.png](https://d2yds90mtvelsl.cloudfront.net/original/3X/4/1/4187eee081e2225c3b4c46c41ebd6e9fb397c346.png)

 ![talk2patel_0-1740414425355.png](https://d2yds90mtvelsl.cloudfront.net/original/3X/6/8/6830cdecfcc13d497094c96e56cf09787f227209.png)

---

<div class="post-metadata">

**Author:** ![x86\_128](https://d3byx8b92xw3lq.cloudfront.net/user_avatar/discuss.google.dev/x86_128/32/212_2.png) [@x86\_128](https://discuss.google.dev/u/x86_128)\
**Post date:** [February 24, 2025, 10:48pm UTC](https://discuss.google.dev/t/ssl/182454/4 "2025-02-24T22:48:14Z")

</div>

DNS records are correct. IP is correct. Checked.

---

<div class="post-metadata">

**Author:** ![x86\_128](https://d3byx8b92xw3lq.cloudfront.net/user_avatar/discuss.google.dev/x86_128/32/212_2.png) [@x86\_128](https://discuss.google.dev/u/x86_128)\
**Post date:** [February 24, 2025, 10:49pm UTC](https://discuss.google.dev/t/ssl/182454/5 "2025-02-24T22:49:01Z")

</div>

Everything checked, everything tried, nothing helped.

---

<div class="post-metadata">

**Author:** ![x86\_128](https://d3byx8b92xw3lq.cloudfront.net/user_avatar/discuss.google.dev/x86_128/32/212_2.png) [@x86\_128](https://discuss.google.dev/u/x86_128)\
**Post date:** [February 24, 2025, 11:47pm UTC](https://discuss.google.dev/t/ssl/182454/6 "2025-02-24T23:47:45Z")

</div>

✅ The DNS records are correctly configured and pointing to the correct IP  
address.  
✅ Check DNS propagation to ensure that the changes have propagated globally.  
✅ Verify domain ownership in Google Search Console.

A Record:  
✅ Type: A Name: [app.apis-charlieai-ml.com](http://app.apis-charlieai-ml.com) Value: [Your Load Balancer or VM  
IP Address]

CNAME Record (if applicable):  
Type: CNAME Name: [www.app.apis-charlieai-ml.com](http://www.app.apis-charlieai-ml.com) Value:  
app.apis-charlieai-ml.comUpdate DNS records if necessary and recreate the  
SSL certificate.

Here is an example of how to configure the DNS records for your domain:

✅ Use the dig command to verify the DNS configuration: dig  
[app.apis-charlieai-ml.com](http://app.apis-charlieai-ml.com) Status= ✅

✅ Ensure that the output shows the correct IP address.

✅ 5. Recreate the SSL Certificate  
If the DNS records were incorrect and you have updated them, you might need  
to delete the existing SSL certificate and create a new one:

✅ Delete the Existing SSL Certificate:

✅ gcloud compute ssl-certificates delete  
mcrt-94a7195a-0f1d-4c85-b67f-fb16fda2bf5f

✅ Crerate a new ssl certificate

✅ gcloud compute ssl-certificates create  
mcrt-94a7195a-0f1d-4c85-b67f-fb16fda2bf5f   
–domains=[app.apis-charlieai-ml.com](http://app.apis-charlieai-ml.com)

Everything is OK, except ‘PROVISIONING’ and ‘FAILED\_NOT\_VISIBLE’  
Nothing helped.
