Skip to content

docs: TRUSTED_PROXIES and FORCE_HTTPS for reverse-proxied installs - #26

Merged
gdarko merged 1 commit into
3.xfrom
docs/https-behind-proxy
Sep 22, 2026
Merged

gdarko merged 1 commit into
3.xfrom
docs/https-behind-proxy

Conversation

@gdarko

@gdarko gdarko commented Sep 21, 2026

Copy link
Copy Markdown
Contributor

Companion to InvoiceShelf/InvoiceShelf#788.

TRUSTED_PROXIES was undocumented, and narrowing it is the trap behind InvoiceShelf/InvoiceShelf#500: people list their reverse proxy's LAN address, but the container sees the Docker bridge gateway, so X-Forwarded-Proto is discarded and the app generates http:// links behind an https site. The visible symptom is a sign-in that fails and then works after a refresh.

Adds both variables to the public-address section of the Docker install page, and TRUSTED_PROXIES to the worked reverse-proxy example.

…stalls

A narrowed TRUSTED_PROXIES must name the address the container sees, not
the proxy's LAN address; naming the wrong one makes InvoiceShelf discard
X-Forwarded-Proto and generate http:// links behind an https site.
@gdarko
gdarko force-pushed the docs/https-behind-proxy branch from e93c621 to e755f6a Compare September 21, 2026 20:23
@gdarko
gdarko changed the base branch from master to 3.x September 21, 2026 20:23
@gdarko
gdarko merged commit 7c55590 into 3.x Sep 22, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant