Ok I am running HA in a Linux Virtual Machine run on a Mac OSX hot (sonoma). The current setup is HA OS 13.0 and core 2024.9.2. With the update to 2024.9.2. I started getting stuck in the look with the CLI won’t start If I do get is started. I can not access via port 8123. but I can observe via port 4357. The update to 2024.9.0 killed insteon… Thought and prayer would be appreciated. I Have lost so much core functionality thinking about building a new VM
Hi ason hirsh,
First I know nothing about VM’s. I do know that everything in a VM has to be passed thru the machine frontend. Is the network bridge and all the stuff in the VM side still passing thru properly?
Other than that, I am no help.
Hey any response in this community is appreciated/. All the front end setting are the same they were before the updates. I restored a snapshot from before the updates to core and OS. I have given some thought to going with HA Red. but I realllllly don’t need to be hosting another box. I already have. 3 Mac OS boxes
with all its warts and a FreeBSD server. Also have given some thought to returning to Indigo. I used that till they abandoned applescriot for Python. Again thanks for the edits and taking time out for a response 
I’m running HAOS in a linux VM and just tried upgrading to the 2024.9.2 release. Now the web interface (at least) is not functional. I’ve restarted the VM, and it is running, but it would seem the service is not running on the VM. And it looks like the VM is running a bunch of Docker containers to boot.
No changes have been made to the firewall. All ports are open to the VM and on the VM to the Docker images.
Observer on 4357 seems to be functional. So it looks like I’m in the same boat as OP.
Ok I sort of fixed my installation by restoring a core pre 2024,9. snap shot. That required re-installation of the core updates. During the process I changed my VM to start headless. I read somewhere that this could solve the ;8123. issue. This worked in getting access back. Of course a lot of clean up afterwards
I figured out my issue. Turned out to be an errant ssl configuration in /mnt/data/supervisor/homeassistant/configuration.yaml. Somehow there were suddenly two lines for ssl parameters which were invalid. This caused the frontend to not start up. Below are the lines, now commented out. After commenting them out, core started and the frontend became accessible again.
Also, during this time, I figured out that /var had filled up, causing the VM to constantly be suspended.
`
http:
ssl_certificate: /ssl/fullchain.pem
ssl_key: /ssl/privkey.pem#
`