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

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