#Problem With remote Access with NGINX + Azure Proxy Application and IP Ban

1 messages · Page 1 of 1 (latest)

quasi heath
#

Good morning,
I have a problem with the IP Ban of Home Assistant and NGINX + Azure Proxy Application for expose my instance, I put the IPs from where I connect most often in trusted_proxies but it continues to give me problems with the message "Unable to connect to Home Assistant." upon login with the 60 second wait.

This always appears in the log:

Registratore: homeassistant.components.http.ban
Fonte: components/http/ban.py:135
Integrazione: HTTP (documentazione, problemi)
Prima occorrenza: 10:18:48 (2 occorrenze)
Ultima registrazione: 10:19:13

Login attempt or request with invalid authentication from 4.232.xxx.xx (4.232.xxx.xx). Requested URL: '/auth/login_flow/ae5989017bddf79ddca20ac72f32082b'. (Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/129.0.0.0 Safari/537.36)
Login attempt or request with invalid authentication from 4.232.xxx.xx (4.232.xxx.xx). Requested URL: '/auth/token'. (Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/129.0.0.0 Safari/537.36)

The indicated IP has been trusted in the settings and gives the same problems.

Even Google Assistant in the manual integration connection logs in and then fails to connect.

unreal raft
#

I put the IPs from where I connect most often in trusted_proxies
That is not what that is to be used for. That is for whatever might be a proxy for your HA instance

#

If MS is acting as an upstream proxy, you likely need to add the blocks they use to get the real client IP, too

quasi heath
unreal raft
#

But that's likely not going to "fix" those error messages. Those look like they're just requests w/ bad tokens/passwords in them. Not sure how Nginx is installed/configured but make sure you're allowing WebSocket connections

quasi heath
unreal raft
quasi heath
rocky basin