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
![](https://secure.gravatar.com/avatar/b129c1b34f4ce29a788ef6ebeea908ef?size=40&default=https%3A%2F%2Fassets.uvcdn.com%2Fpkg%2Fadmin%2Ficons%2Fuser_70-6bcf9e08938533adb9bac95c3e487cb2a6d4a32f890ca6fdc82e3072e0ea0368.png)
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.