Hey, I'm running Traefik in Docker as a local reverse proxy behind a Hetzner Load Balancer but for some reason it stops being available when adding
--entryPoints.http.forwardedHeaders.trustedIPs="127.0.0.1/8,167.199.11.64,162.66.156.232"
to the follow command. On detail:
in docker run --name traefik --detach --restart unless-stopped --publish 80:80 --volume /var/run/docker.sock:/var/run/docker.sock --env-file .kamal/env/traefik/traefik.env --log-driver "awslogs" --log-opt awslogs-region="eu-central-1" --log-opt awslogs-group="/myservice/api" --log-opt awslogs-create-group="true" --log-opt tag="{{.Name}}-{{.ID}}" --volume "/var/run/datadog:/var/run/datadog" botbrains/traefik:v2.10 --providers.docker --log.level="DEBUG" --accesslog="true" --entryPoints.http.forwardedHeaders.trustedIPs="127.0.0.1/8,167.199.11.64,162.66.156.232" --tracing.datadog.localAgentSocket="/var/run/datadog/apm.socket" --metrics.datadog.address="127.0.0.1:8125" --metrics.datadog.addRoutersLabels="true" --metrics.datadog.prefix="traefik"
My containers are started with
--label traefik.http.services.api-web-staging.loadbalancer.server.scheme="http" --label traefik.http.routers.api-web-staging.rule="PathPrefix(`/`)" --label traefik.http.middlewares.api-web-staging-retry.retry.attempts="5" --label traefik.http.middlewares.api-web-staging-retry.retry.initialinterval="500ms" --label traefik.http.routers.api-web-staging.middlewares="api-web-staging-retry@docker"
Even adding
--entryPoints.http.forwardedHeaders.insecure="true" will also result in traefik not being accessible.
Any Idea where this fails?
Thanks you a lot.