hosting_le can't add aliases as SAN's to an LE certificate, because the redirect breaks the lets encrypt validation process.
This issue could be prevented by allowing access to the acme-challenge folder from the redirect vhosts, while still redirecting all other traffic to the target domain.
However, as it stands, there is no hook to allow modification of that part of the config file.

As this prevents the generation of valid certificates for other aliases, this makes server side redirection effectively unusable in combination LE (it will always present certificate warnings when using it with https).

Comments

Kaz de Groot created an issue. See original summary.

colan’s picture

Status: Active » Closed (won't fix)

hosting_le was meant as a workaround, and will not be supported in the long-term. Please try Aegir HTTPS instead (which will be supported), and report this issue there if it's still a problem (assuming it's not reported there already). Thanks!