webmail subdomain is protected by Let's encrypt for domains but not for alias domains
If I have an ALIAS domain example.com, then
webmail.example.com is created, but there is no certificate for it
3
votes
Anonymous
shared this idea
Thank you for your input. We will consider this functionality in upcoming releases if it is popular. Everyone, please continue voting for this feature if you consider it important.
—
IG
-
Anonymous
commented
Currently when an alias domain is created, the webmail subdomain of this alias domain is not included in the Let's Encrypt certificate. That results in:
http://webmail.example.com being accessible but not safe (http)
https://webmail.example.com not being accessible (certificate error)This should be fixed, since it is a security risk. Also there should be a 301 redirection.