Hey guys, i noticed after rebooting my unraid server, HA-in-a-box is not able to start the vm and throws this error:
Version check passed. Continuing...

Host path for '/domains' is /mnt/user/domains

Highest Q35 machine type available is pc-q35-10.2

The default VM network type is eth0

Putting default ha vm icon in place

Icon copied successfully.

Home Assistant directories are already present...continuing.

There is already a vdisk image here...skipping.

As this is an OVMF VM, I need to create an NVRAM file. Creating now ....

Formatting '/etc/libvirt/qemu/nvram/d8e05b6b-07e0-4a41-b1b4-2a961f908de2_VARS-pure-efi.fd', fmt=raw size=65536

All required files are present. Attempting to define the VM...

Failed to define the VM. There was an error during the VM definition process.

Not sure though how to solve this problem, i have no idea why its failing there and how to fix it. Starting the container manually works though and starts the vm properly

Hey I installed home assistant in a box and having issues accessing home assistant through the docker. The VM is running and I can access it at http://192.168.1.181. But the docker points to http://192.168.1.181:8123/ and when that is being used I don't get access. My unraid server is http://192.168.1.228/.

I was also trying to VPN into my Home Assistant and I have wireguard setup to access all other dockers, but can't access home assistant through the app. My understanding is that I may have to pass through something via wireguard to gain access. I first want to solve the web ui as that is one of the reason I installed it using home assistant in a box.

So, the docker exists to create the VM or start it if it fails. It doesn't provide anything unique, the VM UI is what you're after. if it's important to you to be able to access the UI from the Docker icon, manually set the Web UI address in the docker.

For the VPN, connect to the VM, not the docker, again, it doesn't have a UI/interactions.

Looks like this one is now deprecated? But it only had an update yesterday?

@z0ki

There is a new version V3.

See also the GitHub link: https://github.com/SpaceinvaderOne/Home_Assistant_inabox

And the note coming from V2: https://github.com/SpaceinvaderOne/Home_Assistant_inabox#coming-from-v2

Edited August 21Aug 21 by n3ro365

Just so I'm clear, v3 is for the docker container. There was a release for Home Assistant today (2026.8.3). Do I just update Home Assistant through the Home Assistant UI?

Hi there, I upgraded to V3 and now my VM won't start, HA Gui says:

✕ Add -v /var/run/libvirt/libvirt-sock:/var/run/libvirt/libvirt-sock to your docker run. (virsh capabilities failed (1): error: failed to connect to the hypervisor error: Failed to connect socket to '/var/run/libvirt/libvirt-sock': Connection refused)

Libvert log says:

error : virNetSocketNewListenUNIX:514 : Failed to bind socket to '/var/run/libvirt/libvirt-sock': Address already in use

Tried to follow the video https://www.youtube.com/watch?v=ZGJTjXlbxXg and it failed on startup with this error:

error: Failed to create file '/etc/libvirt/qemu/nvram/ddd42a59-0c2d-4e25-bca3-20ba309c1e83_VARS-pure-efi.fd.new': No such file or directory