Add Let's Encrypt Support to Plesk *.domain addresses
The new wildcard SSL support for Let's Encrypt is awesome!
Except that it doesn't work the way a person would expect. For example, when I install a SSL from GoDaddy, I can click my "exampledomain.com" button, and add the SSL. Then I can click my " *.exampledomain.com" button, and add the SSL.
This currently does not work with Let's Encrypt. With LE, I can click into "exampledomain.com" and set up a "*.exampledomain.com " Let's Encrypt SSL. It will properly secure exampledomain.com .
BUT, when I go to the "*.exampledomain.com" in Plesk, and click "Hosting Settings", I cannot select the *. Let's Encrypt SSL that I just created. Therefore, none of my subdomains are secured by the wildcard SSL that is supposed to secure all subdomains.
This really doesn't make any sense. I was informed by support that you have to create a named subdomain for each subdomain I wish to use. But that defeats the purpose of a wildcard SSL ... because if I am going to do that, I could just as easily set up an individual Let's Encrypt for each subdomain.
David Lorimer
shared this idea
-
DCTS Solutions
commented
I need subdomains supported as I prefer to go w them over making a whole another account, OCD part of me wants it's that way. Would be great to have subdomains secure easier vs making a whole another account just get an SSL. So i agree. Voted up.
-
Brainforge.UK
commented
Let's Encrypt secures the following domans
mydomain.com
www.mydomain.com
webmail.mydomain.com
aliasformydomain.comHowever, it does not encrypt www.aliasformydomain.com
Get certificate error in browserJust seen https://support.plesk.com/hc/en-us/articles/213372009
Known bug - fix some time in future ...
Well if it gets some votes maybe sooner rather than later! -
Julian Bonpland
commented
When a new sub domain is created it does not inherit the Let's Encrypt certificate issued for the main domain. Domains > subdomain.example.com > Hosting Settings > Certificate shows as None selected.
If the main domain has the option "Issue a wildcard SSL/TLS certificate" enabled, this certificate could be easily assigned to the new sub domain on creation instead of having to go to subdomain > Hosting settings and selecting it manually.