-
-
Notifications
You must be signed in to change notification settings - Fork 5.2k
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
Disable acme for non https endpoints #989
Comments
Can you provide a sample of your traefik.toml? |
Traefik Config defaultEntryPoints = ["http", "https"]
[entryPoints]
[entryPoints.http]
address = ":80"
[entryPoints.https]
address = ":443"
[entryPoints.https.tls]
[acme]
email = "hostmaster@example.com"
storage = "/etc/traefik/acme.json"
entryPoint = "https"
acmeLogging = true
OnHostRule = true
[docker]
endpoint = "unix:///var/run/docker.sock"
watch = true
exposedbydefault = true Sample Docker run docker run \
--name www \
--network public \
-l "traefik.frontend.rule=Host:test.example.com,88.99.77.66" \
-l "traefik.frontend.entryPoints=http" \
-l traefik.port=8043 \
-v /opt/www:/srv/http \
pierrezemb/gostatic --forceHTTP Treafik prints now errors acquiring a Certificate for 88.99.77.66. |
I have exactly the same issue with the same kind of configuration. I also tried with the label Is there a workaround to have the choice between HTTP/HTTPS according to the frontends? |
Don't fetch ACME certificates for frontends using non-TLS entrypoints (#989)
Fixed by #1023 |
I use acme with
OnHostRule=true
to aquire lets encrypt certs but treafik requests certs for Host-Rules matching only onhttp
Entrypoint. I would expect a host-rule filtering to the[acme] entryPoint
The text was updated successfully, but these errors were encountered: