Backups seem to complete, but spinner never stops... | Home Assistant | Page 1

silent frigate Apr 1, 2025, 4:12 PM

#

I've had this issue since the "new" backup system was introduced. Basically any backup (auto or manual) seems to complete (per supervisor logs and backup lists) but HA must not get the message. As the spinner runs forever and it's not possible to make further backups without restarting HA.

I'm running HAOS on a Proxmox VM and have updated Supervisor throught he latest 15.1 hoping it would resolve, but no lock. The one thing that seems supsicous in the Supervisor logs is the following (which others with my same probablem seem to see also).

Note the "No Home Assistant Core respose" items..

2025-04-01 09:57:22.669 ERROR (MainThread) [supervisor.homeassistant.core] No Home Assistant Core response, assuming a fatal startup error
2025-04-01 09:57:22.669 ERROR (MainThread) [supervisor.core] Can't start Home Assistant Core - rebuiling
2025-04-01 09:57:22.671 INFO (SyncWorker_4) [supervisor.docker.manager] Stopping homeassistant application
2025-04-01 09:57:29.257 INFO (SyncWorker_4) [supervisor.docker.manager] Cleaning homeassistant application
2025-04-01 09:57:29.407 INFO (MainThread) [supervisor.homeassistant.module] Update pulse/client.config: /data/tmp/homeassistant_pulse
2025-04-01 09:57:29.548 INFO (MainThread) [supervisor.docker.homeassistant] Starting Home Assistant ghcr.io/home-assistant/qemux86-64-homeassistant with version 2025.3.4
2025-04-01 09:57:29.548 INFO (MainThread) [supervisor.homeassistant.core] Wait until Home Assistant is ready
2025-04-01 09:57:34.892 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state startup
2025-04-01 09:57:34.892 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete
2025-04-01 10:00:29.814 ERROR (MainThread) [supervisor.homeassistant.core] No Home Assistant Core response, assuming a fatal startup error

If I go into the shell on the Supervisor container I can ping Home asssistant, so it seems ok Docker network wise. Not sure where to head next though?

silent frigate Apr 1, 2025, 8:15 PM

#

So this comes down to using http.server_host in HAOS. Basically supervisor seems to be using the Docker network IP to reach the Core UI. But I want the Core UI to just be on my VLAN that has all my NGINX proxied apps. I don't see any way to set multiple IPs/interfaces for the UI or specifiy what IP Core tells supervisor to use. So I guess with HAOS it must bind to all interfaces. 😦

lilac grotto Apr 1, 2025, 11:00 PM

#

silent frigate So this comes down to using `http.server_host` in HAOS. Basically supervisor s...

perhaps add another network adaptor to the vm on proxmox thats bridged to the same adaptor. that would give you multiple interfaces?

silent frigate Apr 2, 2025, 6:17 PM

#

lilac grotto perhaps add another network adaptor to the vm on proxmox thats bridged to the sa...

Thanks for the suggestion. 👍 I actually have two adapters currently. One on the main LAN to access devices, etc. The other on a private VLAN I just use for non-encrypted services that are proxied through NGINX. The problem is with HAOS I can't tell HA to just put the UI on the private VLAN interface. Before HAOS (when I was just using straight Docker) I could use http.server_host to limit it, but now that kills communications from Supervisor to Core if I restrict things with that (and it can't have specific multiple interfaces). Basically it has to include all interfaces with HAOS from what I've seen. So for now I just made a Proxmox firewall rule on my LAN inteface to block that HA UI port. Feels a little hackish, but it works 😅

#Backups seem to complete, but spinner never stops...