Files

dtoro 2762dcbdb8 arch-migration P1: dedicated forward-auth outpost (LXC 106)

- containers/106-auth-outpost.md: new LAN outpost page
- 124-authentik: forward-auth cut over, Authentik stopped (DNS-only now)
- investigation: forward-auth outpost marked RESOLVED

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

2026-06-01 00:33:26 +02:00

3.2 KiB

Raw Blame History

106 — `auth-outpost`

Authentik forward-auth outpost for LAN-gated apps. A stateless proxy that connects outbound to the VPS Authentik core and serves forward-auth locally, so Caddy (121) never hairpins auth through VPS Traefik.

At a glance

Hostname: auth-outpost
IP: 192.168.8.6 (static)
Privilege: privileged (Docker-in-LXC, features: nesting=1)
Resources: 1 core / 512 MiB / 4 GiB rootfs
Mounts: none
Created: 2026-06-01, Debian 13, replacing the embedded outpost on 124

Role

Runs one container — ghcr.io/goauthentik/proxy — that opens an outbound websocket to https://auth.hubris.network (the VPS core), pulls its proxy-provider config, and answers Caddy's forward_auth subrequests on 192.168.8.6:9000 (LAN-only bind). Because the call path is Caddy → outpost (LAN), with no Traefik in between, X-Forwarded-Host is preserved — the failure that 404s when Caddy is pointed at https://auth.hubris.network directly (Traefik rewrites the header). See the migration investigation.

Service / port map

Service	Listen	Notes
authentik proxy outpost	`192.168.8.6:9000`	`/outpost.goauthentik.io/*` (ping, auth/caddy)

Config paths

/opt/authentik-outpost/docker-compose.yml — ghcr.io/goauthentik/proxy:2026.5.2, AUTHENTIK_HOST=https://auth.hubris.network, AUTHENTIK_INSECURE=false, port bound 192.168.8.6:9000.
/opt/authentik-outpost/.env (mode 600, untracked) — AUTHENTIK_TOKEN for outpost hubris-lan-outpost (sops-encrypt into secrets/ — TODO Phase 5).

The outpost object (VPS Authentik)

Outpost hubris-lan-outpost (type proxy), providers: hubris-forward-auth (domain, Paperless + domain-level apps), Provider for Torrent (qBittorrent), Provider for Artifacto (single).
Health: VPS admin → Applications → Outposts → last-seen current; curl http://192.168.8.6:9000/outpost.goauthentik.io/ping → 204; container log Successfully connected websocket.

Caddy wiring

Caddy (121) (authentik) snippet reverse_proxy/forward_auth → http://192.168.8.6:9000 (was 192.168.8.180:9000 on LXC 124). Tracked in dtoro/caddy-conf.

124 — authentik — old embedded-outpost host (now DNS-only)
Caddy (121) — forward-auth consumer
Ingress (VPS traefik)
Authentik VPS migration

Changelog

2026-06-01 — created; forward-auth cut over from LXC 124

New dedicated LXC for the LAN forward-auth outpost (Phase 1 of the architecture migration). Deployed goauthentik/proxy:2026.5.2 pointed at the VPS core; repointed Caddy (authentik) from 192.168.8.180:9000 → 192.168.8.6:9000. Verified Paperless/qBittorrent/Artifacto return the SSO redirect with 124-Authentik stopped, confirming the frozen instance is out of the path. dnsmasq stays on 124 until DNS is relocated.

3.2 KiB Raw Blame History

106 — auth-outpost