Jul 08, 2021 · A request from a reverse proxy was received from 172.30.33.5, but your HTTP integration is not set-up for reverse proxies. Running Home Assistant OS 6.1 with core-2021.7.0. From private session I get “400: Bad Request”
08.07.2021 · A request from a reverse proxy was received from 172.30.33.5, but your HTTP integration is not set-up for reverse proxies. Running Home Assistant OS 6.1 with core-2021.7.0. From private session I get “400: Bad Request”
Jun 25, 2019 · I am connecting through a server to my home network. client -> public server -> home server. client is in the Internet; public server is runnning a TCP4 to TCP6 tunnel (using socat) home server is behind a router with all ports opened, all running on IPV6; I get the login page, but sending credentials form leads me to "Unable to connect to Home ...
Oct 05, 2021 · I have an existing LetsEncrypt container and am trying to setup Home Assistant via the LinuxServer Docker image. I am able to access Home Assistant via IP address from within my network, but when I try to access via URL, I get the login page that accepts my login information (and apparently validates it). When I login, I just see “Unable to connect to Home Assistant.” from both inside and ...
28.09.2018 · Reverse proxy with NGINX using a subdomain. ⚠ This guide has been migrated from our website and might be outdated. Feel free to edit this guide to update it, and to remove this message after that.
Apr 02, 2017 · ok so i have basically the same issue. I am using a synology for the reverse proxy. The tip with the webSocket helped a lot. thanks @ imperyal. it did work fine for like a minute or so… if I set up a new reverse proxy… with websocket and everything, same thing it works locally and via the internet externaly. But maybe for 10 minutes…
02.04.2017 · if I set up a new reverse proxy… with websocket and everything, same thing it works locally and via the internet externaly. But maybe for 10 minutes… Then it goes back to “Unable to connect to Home Assistant.” Any ideas what i might have done wrong?
25.06.2019 · I am connecting through a server to my home network. client -> public server -> home server. client is in the Internet; public server is runnning a TCP4 to TCP6 tunnel (using socat) home server is behind a router with all ports opened, all running on IPV6; I get the login page, but sending credentials form leads me to "Unable to connect to Home ...
Oct 20, 2021 · Phone model: Fairphone 3. Home Assistant version: 2021.9.7 behind nginx 1.14 as reverse proxy with a Let's Encrypt certificate. Last working Home Assistant release (if known): Exact same versions as above. Failure appeared without an upgrade. Description of problem: Up until this morning the app worked fine.
05.10.2021 · I have an existing LetsEncrypt container and am trying to setup Home Assistant via the LinuxServer Docker image. I am able to access Home Assistant via IP address from within my network, but when I try to access via URL, I get the login page that accepts my login information (and apparently validates it). When I login, I just see “Unable to connect to Home Assistant.” …
26.12.2019 · After entering login id and password, it shows me "Unable to connect to Home Assistant. RETRY" ... A subdomain is routed to Home assistant 8123 port using reverse proxy. Necessary port is open in router. The text was updated …
Sep 28, 2018 · Reverse proxy with NGINX using a subdomain. ⚠ This guide has been migrated from our website and might be outdated. Feel free to edit this guide to update it, and to remove this message after that.
Dec 26, 2019 · A subdomain is routed to Home assistant 8123 port using reverse proxy. Necessary port is open in router. The text was updated successfully, but these errors were encountered:
20.10.2021 · Home Assistant Android version: 2021.9.0-full Android version: 10 Phone model: Fairphone 3 Home Assistant version: 2021.9.7 behind nginx 1.14 as reverse proxy with a Let's Encrypt certificate Last working Home Assistant release (if known...