- Shipped
- October 18, 2026 at 8:14 PM UTC
- Author
- Kamo
- Commit
- 7450b9d
Since 2026.10, Home Assistant migrates a YAML `http:` to its storage once, as a PENDING config. It reverts that config and restarts unless an admin promotes it within 5 minutes, and it ignores the YAML afterwards. The first boot did exactly that: five minutes in, HA dropped use_x_forwarded_for, and every request through Traefik got a 400. configuration.yaml loses `http:`. first-run.py, which runs in the pod, now does the whole first run: - onboarding, or a sign-in as sajon when an owner already exists; - location and units; - `http/config/configure` with the proxy settings. Its `promote` mode runs only after /api/ has answered 401 through Traefik. Live: stable holds use_x_forwarded_for, trusted_proxies 10.42.0.0/16 and bans after 10 failures, with nothing pending. Sign-in as sajon through Traefik returns 123 entities, and only HA's system token remains.