HassOS in kvm on headless debian not accessable on local network

I’m attempting to move my HassOS running in virtualbox on Win10 desktop to a new headless debian 11 server that I have running. I’m new with linux so I have struggeled with configuring kvm and bridge my ethernet, however this part now seem to be working. After mounting the latest HassOS qcow2 image I’m able to access HassCli from my vm, my Hass instance is also recognized and appear in the list over connected devices on my router, however i’m not able to access Hass from other devices on my network. Attempting to connect to Hass from my desktop computer/laptop on the same local network only results in connection refused. What can possibly be the reason for this?

Some details that might help with troubleshooting

Network interfaces

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enp0s25: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master br0 state UP group default qlen 1000
link/ether fc:3f:db:88:37:8c brd ff:ff:ff:ff:ff:ff
3: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether fe:ef:7c:59:3c:14 brd ff:ff:ff:ff:ff:ff
inet 192.168.68.120/24 brd 192.168.68.255 scope global br0
valid_lft forever preferred_lft forever
inet6 fe80::fcef:7cff:fe59:3c14/64 scope link
valid_lft forever preferred_lft forever
8: vnet4: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br0 state UNKNOWN group default qlen 1000
link/ether fe:54:00:b4:e7:e9 brd ff:ff:ff:ff:ff:ff
inet6 fe80::fc54:ff:feb4:e7e9/64 scope link
valid_lft forever preferred_lft forever

joe@debian:/$ virsh net-dumpxml br0
<network>
  <name>br0</name>
  <uuid>6763d1d5-e474-4986-8675-610d8014eb9a</uuid>
  <forward mode='bridge'/>
  <bridge name='br0'/>
</network>
joe@debian:/$ virsh net-list --all
 Name   State    Autostart   Persistent
-----------------------------------------
 br0    active   yes         yes
joe@debian:/$ sudo virsh list
 Id   Name     State
------------------------
 5    hassos   running

Command used to start my hassos instance

sudo virt-install --import --name hassos \
--memory 4096 --vcpus 4 --cpu host \
--disk /var/lib/libvirt/images/hassos-vm/haos_ova-7.5.qcow2,format=qcow2,bus=virtio \
--network bridge=br0,model=virtio \
--graphics none \
--noautoconsole \
--boot uefi \
--os-variant=generic

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: false
interfaces:
- connected: true
  enabled: true
  interface: enp0s2
  ipv4:
    address:
    - 192.168.68.105/24
    gateway: 192.168.68.1
    method: auto
    nameservers:
    - #####
    - #####
    - 192.168.68.1
  ipv6:
    address:
    - fe80::a284:4945:6352:a651/64
    gateway: fe80::ea48:b8ff:fece:7fe4
    method: auto
    nameservers: []
  primary: true
  type: ethernet
  vlan: null
  wifi: null
supervisor_internet: false

Address I have tried connecting to:
http://192.168.68.105:8123

I can however ping 192.168.68.105 from other devices on my network.

I have been stuck on this problem for hours… any input is much apprciated.
Thanks

Nothing is obvious to me, but I have come across reports that netfilters may be applied to the linux kernel bridge by default, so you may want to do some research on netfilters to see if that may be the problem.

You can also see some discussion on this in this community forum thread (as well as the strike-throughs).