Hi @workasr, the documentation about TLS at the "Router" level is for the "incoming" part of the requests.
As you can read in https://docs.traefik.io/routing/overview/, the Traefik object you're looking for is a "Service" (https://docs.traefik.io/routing/services/), which represents the backend services (e.g. your applications behind traefik).
Depending on the kind of dynamic configuration provider (File, Docker, Kubernetes, etc.), there are different way to re-establish a new SSL/TLS connection to the backend (assuming that your backend service is serving a valid TLS certificate chain. If not, let us know as the certificate or the CA authority has to be provided to Traefik, or TLS connection made insecure with insecureSkipVerify
):
- With file provider, set the
url
directive of theserver
(s) definition tohttps://<ip of backend>:443
for instance - With docker (engine or swarm), set the
server.scheme
label to the valuehttps
:
- "traefik.http.services.myservice.loadbalancer.server.scheme=http"
as per https://docs.traefik.io/routing/providers/docker/#services .