Skip to content

docs(admin): clarify trusted_proxies rejects hostnames - #15727

Open
whoalin1 wants to merge 1 commit into
nextcloud:masterfrom
whoalin1:docs/trusted-proxies-no-hostnames
Open

whoalin1 wants to merge 1 commit into
nextcloud:masterfrom
whoalin1:docs/trusted-proxies-no-hostnames

Conversation

@whoalin1

@whoalin1 whoalin1 commented Oct 7, 2026 •

Copy link
Copy Markdown

Summary

Closes #7005

trusted_proxies only accepts literal IPv4/IPv6 addresses and CIDR ranges. Document that Docker/Compose hostnames are not resolved, and point admins at network CIDR ranges plus overwritehost / overwriteprotocol when automatic detection fails.

This is the documentation half of the request; adding DNS lookup in Request::matchesTrustedProxy() would be a separate server change.

Test plan

  • Docs build for reverse_proxy_configuration.rst
  • Note sits under the trusted_proxies bullet list

AI disclosure

This PR was drafted with the help of AI coding assistants (Cursor agents / LLM-based tools), including the description. I am responsible for it and happy to rework anything that doesn't fit.

The commits don't carry Assisted-by: trailers yet; I can add them if wanted (that needs a force push).

This branch has not been deployed

No deployments
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.

Trusted proxy cannot resolve hostname (docker), only IP or CIDR-ip

1 participant