Home Assistant running, but no access through url or app

Installation Home Assistant OS
1

Hi.

Had a power outage and the UPS didn’t last long enough to keep the system running.

Windows machine with VirtualBox. Been running for at least a year.
This is the process :

  • VM starts
  • HA CLI opens and shows the URL
  • No access through IP:8123 or homeassistant.local:8123
  • I can ping the ip address and recieve packages
  • Restart Home Assistant as well as Host
  • Tried creating a new VM with fresh Home Assistant, but still the same problem.
    Attaching the network settings in Virtualbox as well as supervisor logs and network info. Core logs look normal.

Any tips out there?

supervisor logs
supervisor logs1023×689 13.7 KB

network info
network info356×517 5.61 KB

network settings oracle

2

dbus
dbus963×159 85.2 KB

3

I think Promiscous mode might need to be enabled.
This setting enables the network card to receive packets to other MAC addresses than the one coded into its firmware, which is something many hypervisors use when setting up VMs in bridge mode.

4

Sorry, I changed it after the screenshot was taken. It’s on “Allow All”, but still same issue

5

Did you restart the VM after the change?

6

Yes I restarted VM and host.

Home Assistant shows as connected/online on my routers app. “ha network info” confirms the IP address, but still no access

7

how dies your main console look?
does it have home assistant written over 3 lines?

8

This one?

main console
main console712×370 32.9 KB

9

Yup, that is the one.
Does the IPv4 address start with 172, then HA is up and running and something in your VirtualBox is not configured right.

10

Well it’s 192.168, but that should not make a difference if I’m not mistaken.

I can samba into the folders and log files.
Log file has several “setup failed” for dependencies like person, device_tracker, frontend.

11

Yeah, that should work.
As long as it is not starting with 169, because that is a self-signed IP, which indicate a DHCP problem.

Could you run “ha resolution info” in the console?

12

No issues listed

resolution info

This really has me stumped.

13

Running "nmcli con show “Home Assistant OS default” shows no ipv4 addresses though

nmcli con show

EDIT: because it was under “Supervisor enp0s3”

14

and what about “ha net info” ?

15

oh and could you try to use another device to try to connect to ip:8123?
Maybe a mobile phone on wifi?

16

net info result
laptop browser as well as mobile phone on wifi results in “ERR_CONNECTION_REFUSED”

net info

17

Is 192.168.21.x your correct home network? I note it is statically assigned, and if you changed your network to a different subnet, it may now be in a different subnet.

18

Correct.
Also tried a more basic configuration.yaml as well as deleting all custom components folders, but still same problem.

19

Finally up and running again.

I tried deleting the home assistant db, but I don’t think that’s what solved it.
Probably running the following in main console solved it :

ha backups list

  • I then checked the list for one of the latest backups, and checked that the file size was comparable to a full backup.

ha backups restore *backupname*

20

Try changing the Promiscuous Mode: Allow VMs