• Please be aware: Kaspersky Anti-Virus has been deprecated
    With the upgrade to Plesk Obsidian 18.0.64, "Kaspersky Anti-Virus for Servers" will be automatically removed from the servers it is installed on. We recommend that you migrate to Sophos Anti-Virus for Servers.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Issue Lets Encrypt not using DNS-01 for wildcard cert

JoeShmoe

New Pleskian
Did something change?
I'm pretty sure wildcard certs used DNS-01 challenge, but recently I started getting an error every time that it tried the acme challenged (and failed, since I block it on the firewall).
How can I force it to use DNS-01? I'm using external DNS.
Getting:
Code:
Invalid response from https://acme-v02.api.letsencrypt.org/acme/authz-v3/xxxxxxxxxxxxxx
Details:
Type: urn:ietf:params:acme:error:connection
Status: 400
Detail: Fetching http://example.com/.well-known/acme-challenge/xxxxxxxxxxxxxxxxxx: Timeout during connect (likely firewall problem)

Plesk Obsidian v18.0.40_build1800211119.12 os_Ubuntu 18.04
Let's Encrypt 2.13.8-744
 
I am facing the same issue. suddenly on one domain I try to issue a wildcard SSL certificate and it doesn't use DNS-01 challenge but HTTP-01 . I tried removing the SSL, adding it back but nothing changes. I select to install wildcard SSL and I get bellow error since the website is not hosted on the server but on shopify.

Code:
Could not issue an SSL/TLS certificate for mydomain.tld
Details
Could not request a Let's Encrypt SSL/TLS certificate for mydomain.tld



Go to http://mydomain.tld/.well-known/acme-challenge/kaR6i-RbsEJ6HHAqloMqQHoajWWwbR1JFYI1xlCzxNs

and сheck if the authorization token is available.

If it is, try to request the certificate again. If the token is not available, there may be an issue with your DNS configuration.

Your domain in Plesk is hosted on the IP address(es): {{my-server-ip}}, but the DNS challenge used another IP: 23.227.38.32.

Make sure that the IP address(es) specified in the domain's DNS zone match the IP address(es) the domain is hosted on.
 
Back
Top