-
Notifications
You must be signed in to change notification settings - Fork 114
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
Create multiple certificates #16
Comments
@alex88 Have you considered deploying a Let's Encrypt stack for the first certificate, and then add new services (or clone and modify) for the following certificates? It may be a lot of work, but it'd be easy to manage in Rancher. |
@zambon that's what I'm doing right now, I'm just wondering what will happen when a new version is released :D we've now 20 instances running |
How about using a single docker containers with the domains in one single variable, with each certificate separated by semicolon and each domain by a comma? Too complex for the user? e.g.:
|
@janeczku That sounds good! Having the option to choose is essential though, as larger deployments may cause the service to run into rate limits. @alex88 I like your idea too. It may be simpler if the catalog used a
BTW @alex88, I don't mean to sidetrack into another conversation, but how to you handle having many certificates? Do you run one (set of) load balancer(s) per stack? (I'm currently using a "global" load balancer in my deployments, which means I need to have a single certificate) |
@zambon I have a single load balancer running on every instance which has a main certificate and multiple others, SNI support is good enough for us, so it sends the right certificate for the right domain |
@janeczku are there multiline textboxes when creating it? The problem comes later when you've to upgrade the env variables and the input is not multiline |
@alex88 good thinking. Is this something you are regulary doing? I mean upgrading the env vars to change the certificates? |
@janeczku I would agree with @zambon, that it is necessary to be able to choose whether to have certificates with SANs or single-domain certificates (for my use-case I'd prefer the certificates with SANs). But the multiline idea would solve that quite well:
Regarding the rate-limits: Since December 2016 there are additional rate limits to the cert per week-limits. The most important one would be
|
I'd like to be able to mix and match single-domain certificates and certificates with SANs. For now I have three separate containers, each with an identical configuration (included shared storage volume) except for the certificate name, domain names, and renewal time. |
How about to get domains list from the load balancer? #67 |
As an alternative I recommend this: https://github.com/adi90x/rancher-active-proxy
Jan Pobořil
https://honza.poboril.cz/
4. 3. 2018 v 6:56, Maximilian Friedmann <notifications@github.com>:
… Any updates on this? I really like the suggestion from @alex88, its how we used to work with the dockercloud & JrCs/docker-letsencrypt-nginx-proxy-companion, but #67 would be the greatest solution!
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Hi there, not sure if i can be done or if it's worth it, but do you have any plans to create multiple certificates instead of having one with multiple hostnames?
I think it could be useful for big projects where a company would like to not expose other services domains in the certificate.
I imagine having the same comma-separated list of domains but instead of having everything in a certificate, use the certificate field as a prefix for the new certificates it's going to create
The text was updated successfully, but these errors were encountered: