Facebook
Twitter
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:
-
Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring. We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design. If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
-
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!
-
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.
Issue Failed to connect to the Let's Encrypt server https://acme-v02.api.letsencrypt.org.
- Thread starter DigitalSplendid
- Start date
DigitalSplendid
Regular Pleskian
GwenDragon
Basic Pleskian
Please check on the server in a SSH shell the DNS resolving for letsencrypt domain.
Try to repair:
nslookup acme-v02.api.letsencrypt.orgTry to repair:
plesk repair dns
DigitalSplendid
Regular Pleskian
DigitalSplendid
Regular Pleskian
DigitalSplendid
Regular Pleskian
This post suggest restart of sw-engine and sw-cp-server should do the trick: Can't install Let's Encrypt certificate through Plesk after update
Getting this output:
Getting this output:
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.