Same result as above. Tried via IP and the homeassistant.local:8123 (http/https)
Make sure that the firewall is disabled for your specific network type.
If you are not using the Windows firewall, then be aware that when you disable the third party firewall you are using, that the Windows firewall might be enabled then.
No third party firewalls installed… Just a fresh copy of Windows 11 with “defender” and that has been fully disabled. Same issue persists. I did go into advanced firewall settings and create a rule to allow all traffic through 8153 and no luck.
What browser are you using? Firefox will allow you to over ride the https versus http. I just tried Edge and it won’t let me, even tried the way to turn that off with no effect. Since Edge is built on Chrome that will also fail. So try FF
OK, that means something was a missed when you gened up the HA install into the docker. Check the settings for the HA that are brought out to the network card via the docker setup.
There lots of search returns “HA on a docker with networking issues”
Pardon my ignorance, but shouldn’t the docker dependencies be loaded on the image I installed on my virtual box already?
This was the link I used: * VirtualBox (.vdi)
So you followed step 5 on bridging the “Network” then the “virtual” Network Adapter 1 or ?" Choose “Bridged Adapter” the the true host network (allowing for a true network card or a motherboard network adapter).
Can you post the Terminal screen capture that is behind the browser pic also?
Looking back through the thread I see and address of 192.168.1.184 on the Win11 laptop and the docker is set to be 192.168.1.221 from the internal 172.X.X.X address
So I’m confused as what is the true address, so please post that terminal pic please
The IP has to be the same on the host Win11 and the Virtual box (host network adapter.
Thank you! So it looks correct. How is your home network setup? Any VLANs? More than one subnet?
Probably won’t hear from him, it’s the little thanks that us hard working people put in for free that would be appreciated rather than just bullying and steam rolling the community for support that isn’t really homeassistant related
Like me you probably have a stressful high paying day job and family to run or busy lifestyle, yet find some time to help contribute here
With a smile, lets move on 
1 Like
Yeah, I think the network was wrong. It is a single IP address entry and it is set with a range of /24 at the end. The IPv6 has a /64 on the end of it’s normally single IP address.
EDIT:
Well I just checked mine and it has those /24 and /64 added on the end now. A update must of made a change to how the network is setup. Wasn’t like that a few months ago.
So I’m back to my theory about it being a browser issue with forced https: versus http: settings that have to be over-ridden. MS just made a change with that it’s called “Auto-HTTPS” what a pain to find that setting. It is well hidden now by MS
As the address bar shows in FF it has https in it, so it needs to http:
those /24 and /64 is a different way to write the netmask ie 255.255.255.0
Sorry guys, my new user account had a excruciating 20 hour pause on posts yesterday… I really appreciate the effort in trying to get me online!
My home network is very basic right now… The windows machine with Virtual Box/Home Assistant is connected directly to a Verizon router. Verizon router does see “homeassistant” and the IP/mac addresses do match up. Those addresses are different from the Windows machine-which I assume is okay in this situation?
I can still reach the Home Assistant observer directly from the windows machine and from different computers hardwired and via wifi.
Rebooting: I have rebooted the HA VM several times in between changes and nothing… The windows box hosting the VM has been rebooted at least two times as well. For shits and giggles I also rebooted the router and same issue is present.
Maybe I should reboot the windows box a third time? Reminds me of this oldie 
http://www.thewebsiteisdown.com/salesguy.html
Next Step:
route print -4
Hmmm, thats odd?
After running the route print command and seeing some strange IP’s I uninstalled and completely removed the VPN from the Windows box. Route print again after removal:
I do see a strange IP destination (127.255.255.255) on that list… Also, no idea what the 192.168.1.255 is either. No traces of this on the router, and its not pingable. That last route print was after running ipconfig release/renew.
I rebooted the VM and Windows box in hopes that may have been the problem all along (VPN was previously disabled, not fully uninstalled) and still no dice, I don’t think this is a VPN issue.
Using Mozilla FF as requested (previously tested using http on that first tab):
http
https
Again, I appreciate all your efforts here!
I have an old Raspberry Pi Model B laying around… I know its a bit below the HA recommended specs, but would it be worth tossing out this Virtual Box install?
Can you open the settings on FF then go to Privacy/Security and scroll down to the bottom to: HTTPS-Only Mode I have “Don’t enable HTTPS-Only Mode”