Updated to latest OS, forwarding to http://homeassistant:8123 not working in Nginx

[hidden breach]

Am using Nginx Proxy Manager to forward my domain to http://homeassistant:8123, but it's returning a 400 Bad Request and I'm not sure why. Happened right after the latest OS update. Not sure what logs to send, but will take any and all suggestions. The forwarding worked flawlessly before.

[hollow ore]

Take a look at your home-assistant.log... likely your trusted_proxies in your configuration needs to be updated, possibly the NPM IP changed

[hidden breach]

I literally just saw this, not sure how I missed the logs when I checked them earlier. Thanks! 😄
Any way to stop the NPM IP from changing so this won't be an issue?

[hollow ore]

Probably best to just define the range that it can fall in. Did you just specify the exact IP before?

[hidden breach]

I kinda brute forced it last time with:

http:
  use_x_forwarded_for: true
  trusted_proxies: 
    - 10.0.0.4
    - 169.254.0.0/16
    - 10.0.0.0/24
    - 172.17.0.0/16
    - 172.18.0.0/16
    - 172.30.33.4
    - 127.0.0.1
    - 172.30.33.1
  ip_ban_enabled: true
  login_attempts_threshold: 5`

Getting this in the logs now. Do I need to restart the add-on for the new http config to take effect?

Received X-Forwarded-For header from an untrusted proxy 172.30.33.1

I added the 172.30.33.1 line just now

[hollow ore]

172.16.0.0/12
will cover all of the lines you have that start w/ 172

[hidden breach]

As in replace all lines starting with 172 with that? May I ask what the slash does?
And what parts do I need to restart for the new trusted proxies to have effect?

[hollow ore]

You just need to restart HA itself. The slash denotes the size of the subnet (you have similar, smaller ranges defined already)

[hidden breach]

Restarted HA with the new config, works like a charm! Initially tried reloading the configuration, a bit surprised that that didn't work. You need to reload HA every time you update the configuration.yaml?