# Problem issuing new certificate

**URL:** <https://community.letsencrypt.org/t/problem-issuing-new-certificate/134529>\
**Category:** Help\
**Created:** [September 25, 2020, 3:02pm UTC](https://community.letsencrypt.org/t/problem-issuing-new-certificate/134529 "2020-09-25T15:02:16Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![aberbuddha](https://avatars.discourse-cdn.com/v4/letter/a/c57346/32.png) [@aberbuddha](https://community.letsencrypt.org/u/aberbuddha)\
**Post date:** [September 25, 2020, 3:02pm UTC](https://community.letsencrypt.org/t/problem-issuing-new-certificate/134529/1 "2020-09-25T15:02:16Z")

</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:paraglide.co.uk

I ran this command: Let's debug found All OK!  
OK  
No issues were found with [paraglide.co.uk](http://paraglide.co.uk).

It produced this output:Could not issue an SSL/TLS certificate for [paraglide.co.uk](http://paraglide.co.uk)  
Details  
Could not issue a Let's Encrypt SSL/TLS certificate for [paraglide.co.uk](http://paraglide.co.uk). Authorization for the domain failed.

Details  
Invalid response from [https://acme-v02.api.letsencrypt.org/acme/authz-v3/7439420892](https://acme-v02.api.letsencrypt.org/acme/authz-v3/7439420892).

Details:

Type: urn:ietf:params:acme:error:dns

Status: 400

Detail: DNS problem: NXDOMAIN looking up TXT for \_acme-challenge.paraglide.co.uk - check that a DNS record exists for this domain

My web server is (include version):

The operating system my web server runs on is (include version):CentOS Linux 7.8.2003 (Core)

My hosting provider, if applicable, is:ionos1&1

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

I'm using a control panel to manage my site (no, or provide the name and version of the control panel):Plesk Obsidian  
Version 18.0.30 Update #1, last updated on Sept 22, 2020 06:03 AM

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

---

<div class="post-metadata">

**Author:** ![JuergenAuer](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/juergenauer/32/26491_2.png) [@JuergenAuer](https://community.letsencrypt.org/u/JuergenAuer)\
**Post date:** [September 25, 2020, 3:49pm UTC](https://community.letsencrypt.org/t/problem-issuing-new-certificate/134529/2 "2020-09-25T15:49:55Z")

</div>

Hi @aberbuddha

> [@aberbuddha](#):
>
> I'm using a control panel to manage my site (no, or provide the name and version of the control panel):Plesk Obsidian

if you use Plesk and if the Plesk integrated ACME client doesn't work, please ask your hoster.

It's the job of your hoster to support Plesk.

---

<div class="post-metadata">

**Author:** ![aberbuddha](https://avatars.discourse-cdn.com/v4/letter/a/c57346/32.png) [@aberbuddha](https://community.letsencrypt.org/u/aberbuddha)\
**Post date:** [September 25, 2020, 5:09pm UTC](https://community.letsencrypt.org/t/problem-issuing-new-certificate/134529/3 "2020-09-25T17:09:14Z")

</div>

Thanks for the reply, I manually uploaded a TXT record and it is working now, but it should work automatically with ACME?

---

<div class="post-metadata">

**Author:** ![JuergenAuer](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/juergenauer/32/26491_2.png) [@JuergenAuer](https://community.letsencrypt.org/u/JuergenAuer)\
**Post date:** [September 25, 2020, 5:18pm UTC](https://community.letsencrypt.org/t/problem-issuing-new-certificate/134529/4 "2020-09-25T17:18:03Z")

</div>

> [@aberbuddha](#):
>
> but it should work automatically with ACME?

Yes, it should. Why? I don't know. Your hoster has to fix that.

---

<div class="post-metadata">

**Author:** ![griffin](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/griffin/32/50204_2.png) [@griffin](https://community.letsencrypt.org/u/griffin)\
**Post date:** [September 25, 2020, 9:15pm UTC](https://community.letsencrypt.org/t/problem-issuing-new-certificate/134529/5 "2020-09-25T21:15:19Z")

</div>

Welcome to the Let's Encrypt Community, Steve 🙂

It looks to me like your TXT record is fully accessible:  
\_acme-challenge.paraglide.co.uk. 3599 IN TXT "9FXRznl0VKD\_xfseqMQlQTFnvOaUN14PbLRjCJ5BIgc"

It's possible that the record just had not yet propagated when you tried to authenticate. You sometimes need to delay a bit. You can use the following tool to see if a record currently exists:

> **[Dig (DNS lookup)](https://toolbox.googleapps.com/apps/dig/#TXT/)**

If you have more questions, I'm happy to help. Here's some official documentation if you want some reference materials:

* * *

[Getting Free SSL/TLS Certificate from Let’s Encrypt](https://docs.plesk.com/en-US/obsidian/administrator-guide/website-management/websites-and-domains/advanced-website-security/securing-connections-with-ssltls-certificates/getting-free-ssltls-certificate-from-let%E2%80%99s-encrypt.77233/)

* * *

> **[How to install an SSL certificate for a domain in Plesk (Let's Encrypt /...](https://support.plesk.com/hc/en-us/articles/213946825-How-to-install-an-SSL-certificate-for-a-domain-in-Plesk-Let-s-Encrypt-other-certificate-authorities-)**
>
> Applicable to:
> 
> Plesk for Linux
> Plesk for Windows
> 
> 
> Question
> How to install an SSL certificate for a domain in Plesk?
> Answer
>  
> 
> Securing a domain with a free Let's Encrypt certificate (Plesk Onyx a...

---

<div class="post-metadata">

**Author:** ![griffin](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/griffin/32/50204_2.png) [@griffin](https://community.letsencrypt.org/u/griffin)\
**Post date:** [September 25, 2020, 9:24pm UTC](https://community.letsencrypt.org/t/problem-issuing-new-certificate/134529/6 "2020-09-25T21:24:35Z")

</div>

Congratulations! You got your certificate! 🥳

 ![Screenshot_20200925-152601_Samsung Internet](https://global.discourse-cdn.com/letsencrypt/original/3X/b/6/b6ba348700c2ae1e0e45f8205e8f9965e3c47862.jpeg)

 ![Screenshot_20200925-152111_Samsung Internet](https://global.discourse-cdn.com/letsencrypt/original/3X/2/e/2e53d0e76802a258a39818ce8b2de3bd1be7172c.jpeg)

---

<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:** [October 25, 2020, 9:24pm UTC](https://community.letsencrypt.org/t/problem-issuing-new-certificate/134529/7 "2020-10-25T21:24:38Z")

</div>

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