Facebook
Twitter
-
If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
CentOS2Alma discussion
Resolved 17.5 Let's Encrypt Error
- Thread starter -FP
- Start date
Just in case you did`nt read it yet, the issue is with Let`s Encrypt: Let's Encrypt Status
U
UFHH01
Guest
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
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
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.
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.
Similar threads
