Jul 14, 2021 · Home assistant (400 Bad Request) Docker + Proxy - Solution. Configuration. kiwijunglist (Mike Stewart) July 14, 2021, 1:05am #1. Hi. With the latest update of home ...
01.08.2021 · The recommended Cloudflare configuration uses ‘Proxied’ requests to your HA instance. This is treated as a ‘reverse proxy’ by HA which (currently) blocks these requests, so you get a 400 Bad Request error.
19.07.2021 · If you are getting a 400: Bad Request error when you try to access your Home Assistant via HTTPS, then you’re not alone. In today’s article I will teach you how to fix the Home Assistant error and access your Home Assistant over a secure HTTPS connection again! STEP 1 Please Support My work by Making a Donation. STEP 2 Open Docker package.
15.07.2021 · In Home-Assistant, i have setup my Google Home and can play media through it but whenever i try it with the "google_say" API of Home-Assistant it doesn't work. I also tried calling the Home-Assistant API over my Phone using an App called "API Client" but i …
I've been getting this 400 Bad request for days now. I haven't been able to even take a look on how to fix this since I'm traveling for work. Why they would cause this change and NOT give a heads up or something, it's pretty bad. I can't control anything until I get home to figure out how to bypass this. Truly bad form
14.07.2021 · With the latest update of home assistant v2021.7.0 I started getting “400 Bad Request” error when I tried to access HA via my external http/https address. I could still access home assistant without error via the local IP address. If you check out the breaking changes if you are running a proxy you need to add
09.08.2021 · 400: Bad Request after upgrade. adrianwi (Adrian) August 9, 2021, 11:55am #1. I’m running Home Assistant OS 6.2 on a Raspberry Pi which I upgraded yesterday to supervisor-2021.06.8 and core-2021.8.4. Other than some problems with the Tesla integration, everything appeared to have worked fine as I was testing using my local IP address.