Skip to content

docs(admin): clarify trusted_proxies rejects hostnames #15727

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
whoalin1 wants to merge 1 commit into
base: master
Choose a base branch
from
Open

docs(admin): clarify trusted_proxies rejects hostnames #15727

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions admin_manual/configuration_server/reverse_proxy_configuration.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -27,6 +27,12 @@ to define the servers Nextcloud should trust as proxies. This parameter
provides protection against client spoofing, and you should secure those
servers as you would your Nextcloud server.

.. note:: Hostnames are **not** resolved. Entries such as a Docker Compose
service name (for example ``nginx``) will not match. Use the proxy's IP
address or a CIDR range that covers the Docker / private network instead
(for example ``172.16.0.0/12`` or ``10.0.0.0/8``). Pair this with
``overwritehost`` / ``overwriteprotocol`` when automatic detection fails.

A reverse proxy can define HTTP headers with the original client IP address,
and Nextcloud can use those headers to retrieve that IP address. Nextcloud uses
the de-facto standard header 'X-Forwarded-For' by default, but this can be
Expand Down
Loading