After many, many hours I have a working traefik v2 setup with docker where traefik is providing letsencrypt https services for an nginx docker container and for a simple web server on a different physical host on the same LAN as the Docker host. It works well. Requests to exp.example.com go to the nginx Docker container and moodle.example.com go to the test server (without native HTTPS). The dynamic.yaml file is below.
http: middlewares: redirect: redirectScheme: scheme: https # Below is for the external server http: routers: moodle-rtr: entryPoints: - web-secured rule: Host(`moodle.example.com`) service: moodle-svc tls: certresolver: mytlschallenge services: moodle-svc: loadBalancer: passHostHeader: true servers: - url: 'http://192.168.199.22:80'
What I really want is to use my existing moodle server which is already setup for https and which currently is not behind a proxy of any kind. (the building router points all port 80 and 443 traffic to this server).
Is it possible to have traefik merely act as a router for this one specific server and not have it redirect to 443? In other words to have traffic to/from the moodle.example.com server pass through in both directions transparently so that the moodle server can continue with its own https/certificate setup and have traefik deal with all the docker container https/certificate business?