use_x_forwarded_for also requires the trusted_proxies setting

[fuentes81081]

Feedback

see: https://www.home-assistant.io/integrations/http/#use_x_forwarded_for

trusted_proxies can be a list of addresses or ranges. If using SWAG, the container's IP can be grabbed using docker inspect

configuration.yaml
http:
use_x_forwarded_for: true
trusted_proxies:
- 127.0.0.1
- 172.16.0.0/12
- 192.168.0.0/16

URL

https://www.home-assistant.io/integrations/fail2ban/

Version

2025.7.2

Additional information

No response

[home-assistant]

Hey there @home-assistant/core, mind taking a look at this feedback as it has been labeled with an integration (http) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of http can trigger bot actions by commenting:

• @home-assistant close Closes the feedback.
• @home-assistant rename Awesome new title Renames the feedback.
• @home-assistant reopen Reopen the feedback.
• @home-assistant unassign http Removes the current integration label and assignees on the feedback, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information) to the feedback.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information) on the feedback.

[frenck]

Oh hi there @fuentes81081 👋

trusted_proxies can be a list of addresses or ranges.

Correct, that is also documented, and examples show it.

I'm not fully understanding the documentation feedback you are trying to give. Could you clarify?

Thanks! 👍

../Frenck

[fuentes81081]

My comment was entered from the fail2ban documentation page where the trusted_proxies information and examples are absent. A little extra digging was required to get fail2ban to work; the http documentation page was very helpful.

[frenck]

I'm not fully understanding the relation. Are you saying you'd need to set up your instance correctly? 🤷

[fuentes81081]

The fail2ban documentation page mentions adding the use_x_forwarded_for setting in configuration.yaml, but it does not mention adding trusted_proxies which is also required.

My feedback is to mention adding trusted_proxies along with use_x_forwarded_for in configuration.yaml to the fail2ban documentation page.

[github-actions]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved.
If this issue is still relevant, please let us know by leaving a comment 👍
This issue has now has been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.