Hello everyone 
Im a first time user, and facing some issues, hopefully someone can guide me.
So i did the instalation on OracleMV - and got my .vb file from here: Windows - Home Assistant
The machine boots normally, and it ends up in
All looks good right?
The issue is, on windows when i try to reach the IP, it wont connect me, chrome keeps getting “connection refused” - PS i opened the ports in the router just in case, and changed nothing.
Any advise?
Many thanks 
Try connecting to 192.168.1.54:8123 instead of homeassistant.local
Hello @fleskefjes
I already tested that, still no connection possible.
Im able to reach both 192.168.1.52:4357 and http://homeassistant.local:4357/
But the :8123 keeps getting refused connection 
some additional info: both ipv4 and ipv6 are reachable on my local machine
Still having connection refused on all browsers
My guess is that it might be IPv6 that confuses your machine.
If the network is not configured as a bridge, then a fe80 IPv6 network will exist on both the internal and external network of your hypervisor network and that network is not routable.
Try to disable IPv6.
Are you trying to access the VM from the host computer or another computer on the network?
Static ip assigned in router for the VM? OS?
Rebooted router?
Rebooted VM?
Port forwarding? (shouldn’t be needed on lan but might be worth checking anyway)
Logged into the HAOS? (doesn’t look like you are?)
Just some ideas
ipv6 disabled - tested same result
Im trying to access the VM from the host computer
No static IP assigned for the VM - not aware on how to do it.
OS is win10 Pro 22H2 - Build 19045.5011
Rebooted router - not tried yet will do after this post
Rebooted VM - Yes
Port forwarding - no, but i opened them on the router dashboard
Logged into the HAOS - no, i could never reach onboarding
Try connecting from something outside the host machine, your phone for example. Port forwarding does not matter on the internal network, it’s when you need to access it from outside the internal network it matters.
router reboot done, no changes.
tried from phone & tablet via app, same result connection refused
a shot from my cmd in case it helps
I just checked, even i have or not ipv6 activated, the provider is not providing me it, so i think i might need to deactivate it on the VM? if thats the reason for this issue? Any idea how i do that?
On another note, im trying to disable ipv6 via cli, and my adapter has no info on it?
(based on this i gather:
network info to find the correct network adapter and see your current IP address set for HAOSnetwork update eno1 --ipv4-method auto --ipv6-method disabled (“eno1” needs to be replaced by your network adapter)network update eno1 --ipv4-gateway 192.168.x.x (“eno1” needs to be replaced by your network adapter, “x” needs to be replaced by your IP gateway, probably router IP))My HA cli shows:
Its like my adapter has no name… weird
Still looking at it my own, but appreciate any help that anyone can give
You have denied promiscuous mode.
Your NIC will then only accept packets for the hardware MAC address and bridged mode will therefore not work.
promiscuous mode activated, tested on Desktop and phone, same behavior, no access
You need to restart the VM for it to take effect.
Its working - i mean loading onboarding.
Only thing i did was restart the VM, for like the 50th time 
Having promiscuous mode disabled will have made sure all restarts with it in that state would fail.
I’m having a similar issue like @DocKoala992 but slightly different. Should I keep restarting the VM?
Background:
I am looking to migrate a QNAP hosted HA to a Dell OptiPlex hosted HA install. Got tired of QNAP reboots messing up the WAF.
So my home network is 192.168.1.xxx/24, & existing HA install on QNAP NAS is on 192.168.1.170 and responds to homeassistant.local DNS queries.
Installed VirtualBox on Windows, but the VM seems to have ended up on 172.30.32.0/23 range. I am unable to get to the Home Assistant UI for the Virtualbox.
Not sure how to get the VirtualBox VMs to end up on the 192.168.1.xx address ranges.
Not a virtualbox user, but what happens if you click the “cable connected”?
- didnt work.
