My Home Assistant is shown as running on the virsh list, and when i scan the devices over my network i find homeassistant with an assigned IP, but i cannot connect to it’s web client on port 8123.
Some details that might help with troubleshooting
ifconfig
br0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.1.10 netmask 255.255.255.0 broadcast 192.168.1.255
inet6 2804:d45:b300:500:90eb:a7ff:fef2:c7eb prefixlen 64 scopeid 0x0<global>
inet6 fe80::90eb:a7ff:fef2:c7eb prefixlen 64 scopeid 0x20<link>
ether 92:eb:a7:f2:c7:eb txqueuelen 1000 (Ethernet)
RX packets 3816 bytes 409166 (409.1 KB)
RX errors 0 dropped 111 overruns 0 frame 0
TX packets 1663 bytes 184730 (184.7 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
docker0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 172.17.0.1 netmask 255.255.0.0 broadcast 172.17.255.255
ether 02:42:46:04:a6:95 txqueuelen 0 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
enp2s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
ether 98:83:89:73:5c:48 txqueuelen 1000 (Ethernet)
RX packets 9757 bytes 2712863 (2.7 MB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 3897 bytes 430404 (430.4 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 164 bytes 11792 (11.7 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 164 bytes 11792 (11.7 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
vnet0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet6 fe80::fc54:ff:fe3c:d01 prefixlen 64 scopeid 0x20<link>
ether fe:54:00:3c:0d:01 txqueuelen 1000 (Ethernet)
RX packets 1947 bytes 230680 (230.6 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 5792 bytes 2034753 (2.0 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
kayke@server:~$ virsh net-dumpxml br0
<network>
<name>br0</name>
<uuid>5755da99-e6a9-4b54-9bbb-40cd6328dbf3</uuid>
<forward mode='bridge'/>
<bridge name='br0'/>
</network>
kayke@server:~$ virsh net-list --all
Name State Autostart Persistent
-----------------------------------------
br0 active yes yes
kayke@server:~$ sudo virsh list
Id Name State
------------------------
1 hassos running
Command used to start my hassos instance
sudo virt-install --import --name hassos \
--memory 2048 --vcpus 2 --cpu host \
--disk haos_ova-13.2.qcow2,format=qcow2,bus=virtio \
--network bridge=br0,model=virtio \
--osinfo detect=on,require=off \
--graphics none \
--noautoconsole \
--boot uefi
Accessing HA Cli Network info
# ha network info
docker:
address: 172.30.32.0/23
dns: 172.30.32.3
gateway: 172.30.32.1
interface: hassio
host_internet: true
interfaces:
- connected: true
enabled: true
interface: enp0s2
ipv4:
address:
- 192.168.1.12/24
gateway: 192.168.1.1
method: auto
nameservers:
- 192.168.1.1
- 1.0.0.1
ready: true
ipv6:
address:
- 2804:d45:b300:500:ee4a:256a:6a01:9997/64
- fe80::96a2:4cb3:972:40ea/64
gateway: fe80::1
method: auto
nameservers:
- fe80::1
- 2804:d45:400::4
ready: true
mac: 52:54:00:3C:0D:01
primary: true
type: ethernet
vlan: null
wifi: null
supervisor_internet: true
Address I have tried connecting to:
http://192.168.1.12:8123
I can however ping 192.168.1.12 from other devices on my network.
I have been stuck on this problem for hours… any input is much appreciated.
Thanks