Skip to content

Traefik v3.7.1 Startup Failures: Invalid TLS Syntax in Dynamic Configs #135

Description

@SFH008

Summary

Traefik v3.7.1 crashes on startup due to invalid TLS configuration syntax generated by prestart.sh. The dynamic config files use tls: {} on router definitions, which is not valid in Traefik v3.

Root Cause

The prestart.sh script generates YAML files with router-level tls: {} directives:

cockpit.yml: Contains tls: {} on HTTPS routers
localhost-redirect.yml: Contains tls: {} on HTTPS routers
redirect-signalk-server.yml: Contains tls: {} on HTTPS routers
tls-default.yml: Uses invalid syntax for the TLS store definition

Error Messages
{"level":"error","error":"command traefik error: field not found, node: tls","time":"2026-08-08T10:05:34Z","message":"Command error"}

Traefik loops restarting with this error, eventually entering a crash-loop.

Impact
Core services unavailable: Traefik restart failures cascade to Homarr, Authelia, and routing
Signal K on 4430: Not reachable when Traefik is down
TLS entrypoints broken: 443, 4430-4450 all non-functional
Affected Files
/var/lib/container-apps/halos-core-containers/prestart.sh — generates cockpit.yml, localhost-redirect.yml, etc.
/var/lib/container-apps/halos-core-containers/assets/traefik/dynamic/*.yml — static dynamic configs (if still using file provider)
Steps to Reproduce
Fresh HalOS install with Traefik v3.7.1
Start halos-core-containers service
Observe Traefik container looping with "field not found, node: tls" error
Port 80, 443, 4430 remain unreachable

For SKIP, Node Red all are ok but when attempting to use Brineomatic and Forthfet plugins error occurs

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions