• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

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