Cloudflare - 400 Bad Request error-

Configuration
1

I was using DuckDns, but I have changed the provider and I don’t have real Ip anymore this is why I have purchased a domain.
the website gives 400 bad requests error

ERROR (MainThread) [homeassistant. components. HTTP.forwarded] A request from a reverse proxy was received from 172.30.33.3, but your HTTP integration is not set up for reverse proxies

http:
  use_x_forwarded_for: true
  trusted_proxies:
    - 172.30.32.1
    - 127.0.0.1
    - 10.0.0.2
    #log reported ipv4
    - 162.158.159.139
    - 172.69.55.59
    - 141.101.76.195
    - 141.101.98.91
    - 141.101.99.102
    - 141.101.105.87
    - 141.101.105.99
    #cloudflare ipv4
    - 103.21.244.0/22
    - 103.22.200.0/22
    - 172.30.33.3
    - 172.30.33.0
    - 103.31.4.0/22
    - 104.16.0.0/13
    - 104.24.0.0/14
    - 108.162.192.0/18
    - 131.0.72.0/22
    - 141.101.64.0/18
    - 162.158.0.0/15
    - 172.64.0.0/13
    - 173.245.48.0/20
    - 188.114.96.0/20
    - 190.93.240.0/20
    - 197.234.240.0/22
    - 198.41.128.0/17
    #cloudflare ipv6
    - 2400:cb00::/32
    - 2606:4700::/32
    - 2803:f800::/32
    - 2405:b500::/32
    - 2405:8100::/32
    - 2a06:98c0::/29
    - 2c0f:f248::/32

this is the code in my configuration.yaml file

2

solution:

http:
  use_x_forwarded_for: true
  trusted_proxies:
    - 172.30.33.3

for me, the solution was to leave only the Ip that appears in my log.

3

I am facing the same issue. I tried both configurations and it still gives me 400: Bad Request.
I made the transition yesterday from port forwarding to Cloudflare Argo tunnel and everything works fine at the first time. But today after installing a minor HA update I am not able to access it.
I can still access my Raspberry with SMB and modify the configuration.yaml

any suggestion?

4

did you check the HA logs or add-on Logs?

5

I have the same problem until i notice that I put the http proxies yaml code in the wrong yaml. I added it to the dashboard!! i solved the problem instaling de “File Editor” and put it in the /config/configuration.yaml

6

Hi guys after weeks of f***ing around. In your Nginx proxy server add the following to clear the X-Forwarded-For information:
proxy_set_header X-Forwarded-For “”;