[GH-ISSUE #6] traefik-manager config directory issues. #6

New issue

Closed

opened 2026-05-06 12:22:34 +02:00 by BreizhHardware · 3 comments

BreizhHardware commented

2026-05-06 12:22:34 +02:00

Owner

Originally created by @arcoast on GitHub (Mar 28, 2026).
Original GitHub issue: https://github.com/chr0nzz/traefik-manager/issues/6

Originally assigned to: @chr0nzz on GitHub.

Great project and looks fantastic, thanks for making this. A few issues I've found using it.

Traefik Manager is configured as such

    traefik-manager:
        image: ghcr.io/chr0nzz/traefik-manager:latest
        container_name: traefik-manager
        networks:
            - traefik
        # ports:
        #     - 5000:5000
        environment:
            - COOKIE_SECURE=true
            - CONFIG_DIR=/app/config/dynamic
            - AUTH_ENABLED=false
            - DOMAINS=${DOMAIN}
            - CERT_RESOLVER=cloudflare
        volumes:
            # Required
            - ${DEPLOY}/traefik/configs:/app/config/dynamic
            - ${CONFIG}/traefik/traefik-manager/config:/app/config
            - ${CONFIG}/traefik/traefik-manager/backups:/app/backups
            # Optional monitoring
            - ${CONFIG}/traefik/traefik/acme.json:/app/acme.json:ro
            - ${CONFIG}/traefik/traefik/logs/access.json:/app/logs/access.log:ro
        restart: unless-stopped
        labels:
            - "traefik.enable=true"
            - "traefik.docker.network=traefik"
            - "traefik.http.services.traefik-manager.loadbalancer.server.port=5000"
            - "traefik.http.routers.traefik-manager.entrypoints=websecure"
            - "traefik.http.routers.traefik-manager.rule=Host(`traefik-manager.${DOMAIN}`)"
            - "traefik.http.routers.traefik-manager.middlewares=authelia@file, securityHeaders@file"

However my dynamic config files are organised as such, with subdirectories for separation.

├── configs
│   ├── adguard-lxc.yaml
│   ├── fluidd.yaml
│   ├── middleware
│   │   ├── authelia.yaml
│   │   ├── nextcloud-redirect.yaml
│   │   ├── nextcloud-secure-headers.yaml
│   │   └── securityHeaders.yaml
│   ├── nano-kvm.yaml
│   ├── site-2
│   │   ├── adguard.yaml
│   │   └── router.yaml
│   ├── switch.yaml
│   └── nas.yaml

I've come across three issues:

traefik-manager will only pick up configs ending in .yml NOT .yaml
traefik-manager will not pick up configs in the subdirs - middleware & site-2
When editing a route, my entrypoint is websecure but traefik-manager will ignore this and automatically save as https breaking the config.

Originally created by @arcoast on GitHub (Mar 28, 2026). Original GitHub issue: https://github.com/chr0nzz/traefik-manager/issues/6 Originally assigned to: @chr0nzz on GitHub. Great project and looks fantastic, thanks for making this. A few issues I've found using it. Traefik Manager is configured as such ```yaml traefik-manager: image: ghcr.io/chr0nzz/traefik-manager:latest container_name: traefik-manager networks: - traefik # ports: # - 5000:5000 environment: - COOKIE_SECURE=true - CONFIG_DIR=/app/config/dynamic - AUTH_ENABLED=false - DOMAINS=${DOMAIN} - CERT_RESOLVER=cloudflare volumes: # Required - ${DEPLOY}/traefik/configs:/app/config/dynamic - ${CONFIG}/traefik/traefik-manager/config:/app/config - ${CONFIG}/traefik/traefik-manager/backups:/app/backups # Optional monitoring - ${CONFIG}/traefik/traefik/acme.json:/app/acme.json:ro - ${CONFIG}/traefik/traefik/logs/access.json:/app/logs/access.log:ro restart: unless-stopped labels: - "traefik.enable=true" - "traefik.docker.network=traefik" - "traefik.http.services.traefik-manager.loadbalancer.server.port=5000" - "traefik.http.routers.traefik-manager.entrypoints=websecure" - "traefik.http.routers.traefik-manager.rule=Host(`traefik-manager.${DOMAIN}`)" - "traefik.http.routers.traefik-manager.middlewares=authelia@file, securityHeaders@file" ``` However my dynamic config files are organised as such, with subdirectories for separation. ``` ├── configs │ ├── adguard-lxc.yaml │ ├── fluidd.yaml │ ├── middleware │ │ ├── authelia.yaml │ │ ├── nextcloud-redirect.yaml │ │ ├── nextcloud-secure-headers.yaml │ │ └── securityHeaders.yaml │ ├── nano-kvm.yaml │ ├── site-2 │ │ ├── adguard.yaml │ │ └── router.yaml │ ├── switch.yaml │ └── nas.yaml ``` I've come across three issues: 1. traefik-manager will only pick up configs ending in `.yml` NOT `.yaml` 2. traefik-manager will not pick up configs in the subdirs - `middleware` & `site-2` 3. When editing a route, my entrypoint is `websecure` but traefik-manager will ignore this and automatically save as `https` breaking the config.

BreizhHardware

2026-05-06 12:22:34 +02:00

closed this issue
added the
bug
label

BreizhHardware commented

2026-05-06 12:22:36 +02:00

Author

Owner

@chr0nzz commented on GitHub (Mar 28, 2026):

Thanks for the detailed report - all three issues are fixed and will be included in the next release (v0.7.0).

.yaml extension support - CONFIG_DIR now globs for both *.yml and *.yaml files.
Subdirectory scanning - CONFIG_DIR now scans recursively, so files in middleware/, site-2/, or any nested subdirectory are discovered automatically.
Entry point preservation - Entry points set in the Add/Edit route form (e.g. websecure) are now correctly written to the config. Previously the value from the form was ignored and https was always hardcoded on save.

@chr0nzz commented on GitHub (Mar 28, 2026): Thanks for the detailed report - all three issues are fixed and will be included in the next release (v0.7.0). 1. .yaml extension support - CONFIG_DIR now globs for both *.yml and *.yaml files. 2. Subdirectory scanning - CONFIG_DIR now scans recursively, so files in middleware/, site-2/, or any nested subdirectory are discovered automatically. 3. Entry point preservation - Entry points set in the Add/Edit route form (e.g. websecure) are now correctly written to the config. Previously the value from the form was ignored and https was always hardcoded on save.

BreizhHardware commented

2026-05-06 12:22:36 +02:00

Author

Owner

@chr0nzz commented on GitHub (Mar 29, 2026):

v0.7.0 is out, please report back if all is working as expected. thanks

@chr0nzz commented on GitHub (Mar 29, 2026): v0.7.0 is out, please report back if all is working as expected. thanks

BreizhHardware commented

2026-05-06 12:22:36 +02:00

Author

Owner

@arcoast commented on GitHub (Mar 30, 2026):

Yep, that's got it all fixed up. Thanks so much!

@arcoast commented on GitHub (Mar 30, 2026): Yep, that's got it all fixed up. Thanks so much!