docs: add reverse proxy requirements for subdomain gateway #317
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
willscott
approved these changes
Dec 19, 2025
lidel
force-pushed
the
docs/subdomain-gateway-reverse-proxy
branch
from
92e48f7 to
fd5765a
Compare
- expand nginx example (no longer collapsed) - add explicit warning about X-Forwarded-Proto consequences - improve nginx config comments explaining header importance
lidel
force-pushed
the
docs/subdomain-gateway-reverse-proxy
branch
from
fd5765a to
60d028e
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
document the need for correct
Hostheader forwarding when running Rainbow behind nginx or other reverse proxies, and provide minimal nginx configuration example with common pitfalls to avoid