I’ve been running for several years on an HAOS install on a VM in Proxmox, probably installed via ISO, and with one of the July updates, I’m getting notifications that I am running an unsupported supervised installation. I believe it showed up with the most recent update where it’s reporting no OS Version, supervisor-2026.07.5, and core-2026.7.4. Is something wrong with my install, or is there a problem with the detection? I have attached a screenshot from the proxmox console as well.
32 bit is now unsupported if that is what your running?
That can’t actually be the case, because the supervisor version actually no longer exists since Core 2025.6 and you would have received corresponding messages about it since and last year.
So the question is what version exactly have you installed under Proxmox? A screenshot of the HA VM Console under HA isn’t that good either; the system information from HA would be better. Current example from me here:
It shows installation type “Home Assistant Supervised”, which it’s not, and I agree it can’t actually be the case. It was installed with Home Assistant OS. I suspect something in one of the recent releases is causing it to detect the installation is Supervised when it’s not. I’m at 6.18.37-haos, and yours is at 6.18.39-haos, but I don’t even see that as an option to update to,
Also seeing these two messages in settings. Is the systemd message the real root cause for all of this??
I found the issue.. systemd was indeed at the root of the problems.. I had made some L3 changes on my network which resulted in my DNS server not being reachable at the same IP it was on previously (on OPNSense, and used to be on multiple VLANs, L3 moved to VyOS inside the firewall now). I had forgotten that while I had a DHCP reservation for my Home Assistant, it was in fact statically configured with a statically assigned DNS server, so the inability to reach DNS lead to systemd failing, and then I assuming the other errors. Fixing DNS and rebooting the VM resolved the issue. I suspected a recent update, and it was a recent network change.
… it’s always DNS …
I haven’t had to fight DNS issues previously with HA, and the errors I was seeing didn’t scream DNS to me because I don’t know enough about how that validation process works, so it took me a little longer to figure that out.
Yeah, for me too, it’s actually not been real common to encounter DNS issues with HA (other than mDNS). But I’ve been around network folks enough (& once used to be one) that the phrase has stuck with me for troubleshooting situations.