# No TXT record found

**URL:** <https://community.letsencrypt.org/t/no-txt-record-found/112767>\
**Category:** Help\
**Created:** [February 10, 2020, 5:59am UTC](https://community.letsencrypt.org/t/no-txt-record-found/112767 "2020-02-10T05:59:36Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![carolgann](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/carolgann/32/36996_2.png) [@carolgann](https://community.letsencrypt.org/u/carolgann)\
**Post date:** [February 10, 2020, 5:59am UTC](https://community.letsencrypt.org/t/no-txt-record-found/112767/1 "2020-02-10T05:59:37Z")

</div>

Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. [https://crt.sh/?q=example.com](https://crt.sh/?q=example.com)), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domain is: [https://texasvintageshopper.com/](https://texasvintageshopper.com/)

I ran this command: Issue a new certificate | \*.texasvintageshopper.com

It produced this output:  
There was a problem processing your request

- Error issuing certificate
- Failed to issue certificate
- Updating challenge for [texasvintageshopper.com](http://texasvintageshopper.com): acme: error code 403 “urn:ietf:params:acme:error:unauthorized”: No TXT record found at \_acme-challenge.texasvintageshopper.com (order URL: [https://acme-staging-v02.api.letsencrypt.org/acme/order/8952719/74707076](https://acme-staging-v02.api.letsencrypt.org/acme/order/8952719/74707076))

My web server is (include version): Apache

The operating system my web server runs on is (include version): Intel Xeon E3-1270

My hosting provider, if applicable, is: [https://www.inmotionhosting.com/](https://www.inmotionhosting.com/) Ellte Dedicated Server Plan

I can login to a root shell on my machine (yes or no, or I don’t know): Yes

I’m using a control panel to manage my site (no, or provide the name and version of the control panel): Yes cPanel

The version of my client is (e.g. output of `certbot --version` or `certbot-auto --version` if you’re using Certbot): AutoSSL

---

<div class="post-metadata">

**Author:** ![\_az](https://avatars.discourse-cdn.com/v4/letter/_/22d042/32.png) [@\_az](https://community.letsencrypt.org/u/_az)\
**Post date:** [February 10, 2020, 6:39am UTC](https://community.letsencrypt.org/t/no-txt-record-found/112767/2 "2020-02-10T06:39:44Z")

</div>

Hi,

Since you host your DNS with Cloudflare, you can’t issue a wildcard via the cPanel plugin.

The reason for this is that Let’s Encrypt requires wildcard certificates to prove control via a DNS change, but cPanel lacks the access to your DNS hosting (Cloudflare) to perform that change.

Your options are to not use a wildcard, or alternatively change over your domain’s nameservers to your cPanel nameservers.

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/letsencrypt/original/3X/c/a/ca6c06ea1ea201324bba7048c6841ce60236468d.png) [@system](https://community.letsencrypt.org/u/system)\
**Post date:** [March 11, 2020, 6:39am UTC](https://community.letsencrypt.org/t/no-txt-record-found/112767/3 "2020-03-11T06:39:49Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
