Skip to content

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

Closed
CarlosTorrecillas opened this issue Jul 31, 2019 · 6 comments
Closed

Support for multiple domains under the same container #562

CarlosTorrecillas opened this issue Jul 31, 2019 · 6 comments
Labels
kind/letsencrypt Issue, question or PR regarding Let's Encrypt

Comments

@CarlosTorrecillas
Copy link

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!

@CarlosTorrecillas
Copy link
Author

Actually, reading the email again I can see:

For details about when we send these emails, please visit https://letsencrypt.org/docs/expiration-emails/. In particular, note that this reminder email is still sent if you've obtained a slightly different certificate by adding or removing names. If you've replaced this certificate with a newer one that covers more or fewer names than the list above, you may be able to ignore this message.

Which is my case because I added api.domain3.com recently. I assume that's why

@buchdag buchdag added the kind/letsencrypt Issue, question or PR regarding Let's Encrypt label Aug 7, 2019
@buchdag
Copy link
Member

buchdag commented Aug 7, 2019

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?

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.

Which is my case because I added api.domain3.com recently. I assume that's why

Most probably.

@maxnoe
Copy link

maxnoe commented Feb 21, 2020

How would a config for this look like?

@Mesqualito
Copy link

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!

@buchdag
Copy link
Member

buchdag commented Sep 27, 2020

@Mesqualito wildcard certificates aren't supported : #319

@buchdag buchdag closed this as completed Dec 26, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/letsencrypt Issue, question or PR regarding Let's Encrypt
Projects
None yet
Development

No branches or pull requests

4 participants