[whoalin1]

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.

All commits carry an Assisted-by: Cursor:grok-4.7 trailer.

[github-actions]

Hello there,
Thank you so much for taking the time and effort to create a pull request to our Nextcloud project.

We hope that the review process is going smooth and is helpful for you. We want to ensure your pull request is reviewed to your satisfaction. If you have a moment, our community management team would very much appreciate your feedback on your experience with this PR review process.

Your feedback is valuable to us as we continuously strive to improve our community developer experience. Please take a moment to complete our short survey by clicking on the following link: https://cloud.nextcloud.com/apps/forms/s/i9Ago4EQRZ7TWxjfmeEpPkf6

Thank you for contributing to Nextcloud and we hope to hear from you soon!

(If you believe you should not receive this message, you can add yourself to the blocklist.)