• 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 Failed to connect to the Let's Encrypt server https://acme-v02.api.letsencrypt.org.

DigitalSplendid

Regular Pleskian
Server operating system version
18.0.49
Plesk version and microupdate number
Web Admin Se Edition
Unable to add SSL. Getting this error:

1686560509662.png
 
Please check on the server in a SSH shell the DNS resolving for letsencrypt domain.
nslookup acme-v02.api.letsencrypt.org

Try to repair:
plesk repair dns
 
Instead you could use "service sw-engine restart" etc. But I think the issue is rather caused by a malfunctioning name resolution. Can you show what's in your /etc/resolv.conf file? have you tried switching nameservers to 8.8.8.8 and 8.8.4.4?
 
If by chance this is a windows server running Plesk, make sure in your IIS configuration for that domain that the HSTS option is checked. I've seen on a windows server with Plesk, this option become un-sync'd from the HSTS option in Plesk and cause this exact error. If not windows, try toggling the HSTS option on and off for this domain in Plesk.
 
Back
Top