• 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 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.

Resolved 17.5 Let's Encrypt Error

-FP

New Pleskian
I'm trying to secure a domain for the first time since I upgraded to 17.5 and I'm getting an error. Before 17.5 I secured a few without problems.

Error: Let's Encrypt SSL certificate installation failed: Could not obtain directory: Invalid response: <HTML><HEAD><TITLE>Error</TITLE></HEAD><BODY>
An error occurred while processing your request.<p>
Reference #97.179333b8.1495189859.b2676c2
</BODY></HTML>
.
Status: 504.

The domain is accesible without problems through HTTP. Any ideas?
 
experiencing same, i was thinking something is wrong on my side. This came after today's update, it is not generating any acme challenge, but only this error.
 
Hi @ ALL ,

pls. note the following post => #91

... and pls. consider to check the Let's Encrypt service at: => http://letsencrypt.status.io , if you experince issues/errors/problems as described.


You should consider to remember, that this forum is a PLESK - related forum. If you experience issues/errors/problems with a service that is not at all controlled by Plesk or by your server ( controlled with the help of Plesk components and extensions ), pls. consider to open a thread at: => Home > Forum > General Discussion > Open Topics
 
HI yes, i was able to see same tye threads multiple times, and than you for clearing where to post, as if we got in trouble we just run to open a thread under plesk version as at that time this is what you can remember if you are using a production server :)
 
Of course @UFHH01 is right in that we should look at Let's Encrypt Status (funny it's not https) in the future, but it's quite normal to look at Plesk for this.

They updated their Plesk extension. First of all the automatic upgrade was unsuccessful (just like all the previous LetsEncrypt upgrades) and then after removing the component and installing it again (this always worked thus far) I try to secure my first webmail domain and it fails....

But I'm glad it's working now.
I've always felt a bit embarrased to offer webmail over plain http, although none of our clients ever asked for it.
Webmail is typically something that is used on the road on open wifi-connections from sometimes obscure locations. The content is more privacy sensitive and passwords are being sent that could open up even more access.
It has been always more important than the also nice secure connection of the main website.
 
Back
Top