• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Issue Let's Encrypt Attempting to use HTTP instead of DNS Challenge for wildcard

fjl3

New Pleskian
Server operating system version
Windows Server 2022
Plesk version and microupdate number
Plesk Obsidian 18.0.47
Hello. I was trying to renew a certificate in Plesk using Let's Encrypt and it is giving me the error and it is giving me the following error:
Could not request a Let's Encrypt SSL/TLS certificate for pizzamandans.com.

Go to http://domain.tld/.well-known/acme-challenge/2JXPo2rck390xWfdXScC7zfCA11tX-vxuIaLwnTLq7o

and сheck if the authorization token is available.
Previously when issuing certificates it would present me with an image that says to add a DNS record, which I would do and everything would run smoothly.
I ended up removing the certificate and attempting to issue a new one, but receive the same incorrect challenge method.
Is there a setting to force Let's Encrypt to use the DNS challenge?
 
I see many other people posting about the same (or very similar) issue but don't see any solutions. So I'm not sure there is a solution, but I'm hopeful.
 
Back
Top