Endless 502 / forwarding when calling dashboard via subdomain #6123

Traefik Traefik v2
,
14

so https works :partying_face: :partying_face: :partying_face: :partying_face: :partying_face:
and I think I understood how that all works :slight_smile:.
@ldez can you tell me what app you use for the drawings?

my config

Treafik dynamic config

# https://stackoverflow.com/questions/49718431/docker-compose-yml-file-naming-convention
version: "3.7"

services:
  traefikV2:   
    # The official v2.0 Traefik docker image
    #image: traefik:latest 
    #image: traefik:v2.0
    image: traefik:v2.1.1
    container_name: traefik
    #command: 
    ## to work with custom traefik configuration file you have to declare the local path and mount the location on the host, see volume section
    #- --configFile=/etc/traefik/traefik-config.yaml
    
    ports:
      # The HTTP port
      - 80:80
      # The HTTPS port
      - 443:443
      # The Web UI (enabled by --api.insecure=true)
      #- "8080:8080"
    
    volumes:         
    # syntax --> host-location:path-in-container, see https://docs.docker.com/compose/compose-file/#volumes
      # So that Traefik can listen to the Docker events
      - /var/run/docker.sock:/var/run/docker.sock
      # mount the location for the log files to the host, so that I can read them on the host
        # chosen based on https://unix.stackexchange.com/questions/104936/where-are-all-the-posibilities-of-storing-a-log-file
      - /var/log/traefik:/var/log
      # mount the location for the certifcates to the host, so that I can read them on the host
        #based on https://www.getpagespeed.com/server-setup/ssl-directory and https://serverfault.com/questions/62496/ssl-certificate-location-on-unix-linux
      - /etc/ssl/certs/traefik/letsencrypt:/etc/ssl/certs/letsencrypt
      # I use a customized "traefik.toml", so it has to be mounted into the traefik container (or stored there), combine 
        # https://stackoverflow.com/questions/47382756/why-is-my-traefik-toml-file-not-be-read-by-docker-compose-configuration
        # https://stackoverflow.com/questions/57200728/can-the-default-location-of-the-traefik-configuration-file-be-changed-in-the-off
        # https://stackoverflow.com/questions/45902133/how-to-use-custom-traefik-toml-file
        # https://docs.traefik.io/getting-started/configuration-overview/
      - /opt/traefik/traefik-config.yaml:/etc/traefik/traefik.yaml
    
    labels:
      - traefik.enable=true
      #- "traefik.docker.network=bridge_proxy_traefikv2"
      
      #---HTTP ROUTER SECTION
      - traefik.http.routers.traefik_dashboard.rule=Host(`traefik.fairbnb.community`)
      - traefik.http.routers.traefik_dashboard.service=api@internal
      
         #---HTTP SECTION
      -  traefik.http.routers.traefik_dashboard.entrypoints=web
      -  traefik.http.routers.traefik_dashboard.middlewares=traefik_dashboard_redirect2https      
      #-  traefik.http.services.traefik_dashboard-service.loadBalancer.server.port=8080
      
      #---HTTPS ROUTER SECTION
      - traefik.http.routers.traefik_dashboard_secure.rule=Host(`traefik.fairbnb.community`)
      - traefik.http.routers.traefik_dashboard_secure.service=api@internal
           
         #---HTTPS SECTION
      -  traefik.http.routers.traefik_dashboard_secure.entrypoints=websecure      
      
         #---TLS SECTION
      -  traefik.http.routers.traefik_dashboard_secure.tls.certresolver=tlsChallenge_letsencrypt
      
      #---MIDDLEWARE SECTION redirect http to https
      - traefik.http.middlewares.traefik_dashboard_redirect2https.redirectscheme.scheme=https

    networks:
      - traefik

      
networks:
  traefik:
    external:
      name: bridge_proxy_traefikv2

Treafik Static Config

global:
  checkNewVersion: true
entryPoints:
  web:
    address: :80
  websecure:
    address: :443

api:
   debug: true

providers:
  docker:
    exposedByDefault: false
    network: bridge_proxy_traefikv2

log:
  level: DEBUG
  filePath: /var/log/traefik-log.log

accessLog:
  filePath: /var/log/traefik-access.log

certificatesResolvers:
  tlsChallenge_letsencrypt:
    acme:
      email: my.secret@gmail.com
      storage: /etc/ssl/certs/letsencrypt/acme.json
      tlsChallenge: {}