-
Notifications
You must be signed in to change notification settings - Fork 825
Support for multiple domains under the same container #562
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Actually, reading the email again I can see:
Which is my case because I added api.domain3.com recently. I assume that's why |
Yes, the container create SAN certificates, ie single certificates that cover multiple domain names. The actual certificate is named after the first domain (referred to as base domain in the code), the rest are symlinks to it.
Most probably. |
How would a config for this look like? |
Can somebody link to an .env-configuration-file for multiple names (and multiple certificates) for domains which link to one container publishing http/80 or paste an example here? Is a wildcard possible (*.domain.eu covering http://one.domain.eu, https://one.domain.eu, http/https://another.domain.eu, http/https://www.domain.eu, http/https://domain.eu... ) ? Thanks in advance! |
@Mesqualito wildcard certificates aren't supported : #319 |
I'm not sure if this is related to this: #57 but I have a container with multiple domains associated (being api.domain1.com, api.domain2.com, api.domain3.com), and today I got the email saying that all three domains are about to expire the certificate. My question is whether that's something we can achieve using this container. It is the first time I use that structure (normally I have 1-to-1 relationship between a container and a domain but this time is different).
What I see in the certs folder is that all certs refer to the first domain's certs (api.domain1.com in this case). Is that normal/valid?
Many thanks!
The text was updated successfully, but these errors were encountered: