Help with Error 400: Bad Request

Configuration
, ,
1

Please help. I have scoured the blogs for anything that might help and tried everything I can understand to try and I still end up with the same problem. 400: Bad Request everytime I try to access my Home Assitant from my domain. I am using AdGuard for DNS and DHCP, NGINX Proxy Manager for proxy, Let’s Encrypt for the certificarte, and cloudflare for my host. I have added in to my configuration.yaml:

http:
use_x_forwarded_for: true
trusted_proxies:
- 172.30.32.1
- 127.0.0.1
- 10.0.0.2

and nothing seems to work. I am at my rope’s end. I don’t know what logs I should post here to help show what’s going on so any direction would be helpful. I know I’m not the only one who has faced this issue and it seems that for most everyone adding in the above has solved the problem. I am using a RPi 4 8GB with a 500 GB SSD connected to my TP-Link router with the appropriate ports open. I have followed all the instructions and everything was working perfetly until the need to add the trusted_proxies section to configuration.yaml. Thank you for your time.

2

Show the error in your home-assistant.log. It contains the IP you need to add to trusted_proxies.

2 Likes
3

Here is a copy of the log entry when I tried to access form the outside:

2021-09-25 19:25:54 ERROR (MainThread) [homeassistant.components.http.forwarded] Received X-Forwarded-For header from an untrusted proxy 172.70.98.43
2021-09-25 19:25:54 ERROR (MainThread) [homeassistant.components.http.forwarded] Received X-Forwarded-For header from an untrusted proxy 172.70.98.135
2021-09-25 19:25:55 ERROR (MainThread) [homeassistant.components.http.forwarded] Received X-Forwarded-For header from an untrusted proxy 172.69.35.164

As you can see they are all from different IP Addresses and one from another subnet.
Here’s another one a little later:

2021-09-25 19:42:09 ERROR (MainThread) [homeassistant.components.http.forwarded] Received X-Forwarded-For header from an untrusted proxy 108.162.215.105
2021-09-25 19:42:09 ERROR (MainThread) [homeassistant.components.http.forwarded] Received X-Forwarded-For header from an untrusted proxy 172.69.35.164
2021-09-25 19:42:11 ERROR (MainThread) [homeassistant.components.http.forwarded] Received X-Forwarded-For header from an untrusted proxy 108.162.215.105
2021-09-25 19:42:11 ERROR (MainThread) [homeassistant.components.http.forwarded] Received X-Forwarded-For header from an untrusted proxy 172.69.35.164
2021-09-25 19:42:11 ERROR (MainThread) [homeassistant.components.http.forwarded] Received X-Forwarded-For header from an untrusted proxy 172.70.98.43

So, yeah. No one else has run across this before from my research. I hope this means something to someone because I’m stumped.

4

You use the

proxies ?

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
  - 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
4 Likes
5

Thanks, @francisp. I’ll give anything a try at. This point. I’ll let you know.

6

@francisp that did the trick! Thank you so very much. It never occured to me that the revers proxy could also be on the host’s side too.

7

Just wanted to jump in here and also say thanks @francisp too, as that sorted it for me as well!

8

Thank you, this has had me chasing my tail for the last 24hrs.

The only change I had to make was this though.

trusted_proxies:

  • 172.30.32.0/23
  • 127.0.0.1
  • 10.0.0.2
  • internal ip
2 Likes
9

Also wanted to say thank you, this saved me time and a lot of hassle identifying what was wrong with my apache proxy. Thank you.

10

I am going to cry. I can’t get this to work no matter what I try. here’s my setup:

  1. TrueNAS HomeLab on 192.168.61.41
  2. Nginx installed within TrueNAS, accessible through 192.168.61.41:10583 (for port 80 and 10584 for port 443
  3. HA installed on RPI at 192.168.61.154:8123
  4. HA config.yaml includes:
  use_x_forwarded_for: true
  trusted_proxies: 
    - 173.245.48.0/20
    - 103.21.244.0/22
    - 103.22.200.0/22
    - 103.31.4.0/22
    - 141.101.64.0/18
    - 108.162.192.0/18
    - 190.93.240.0/20
    - 188.114.96.0/20
    - 197.234.240.0/22
    - 198.41.128.0/17
    - 162.158.0.0/15
    - 104.16.0.0/13
    - 104.24.0.0/14
    - 172.64.0.0/13
    - 131.0.72.0/22
  1. Nginx UI panel config:

Keep getting 400 bad request. If I enable SSL settings then I get too many redirects.

I will pay someone to solve this problem of mine, that’s how desperate I am.

11

have you tried adding - 192.168.61.41 to the trusted proxy list? That should work as it’s your LAN proxy IP if I’m following you correctly.

12

I had to add ::1 for IPv6. I had the IPv4 IP you mentioned and the moment I added the IPv6 redirect, it magically started working

13

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