but port 8123 is closed, as shown by this nmap scan output
❯ nmap homeassistant.local -p 4357,8123
Starting Nmap 7.80 ( https://nmap.org ) at 2022-08-07 14:21 CDT
Nmap scan report for homeassistant.local (192.168.86.34)
Host is up (0.00062s latency).
Other addresses for homeassistant.local (not scanned): fe80::1388:c38:347:3f9
rDNS record for 192.168.86.34: homeassistant.lan
PORT STATE SERVICE
4357/tcp open qsnet-cond
8123/tcp closed polipo
Nmap done: 1 IP address (1 host up) scanned in 0.08 seconds
How do I get the supervisor to listen properly on port 8123? I didn’t find anything about this in the installation guide or docs.
Is there some way to break out of this ha > command prompt to a Linux shell, so I can at least try curling the url from localhost to see if it’s running at all?
Ok I figured it out. You can type login at the ha > prompt to get a shell. And supervisor is definitely not listening on port 8123, even though the “observer” shows healthy status
This is as far down the rabbit hole as I’m able to go - it appears there is a HostPort config for the observer, but not for the supervisor. /mnt/data/docker/network/files/local-kv.db also has nothing about port 8123.
There should be a container named homeassistant, this one is responsible for the UI running on port 8123. This one seems to be missing on your installation. You should run docker logs hassio_supervisor to check for errors.
Nothing there in the logs. I think Virtualbox is too janky for this app. I’d try VMware workstation but it looks like it costs $199 for a license to run the “pro” version now.
What is the recommended / officially supported hardware configuration for this app? As in, tested, known working, or even better comes with home assistant pre-installed?
I’m sorry to say it but the new user experience here is pretty terrible. You shouldn’t have to dive into docker logs to get a simple virtual disk image working.
I gave this one last shot with Hyper-V. Same issue, there’s no container called “homeassistant”. And this is in the log output for docker logs hassio_supervisor:
If yes, could you try to get to your “System Health” page? Should be under the new “Repair” dashboard, and then inside the menu around the upper-right corner.
