HoAs not reachable through Web

Installation
1

Hi there,

I am running HassIO since a good time on Debian12. For some reason I am not able to connect to it as port 8123 for the WebGUI appears to be closed.
I did some troubleshooting but do not know enough from the details so I did not succeed.

When I try to access hoas.server.my on port 8123 I am getting connection refused.
I checked the services on the system:

root@hoas:~# systemctl status hassio-supervisor.service 
● hassio-supervisor.service - Hass.io supervisor
     Loaded: loaded (/etc/systemd/system/hassio-supervisor.service; enabled; preset: enabled)
     Active: active (running) since Fri 2023-09-08 09:10:24 CEST; 1min 18s ago
    Process: 302667 ExecStartPre=/usr/bin/docker stop hassio_supervisor (code=exited, status=0/SUCCESS)
   Main PID: 302672 (docker)
      Tasks: 6 (limit: 4648)
     Memory: 12.1M
     CGroup: /system.slice/hassio-supervisor.service
             └─302672 docker container wait hassio_supervisor

Sep 08 09:10:24 hoas systemd[1]: Starting hassio-supervisor.service - Hass.io supervisor...
Sep 08 09:10:24 hoas docker[302667]: hassio_supervisor
Sep 08 09:10:24 hoas systemd[1]: Started hassio-supervisor.service - Hass.io supervisor.
Sep 08 09:10:24 hoas hassio-supervisor[302672]: [INFO] Starting the Supervisor...
Sep 08 09:10:25 hoas hassio-supervisor[302693]: hassio_supervisor

I even restarted Docker service, still no success.
I can confirm there is no process listening:

root@hoas:/var/log# netstat -anp| grep LIST
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      577/sshd: /usr/sbin 
tcp        0      0 0.0.0.0:4357            0.0.0.0:*               LISTEN      302561/docker-proxy 
tcp        0      0 127.0.0.54:53           0.0.0.0:*               LISTEN      463/systemd-resolve 
tcp        0      0 127.0.0.53:53           0.0.0.0:*               LISTEN      463/systemd-resolve 
tcp        0      0 0.0.0.0:5355            0.0.0.0:*               LISTEN      463/systemd-resolve 
tcp        0      0 0.0.0.0:8086            0.0.0.0:*               LISTEN      303827/docker-proxy 
tcp        0      0 0.0.0.0:8088            0.0.0.0:*               LISTEN      303771/docker-proxy 
tcp6       0      0 :::22                   :::*                    LISTEN      577/sshd: /usr/sbin 
tcp6       0      0 :::4357                 :::*                    LISTEN      302568/docker-proxy 
tcp6       0      0 :::5355                 :::*                    LISTEN      463/systemd-resolve 
tcp6       0      0 :::8086                 :::*                    LISTEN      303832/docker-proxy 
tcp6       0      0 :::8088                 :::*                    LISTEN      303779/docker-proxy

Anyone having an idea how to get the frontend up and running again?

Thanks

/KNEBB

2

After a reboot it is working again.

I have a python3 process listening on port 8123.

So my question: What can I do to get this up and running without rebooting?