the traefik-init service attempts to write static configuration (entrypoints and redirections) into a dynamic file provider.
but the issue is that Traefik apparently does not support defining address or redirections within the providers.file scope.
additionally, the redirection logic in the https block is inverted and uses an invalid top-level YAML key (https: instead of http:).
i had a fresh deployments using TRAEFIK_PROTOCOL=https resulting in 502 Bad Gateway and no error logs were produced.
the workaround was to manually recreate https/dynamic.yml removing the https block and and move the http to https redirect to the static Traefik config.
my environment:
Rocket.Chat: 8.3.1
Traefik: v3.4
Docker Compose: 2.34.0
OS: Debian 12 (Bookworm) on Proxmox LXC
the traefik-init service attempts to write static configuration (entrypoints and redirections) into a dynamic file provider.
but the issue is that Traefik apparently does not support defining address or redirections within the providers.file scope.
additionally, the redirection logic in the https block is inverted and uses an invalid top-level YAML key (https: instead of http:).
i had a fresh deployments using TRAEFIK_PROTOCOL=https resulting in 502 Bad Gateway and no error logs were produced.
the workaround was to manually recreate https/dynamic.yml removing the https block and and move the http to https redirect to the static Traefik config.
my environment:
Rocket.Chat: 8.3.1
Traefik: v3.4
Docker Compose: 2.34.0
OS: Debian 12 (Bookworm) on Proxmox LXC