• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Question SSL - Multiple Domain

MartinPl

New Pleskian
Hello everyone,


i use plesk for multiple domains on one IP. My domains and subdomain (webmail) have received a certificate from letsencrypt plugin.

How can I create for each individual mailserver a own certificate? many thanks


currently it looks like this:

https://www.domain1.com -> OK

https://webmail.domain1.com -> OK

mailserver: mail.domain1.com -> NOT OK (default certificate)

IP: 1.2.3.4


https://www.domain2.com -> OK

https://webmail.domain2.com -> OK

mailserver: mail.domain2.com -> NOT OK (default certificate)

IP: 1.2.3.4


Plesk Onyx 17.5.3
 
A virtual hosting solution for mail services (smtp, pop, imap) is being worked on and will be made available in the next version of Plesk.
 
Hi.
When does this version appear?
Then is it possible to create for each domain a separate certificate with letsencrypt?
 
Hi.
When does this version appear?
I don't know, someone else may answer that.
Then is it possible to create for each domain a separate certificate with letsencrypt?
Yes it does.
Personally I'm not interested in it as it will only be supported by modern mail clients that support SNI.
I have a working solution (needs a wildcard) that works for all mail clients.
As I have long-term client relationships I don't want to alter the "naming policy" every 3 or 4 years.
The one I have is future-proof AND supports older mail clients (which don't need to be that old to fail).

I also don't trust the dynamical nature of LetsEncrypt certificates for something as trivial as mail.
My clients never had to pay anything extra for suddenly having the possibility to have a https-site.
If it fails in the future I have a "decent story to tell" to explain the outage.
I can't tell a decent story if it starts to fail securing the mail.
 
Back
Top