@scottgus1@JonE Even if the extensions are not displayed, the .vbox file is pretty easy to see. It has a blue box and the file type is VirtualBox Machine Definition. It is quite clearly shown in the screenshot posted by JonE.
vbox.PNG
Thanks Bill, I'll upload that when I get a chance.
mpack wrote:He's definitely bridging to a wireless NIC.
00:00:04.569166 Network <string> = "HostInterfaceNetworking-Intel(R) Dual Band Wireless-AC 8260" (cb=60)
Before we go thinking up weird and complex problems, I'm wondering if it isn't something simple: could there be more than one WiFi on this PC? Could the VM be bridging to the wrong one?
Also, I see that the VM is on drive D while the primary VDI is in the Downloads folder in drive C. This is not a stable, long term solution, in fact it's a future disaster waiting to happen. The VDI needs to be inside the VM folder. And hopefully D is still an internal drive.
As a temporary solution or test, I would suggest plugging this PC directly into the router using an Ethernet cable. Then bridge to the PC's Ethernet NIC. That should definitely work. If it still doesn't work then it's a problem of the network config, not a VirtualBox config problem.
I'll try and see if I can connect directly, d drive is internal storage as well. If needed I could do a fresh install and put it all on the same drive.
OK so I did try just connecting directly to the router and I still have the same issue. I have attached some files of what I see and why I feel the VM is not connecting and also another vbox log file if needed. Thanks again!
Please try downloading Ubuntu and make a fresh new VM Bridged to your wired Ethernet adapter from the beginning, then we can see if Virtualbox Bridged is working. (It is possible that enough tweaking on the Home Assistant VM has happened to have broken something beyond easy repair.
Well I removed everything associated with orcal and virtualbox to try a clean install. After that I reinstalled everything and was running into some problems at first but I was able to set up a new home assistant through the web interface. I don't really know what happened or if it is really fixed as I am afraid to turn off the VM incase it doesn't come back up. One thing that did help was I looked at advanced ip scanner and finally saw my home assistant name show up with a ip address. So I used that VM ip:8123 and was able to log in. I will try and shut it down and see if it stays around if not I might be back. But I really appreciate all the help from you all. If you would like me to post any logs or anything please let me know and I will in the event it could help someone else. Another side not in the VM when starting for the first time it took me straight to the user name and password part of Hassos which was knida strange but I typed in root for the username and hit enter then did network info to cross reference the VM's ip with ip scanner and then went to the browser and it all worked. still kinda strange to me but oh well. Again thanks for all the help!