• 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.
  • 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.
  • The ImunifyAV extension is now deprecated and no longer available for installation.
    Existing ImunifyAV installations will continue operating for three months, and after that will automatically be replaced with the new Imunify extension. We recommend that you manually replace any existing ImunifyAV installations with Imunify at your earliest convenience.

Question Let's Encrypt Extension

UweP

Regular Pleskian
With the Plesk Let's Encrypt Extension can we secure plesk and webmails automatically too? oO
 
You can secure plesk,add host name as own hosting space,than log in to and add lets encrypt SSL as you do for any domain.After that go to tool/server setting and select that SSL as plesk default ssl
 
Just to say ...you can do it even more professional..with just one more IP.Set that IP as dedicated for hostname..than add .htaccess rule to redirect IP to hostname...just in case someone go through Ip...
 
With the Plesk Let's Encrypt Extension can we secure plesk and webmails automatically too? oO

Plesk, yes, webmail, no. You can't use let's encrypt to secure webmail. Its a nice idea, but technically impossible Here is why:

Let's Encrypt don't create wildcards, that not a Plesk issue, Let's encrypt simply don't dont do wildcards. you need a wildcard cert to use the "also secure webmail" feature.

Lets take domain example.com as example
The certificate generated bij Let's Encrypt is for example.com and www.example.com.

The webmail url is always webmail.example.com, the certificate for example.com and www.example.com will give a name mismatch error on subdomain webmail.example.com. There is no way to create a Let's Encrypt certificate for a webmail subdomain because the .well-known can not be read by Let's encrypt.

The only way to use the "also use certificate for webmail" feature, is when you buy a wildcard certificate.

regards
Jan
 
The only way to use the "also use certificate for webmail" feature, is when you buy a wildcard certificate.

Sorry, but this statement is incorrect. Pls. have a look at one of my previous forum posts: => #13
 
Sorry, but this statement is incorrect. Pls. have a look at one of my previous forum posts: => #13

Maybe its technically possible, but not in the real world because this must be run as root, even a user with full ssh access (/bin/bash) can't run this.

-bash-4.1$ plesk bin extension --exec letsencrypt -d linulexhosting.nl
Could not open Repository at "/etc/sw/keys": Cannot open file
Error: must run as root.
exit status 1

The whole point of plesk and something like the Let's Encrypt add-on is that users can do it them self without interference of the sys-admin.

regards
Jan
 
Back
Top