Putting Authelia in front of my whole homelab: what worked, what didn’t, and the £0 lesson that nearly undid all of it
Description and use
After rotating secrets, adjusting CDN rules, and pinning the reverse‑proxy IP, the homelab’s single‑sign‑on gateway operates securely and reliably, with clear separation of failure modes between the front door and back‑end services.
Problem
Deploying Authelia as a single sign‑on gateway for a homelab exposed the risk of mis‑configured secrets, edge‑layer blocking, and DHCP lease changes that could bring the entire front door down.
Outcome
After rotating secrets, adjusting CDN rules, and pinning the reverse‑proxy IP, the homelab’s single‑sign‑on gateway operates securely and reliably, with clear separation of failure modes between the front door and back‑end services.
Workflow
- 1. Identify mis‑configured secrets in Authelia config.
2. Stop the Authelia container.
3. Backup the database.
4. Run
authelia storage encryption change-keybefore editing config. 5. Replace placeholder secrets and verify withauthelia check-config. 6. Restart Authelia and health‑check. 7. Test OIDC flow; if JWKS fetch fails, add a browser‑like User‑Agent header to the key‑fetching client. 8. Monitor CDN logs for 403s and adjust bot‑fight rules. 9. Assign a static IP and MAC reservation to the reverse‑proxy host. 10. Update monitoring to distinguish front‑door availability from back‑end services.
Evidence
I had changed some of them. I had not changed these two. And the portal was internet‑facing, behind a CDN, doing real SSO for real services.
The fix was to pass an explicit browser‑like User‑Agent header to the key‑fetching client. One header.
The one running the reverse proxy came back up and DHCP handed it a different IP than the one it always had.
- Record date: 2026-09-13T11:02:03.484Z