Skip to content
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

ACME OnDemand ignores entrypoint certificate #672

Closed
dtomcej opened this issue Sep 13, 2016 · 1 comment
Closed

ACME OnDemand ignores entrypoint certificate #672

dtomcej opened this issue Sep 13, 2016 · 1 comment

Comments

@dtomcej
Copy link
Contributor

dtomcej commented Sep 13, 2016

When specifying a wildcard certificate on an HTTPS entrypoint, the OnDemand ACME setting seems to override it, resulting in an LE certificate being generated despite the defined certificate already being present.

Example: *.example.com certificate is defined in [[entryPoints.https.tls.certificates]], but if OnDemand is set, a certificate for bacon.example.com will be requested from LE.

@dtomcej
Copy link
Contributor Author

dtomcej commented Jan 6, 2017

Resolved with #1018

@dtomcej dtomcej closed this as completed Jan 6, 2017
@ldez ldez added the area/acme label Jun 11, 2017
@traefik traefik locked and limited conversation to collaborators Sep 1, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants