Hacker News new | past | comments | ask | show | jobs | submit login

The author doesn't explain it well, but I use home assistant and I share the same view. Home assistant is not a very secure app. I would be fine putting it behind Nginx with basic auth, because Nginx is quite battle hardened and basic auth is a small attack surface.

I've solved it instead by using Wireguard and keeping home assistant on my private network. No idea why the author thinks VPN is not a good solution. It's also helpful for several other apps I don't feel safe exposing to the internet.






Nginx isn't suggested on the remote access manual page for sure https://www.home-assistant.io/docs/configuration/remote/

But there's addons in the package manager:

> Want to protect the website with a username/password? Well, it can do that too!

https://github.com/hassio-addons/addon-nginx-proxy-manager


> Nginx isn't suggested on the remote access manual page for sure

This makes it seem like they advise against it on that page, which is not true. Nor would it make any sense, putting a reverse proxy in front of a web application before exposing it to the open internet is about as typical as things get.


The problem the author describes is that doing this is not compatible with the mobile app. It doesn't support http basic auth and also can't present a client certificate (that's what I used to secure remote access to other browser based apps)

Home Assistant's Android app does work with client certificates.

https://companion.home-assistant.io/docs/getting_started/#tl...


> I've solved it instead by using Wireshark and keeping home assistant on my private network.

What is wireshark for? Or did you mean wireguard and get autocorrected?


Indeed wireguard. Fixed, tnx



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: