goyban/docker-compose-repo
1
1
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: explain the proxy target address in the forward auth example

Browse Source
This commit is contained in:
Goyban
2026-09-03 14:27:22 +02:00
parent 2f678693bf
commit 04e84fde7a
1 changed files with 7 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/authentik-sso.md
+7
View File
@@ -114,6 +114,13 @@ firefly.domain.com {
Only the last line changes per service: swap the address and port, and the Only the last line changes per service: swap the address and port, and the
hostname at the top. Everything between is identical for every app. hostname at the top. Everything between is identical for every app.
`10.10.0.2` there is a **private address, not a public one** — in this setup a
WireGuard host, so Caddy reaches the app over the tunnel rather than across the
internet. Whatever address your proxy uses to reach the service goes there: a
LAN IP, a WireGuard or Tailscale peer, or a container name if Caddy runs in the
same Compose project. The only requirement is that Caddy can reach it and the
outside world can't.
### Why each piece is there ### Why each piece is there
**`route { }` is not optional.** Caddy normally executes directives in its own **`route { }` is not optional.** Caddy normally executes directives in its own