• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Issue Cannot Issue Let's Encrypt Wildcard

avlza

New Pleskian
Server operating system version
Plesk Obsidian Web Pro Edition
Plesk version and microupdate number
18.0.48
I am having trouble issuing Wildcard SSL via Let's Encrypt.

Code:
Could not issue an SSL/TLS certificate for agents.eifl-loans.com
Details
Could not issue a Let's Encrypt SSL/TLS certificate for agents.eifl-loans.com. Authorization for the domain failed.

Details
Invalid response from https://acme-v02.api.letsencrypt.org/acme/authz-v3/194668650407.

Details:

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

Status: 400

Detail: DNS problem: NXDOMAIN looking up TXT for _acme-challenge.agents.eifl-loans.com - check that a DNS record exists for this domain

I followed the following troubleshooting steps :

Guide 1 :


Result :
IPv4 Settings is correct.
Added test.txt acme challenge text on file manager, not working.

Guide 2 :

Result :
Issued Wildcard.
Checked via DNS Checker, TXT not available.

--
Side notes :

Added the _acme-challenge both details on Plesk or on Server.
 
Looks like you're using NameCheap for your DNS. In that case, when you're getting a wildcard cert issue, plesk will initially fail the challenge since it needs to present you the DNS record you need to add to your DNS provider (NameCheap in your case).

Since the wildcart cert is being issued to agents.eifl-loans.com, your DNS record will need to look something like this:

1673559650743.png
Please note the host field is the _acme-challenge.agents
 
Back
Top