• 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.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Issue Let's Encrypt not for alias???

mr-wolf

Silver Pleskian
Plesk Guru
I just upgraded to Plesk Onyx and I'm checking out the "Let's Encrypt" feature. Already I noticed there's no automated method to install an SSL-certificate for the webmail.

Just now I discovered it also doesn't work for the alias.
I've setup a website for 2 domains, but the certificate is only issued/installed for the primary domain.
Its alias doesn't get a seperate SSL-certificate.

It would be a great enhancement if this gets added.

Cheers


PS (can this post be moved to the Onyx thread?)
 
Wrong: "Not a Plesk issue. It is technically not possible to do this with Let's Encrypt. Let's Encrypt provides single-domain certificates, and in an Apache virtual host, an alias is an additional domain name while the virtual host can only have exactly one certificate. The only solution would be to have a certificate that incorporates the main domain of the account plus the alias domain, but that is something that Let's Encrypt authority does not offer and has no plans for."

Edit: I was wrong. According to https://support.plesk.com/hc/en-us/articles/213372009 it can be done manually, and the information I had from Let's Encrypt was on wildcard certificates, not on incorporating several domains in a single certificate. Sorry for that. The current Let's Encrypt extension does not support putting more domains into the certificate, but a manual solution is possible.
 
Last edited:
Hi Peter,

I don't know much about let's encrypt, but I do know that I have subdomains installed on Plesk which got their own certificate. Maybe it just needs a separate request for those?

On the technical side...
I can manually solve it, so why wouldn't Plesk be able to? In nginx I could create a double entry with separate certificates with the alias as a "server name" entry. The apache entry could stay the same. For apache it would be an alias and for nginx a separate entry with the same parameters.
 
Last edited:
I wouldn't say you were wrong.
You were actually very precise and correct in stating that an apache single vhost does not support multiple certificates.
I just want to assign an alias to a domain and let Plesk do the things that give that effect.

BTW I long thought that an alias only affected the main domain. When I needed it for a subdomain I started examining the configs to see if I could make a manual workaround. I then noticed that aliases were also automatically made for subdomains.
 
Back
Top