Over the last couple of updates I’ve struggled to get them to complete. The last update to 5.1 crashed my VM multiple times and ended up with me having to update in safe mode. This time even that isn’t working, it starts to update, clearly looks like it has restarted and the companion app loses connection, then it never comes back up. I can’t see anything in the logs either, and the only way to get it back is to restart the VM and it’s magically back at the old revision. Am I the only one having this?
The upgrade on my HA VM from 2025.5.1 to 5.2 took two tries before it completed successfully. I didn’t look to see why it failed the first time, other than noticing that it rebooted and was still 5.1 so I tried again. Another strange thing is that the pending Matter 8.0.0 update vanished with the first failed 5.1 → 5.2 update, and I’m apparently still running on Matter 7.0.0…
Same here.
Lately I always have to try it twice - I tend to use the command line of my VM - first try with “core update” results in a rollback (you can check the supervisor logs), second one with a slow reboot (and a fatal error with no response from the core) mostly works - after another reboot everything is back.
My update to 5.2 has borked, for about a week port 8123 has responded then stopped responding after a few hours and all data logging has stopped. Running ha core check from the CLI had no effect, restarting the supervisor sometimes restarted port 8123 activity, but now restarting the Proxmox VM is having no effect - have now tried ha supervisor repair, followed by ha supervisor reload to see what happens.
Uptimes for devices in the logbook are hours / minutes instead of weeks, even over the past couple of days when I’ve not been trying to fix it. Have given the VM another GB of RAM, now up to 4.88. Will update this post with progress. This all started after an attempt to update to 2025.5.2. The core is reporting 2025.5.2, supervisor is 2025.5.1.
I confirm: updating to 2025.5.2 leads to unstable operation - after a few hours (the first time) and after 2 days the second time the system simply stops responding. The logs contain entries like “addon_core_configurator[710]: WARNING:2025-05-20 13:08:52,516:hass_configurator.configurator:HTTP Error 502: Bad Gateway”. After rebooting the system, HA cannot find plugins, in general the dashboard is full of errors. The only thing that helps is rolling back to 2025.5.1.
and the core is reporting 2025.5.2, supervisor is 2025.5.1
That’s exactly the condition I am seeing, I tried an update to 2025.5.2 which seemed to complete ok. Before being able to see the system was properly working I managed to trip the power to all my computing systems - I was hoping that wasn’t the cause, and now I am sure it wasn’t.
Trying to figure out how to rollback. I do have backups.
Treid a rollback to 2025.5.1, still broken 
Now this happened on version 2025.5.1 too.
Something happens in the container, after which it stops responding.
2025-05-27T10:24:04.943609+03:00 race-home-assistant hassio_supervisor[710]: #033[33m2025-05-27 10:24:04.942 WARNING (SyncWorker_7) [supervisor.docker.manager] Can't restart homeassistant: 500 Server Error for http+docker://localhost/v1.47/containers/c50568875fc2c96a0ea83ddf91318f18dd696b793a5dd31f96041f873f63daf8/restart?t=260: Internal Server Error ("Cannot restart container c50568875fc2c96a0ea83ddf91318f18dd696b793a5dd31f96041f873f63daf8: tried to kill container, but did not receive an exit event")#033[0m
[10:20:28] [root@race-home-assistant$ docker logs homeassistant
s6-rc: info: service legacy-services: stopping
s6-svwait: fatal: timed out
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
[10:21:00] [root@race-home-assistant:/var/lib/docker/containers/ $ docker stop homeassistant
Error response from daemon: cannot stop container: homeassistant: tried to kill container, but did not receive an exit event`
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
c50568875fc2 ghcr.io/home-assistant/qemux86-64-homeassistant:2025.5.1 "/init" 6 days ago Up 4 days homeassistant
I am also having a problem updating my PI 5 running portainer. When I try to update to 2025.5.4 my system will not restore. The normal IP address for the PI also changes. I have tried to login to the system with the new IP but that also does not work.
Same here, I’ve installed HAOS from the install script [Proxmox VE Helper-Scripts], twice, and restored the backup from my original broken install, both died in the same way, unresponsive on port 8123. So I’m going to try another build and then a partial restore… If that fails it will be a full new install and a manual recovery from the data I can get off the original system when its operational. My backups are on a NAS drive BTW.