# Unable to provision certificate

**URL:** <https://discuss.google.dev/t/unable-to-provision-certificate/164442>\
**Category:** Compute Infrastructure\
**Tags:** server-configuration\
**Created:** [August 25, 2024, 3:45am UTC](https://discuss.google.dev/t/unable-to-provision-certificate/164442 "2024-08-25T03:45:48Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![mountaincode2](https://d3byx8b92xw3lq.cloudfront.net/user_avatar/discuss.google.dev/mountaincode2/32/4230_2.png) [@mountaincode2](https://discuss.google.dev/u/mountaincode2)\
**Post date:** [August 25, 2024, 3:45am UTC](https://discuss.google.dev/t/unable-to-provision-certificate/164442/1 "2024-08-25T03:45:48Z")

</div>

I am trying to follow the steps in the following document to create a certificate using Certificate Manager:

[https://cloud.google.com/certificate-manager/docs/deploy-google-managed-dns-auth#create-cert-dns-auth](https://cloud.google.com/certificate-manager/docs/deploy-google-managed-dns-auth#create-cert-dns-auth)

I have a query regarding “Add the CNAME record to your DNS configuration”

[https://cloud.google.com/certificate-manager/docs/deploy-google-managed-dns-auth#cname-record](https://cloud.google.com/certificate-manager/docs/deploy-google-managed-dns-auth#cname-record)

I have create a public zone using Cloud DNS, but my domain is from Hostinger.  
I have added a CNAME record as shown in the documentation.

When i run the command to verify whether my certificate is added, i still don’t see the ACTIVE state even after several hours:

```auto
`gcloud certificate-manager certificates describe <cert-name>`

```

```html
createTime: '2024-08-25T03:26:07.788998638Z'
managed:
  authorizationAttemptInfo:
  - domain: <domain>
    state: AUTHORIZING
  dnsAuthorizations:
  - projects/xxxxx/locations/global/dnsAuthorizations/test-dns-auth
  domains:
  - <domain>
  state: PROVISIONING
name: projects/<project>/locations/global/certificates/test-cert
sanDnsnames:
- <domain>
updateTime: '2024-08-25T03:26:08.245783381Z'

```

After some time, i got the message that the authorization has failed:

```html
createTime: '2024-08-25T03:26:07.788998638Z'
managed:
  authorizationAttemptInfo:
  - domain: <domain>
    failureReason: CONFIG
    state: FAILED
  dnsAuthorizations:
  - projects/xxxxxxxx/locations/global/dnsAuthorizations/test-dns-auth
  domains:
  - <domain>
  provisioningIssue:
    reason: AUTHORIZATION_ISSUE
  state: PROVISIONING
name: projects/<project>/locations/global/certificates/test-cert
sanDnsnames:
- <domain>
updateTime: '2024-08-25T03:26:08.245783381Z'

```

Where am i going wrong here.

---

<div class="post-metadata">

**Author:** ![jamespatrickm](https://d3byx8b92xw3lq.cloudfront.net/user_avatar/discuss.google.dev/jamespatrickm/32/6173_2.png) [@jamespatrickm](https://discuss.google.dev/u/jamespatrickm)\
**Post date:** [August 27, 2024, 6:06pm UTC](https://discuss.google.dev/t/unable-to-provision-certificate/164442/2 "2024-08-27T18:06:51Z")

</div>

Hi @mountaincode2 ,

Welcome to Google Cloud Community!

It appears you encountered an issue during authorization. In the message, **_authorizationAttemptInfo_** is showing **_[failureReason](https://cloud.google.com/certificate-manager/docs/reference/certificate-manager/rpc/google.cloud.certificatemanager.v1#failurereason)_\_\_\_\__: CONFIG_**. This means that there was an issue with your DNS or load balancer configuration. This prevents the Managed Certificate from being issued.

It is best to review your DNS or load balancer configuration for your domain and try again. Please note that you will have to delete and create a new managed certificate resource to try again.

Please refer to the following troubleshooting pages below for more guidance:

- [Troubleshooting Certificate Manager](https://cloud.google.com/certificate-manager/docs/troubleshooting)
- [Troubleshoot SSL certificates](https://cloud.google.com/load-balancing/docs/ssl-certificates/troubleshooting)

Hope this helps.

---

<div class="post-metadata">

**Author:** ![AI](https://d3byx8b92xw3lq.cloudfront.net/user_avatar/discuss.google.dev/ai/32/212_2.png) [@AI](https://discuss.google.dev/u/AI)\
**Post date:** [August 27, 2024, 6:59pm UTC](https://discuss.google.dev/t/unable-to-provision-certificate/164442/3 "2024-08-27T18:59:36Z")

</div>

A crucial part of troubleshooting this issue would be to verify if the dns record you created in your dns zone is publicly resolvable. Try to resolve it from your system (using nslookup or dig or host or ping) or online with one of the services like dnschecker and see if the name (\_acme-challenge…) resolved to that long string ending in goog.

---

<div class="post-metadata">

**Author:** ![mountaincode2](https://d3byx8b92xw3lq.cloudfront.net/user_avatar/discuss.google.dev/mountaincode2/32/4230_2.png) [@mountaincode2](https://discuss.google.dev/u/mountaincode2)\
**Post date:** [August 29, 2024, 11:14am UTC](https://discuss.google.dev/t/unable-to-provision-certificate/164442/4 "2024-08-29T11:14:31Z")

</div>

Hi @AI :

i checked in the console and there is the following, however, it is not ending in `goog`:

DNS name: \_acme-challenge.\<domanin.com.\>  
Type: CNAME  
TTL(seconds): 30

What do i need to look for please. can you break it down for me.

---

<div class="post-metadata">

**Author:** ![AI](https://d3byx8b92xw3lq.cloudfront.net/user_avatar/discuss.google.dev/ai/32/212_2.png) [@AI](https://discuss.google.dev/u/AI)\
**Post date:** [August 29, 2024, 3:20pm UTC](https://discuss.google.dev/t/unable-to-provision-certificate/164442/5 "2024-08-29T15:20:22Z")

</div>

what is the value for that record? that’s what usually ends with “.goog.”

Go to dnschecker, edit the name of the record (copy the name of the record from Cloud DNS to avoid mistakes) and click Search to verify if the record is publicly resolvable.

[https://dnschecker.org/#CNAME/\_acme-challenge.yourdomain.com](https://dnschecker.org/#CNAME/_acme-challenge.yourdomain.com).

---

<div class="post-metadata">

**Author:** ![mountaincode2](https://d3byx8b92xw3lq.cloudfront.net/user_avatar/discuss.google.dev/mountaincode2/32/4230_2.png) [@mountaincode2](https://discuss.google.dev/u/mountaincode2)\
**Post date:** [August 30, 2024, 7:44am UTC](https://discuss.google.dev/t/unable-to-provision-certificate/164442/6 "2024-08-30T07:44:20Z")

</div>

@AI

In DNS checker, i see that the record is publicly resolvable.

and i am able to see that the certificate is active now as well.

But there is one thing that is eluding my understanding and that is in the following step why am i adding the CNAME record to the DNS zone in Cloud DNS. Shouldn’t i also add it to my records in Hostinger from whom i purchased the domain.

[https://cloud.google.com/certificate-manager/docs/deploy-google-managed-dns-auth#cname-record](https://cloud.google.com/certificate-manager/docs/deploy-google-managed-dns-auth#cname-record)

```auto
 

```

---

<div class="post-metadata">

**Author:** ![mountaincode2](https://d3byx8b92xw3lq.cloudfront.net/user_avatar/discuss.google.dev/mountaincode2/32/4230_2.png) [@mountaincode2](https://discuss.google.dev/u/mountaincode2)\
**Post date:** [July 10, 2025, 2:21pm UTC](https://discuss.google.dev/t/unable-to-provision-certificate/164442/7 "2025-07-10T14:21:00Z")

</div>

Update:

I have configured all the steps as shown in

[https://cloud.google.com/certificate-manager/docs/deploy-google-managed-dns-auth#create-cert-dns-auth](https://cloud.google.com/certificate-manager/docs/deploy-google-managed-dns-auth#create-cert-dns-auth)

```auto

 

```

And everything checks out. All the steps show that the certificate map is configured. Yet when i point my browser to the domain, it doesn’t work.

where could i be going wrong.
