A request from a reverse proxy was received from 172.30.33.4, but your HTTP integration is not set-up for reverse proxies

Configuration
1

I get this warning.

Logger: homeassistant.components.http.forwarded
Source: components/http/forwarded.py:90
Integration: HTTP (documentation, issues)
First occurred: 18:54:35 (49 occurrences)
Last logged: 19:32:00

A request from a reverse proxy was received from 172.30.33.4, but your HTTP integration is not set-up for reverse proxies; This request will be blocked in Home Assistant 2021.7 unless you configure your HTTP integration to allow this header

But as far as I know I do not use reverse proxy.
I do use: NGINX Home Assistant SSL proxy for running DuckDNS
or is that reverse proxy? (I am a Noob on this)
configuration:

image
image822×774 25.6 KB

How to avoid this error? Thanks in advance

2

Not sure how this works with the addon, but usually you need to define trusted proxies in configuration.yaml

3

I had that before
but because of installing NGINX Home Assistant SSL proxy in the past, I had to flag out the http lines in the configuration.yaml:
(I don’t know why, I just followed a setup movie)

#----------------------------------------------------------------
# Uncomment this if you are using SSL/TLS, running in Docker container, etc.
#----------------------------------------------------------------
#http:
#   base_url: https://myduck.duckdns.org:8123
#   ssl_certificate: /ssl/fullchain.pem
#   ssl_key: /ssl/privkey.pem

If I unflag these I can not approach HA anymore (Locally and by DuckDNS)

4

This worked for me: Reverse proxy error - #29 by moto2000
There are a few different possible variations if you look through the whole post

1 Like
5

Thanks. It looks like it is working for me also.
I do understand 127.0.0.1 (localhost)
but what is 172.16.0.0/12 and ::1?

My warning is saying on adress: 172.30.33.4
Do I need to add that adress also? (or is that covered by: 172.16.0.0/12?)

6

That would be the ip for nginx inside of docker supposedly the /12 is for internal only docker ips (from another post I can’t seem to find) and the ::1 is for the ipv6 variation I believe. I will update with the post where others were discussing it as soon as I can find it again

7

I forgot to thank you.
THANKS! :grinning:

8

From what i gathered that covers all of it… I believe that specific ip for nginx container can change on a reboot of the host

9

Thanks again. I think your right, because the warning is gone