I have set up the HTTP x_forward/trusted proxy statements in HA configurations.yaml, (clearing the 400 error).
Then, yes. If there’s something other than these to enable the websockets in nginx configuration, can you provide more detail or a link? Thanks for responding!
Holy cow, @francisp!!! Thank you!!! I’m sorry that it was something I hadn’t found previously myself, but very thankful for your reference to it! That was simple, and it instantly started working!!! I love this HA community!
Well, my excitement was short lived… strangely, this fixed the PC/browser connection using HTTPS perfectly… it seems to work through and through. But when I try to connect with the iOS app on my phone, it stalls out when it tries to connect, and then the picture below. (This is out of the HA iOS app, not out of my phone config… it is found when I go to my profile in the app, after failure to connect.)
I’m going to move this to the other thread now, where @francisp referenced. Answer here if you know the answer, I suppose, but that seems the more appropriate place now.
You guys have no idea the amount of time I’ve spent trying to figure this out. This is exactly what I needed. I was checking the logs in the NPM addon, but it wasn’t very clear. I thought I might get a clue with developer tools in Chrome. Nothing helped until I read this post. Thank you @kiwijunglist for posting this. You have probably helped save my marriage LOL through this.
Here is an unusual case that might come up for a few. I set up an HA box in my home network. THen moved it to another network where I use an openvpn tunnel to access it, but the reverse proxy is still on my network. So guess what…what HA thinks is the reverse proxy is actually is the IP of the other end of the tunnel. I guess that’s not surprising but I had to go to the logs like the OP to see the IP and then quickly realized it was the tunnel IP. THere you have it!