Add dide domain to cert#11
Conversation
|
How should this alias be handled by nginx? I'm not too sure what will happen at present when we load a different domain name. Possibly it will load up the daedalus website anyway because there's only one server block on 443. We should make that explicit in the configuration though. I'm not a huge fan of having two names for the same domain tbh. I think it will just lead to confusion (eg. cookies and state when visiting one domain won't be shared with the other one). Or we just make connections to |
|
This came from Rich's observation during the outage, when daedalus.jameel-institute.org was down, but daedalus.dide.ic.ac.uk was viewable - just with the security warning because of name on the cert - in which case, why not just add the alternative name to the SSL cert, using the mechanism we already did for that. The other use case was we wanted both Anyway - it felt like a quick fix, since nginx already responds to both; this change would only add the extra name onto the cert for acme-buddy. But it's not a high priority thing. |
This adds an extra name on the LetsEncrypt, so that the same cert will be valid viewed from either daedalus.jameel-institute.org or daedalus.dide.ic.ac.uk (which are the same machine). Acme-buddy supports this with just comma-separated domains on the --domain argument.