Hello,
I am new to and testing Home Assistant (hopefully to replace SmartThings). I installed Home Assistant on a VirtualBox on win 10.
I am now trying to enable remote access, but having some problems:
I can access Home Assistant using http://homeassistant.local:8123/
But I cannot access Home Assistant using my local IP http://192.168.1.6:8123/
(Note that I can access other services, like …:3000/)
Any suggestions?
Thanks!
Do not expose your Home Assistant server over an unencrypted session (http).
DuckDNS includes LetsEncrypt (free).
Or use Nabu Casa ($5 per month, which goes to support Home Assistant).
Or set up a VPN.
I’ve set up duckdns, but it’s not reachable either. (Before considering Nabu Casa, I’d like to play around.)
Since other services (e.g. 3000) are accessible, can this be related to the VM? Note that I’ve followed the instructions and chose “bridged” adapter…
Then you should be using https not http.
same story… nor reachable. But even before involving duckdns and extranl IPs, shouldnt I be able to reach it using my internal IP http(s)://192.168.1.6:8123/…? Can this be linked to the VM?
No. Before enabling DuckDNS you should be using http.
I tried both http and https… let’s forget duckdns for a moment.
How am i supposed to access home assistant using a local IP within my network? Neither http://192.168.1.6:8123/ and https://192.168.1.6:8123/ seem to work.
If this is the correct IP and you have not set up DuckDNS yet then this should work:
Unless you have not set up your VM correctly.
I’ve just uninstalled the duckDNS add-on and deleted my duckDNS domain.
The IP is definitely correct, I can access other ports (3000 for example).
I’ve followed the VDI instructions, shouldn’t this be correct?
Thanks!
OK I solved it: I misunderstood what “bridged” meant, i thought the home assistant (VM) would end up with the same IP as the Windows machine hosting it, but I now realize that’s not the case… In short: I was using the wrong IP.