I am struggling to update my Supervisor to 2025.06.1. Here are my logs.
2025-06-26 09:36:40.165 INFO (MainThread) [supervisor.supervisor] Fetching AppArmor profile https://version.home-assistant.io/apparmor_stable.txt
2025-06-26 09:36:40.170 ERROR (MainThread) [supervisor.supervisor] Can't fetch AppArmor profile https://version.home-assistant.io/apparmor_stable.txt: Cannot connect to host version.home-assistant.io:443 ssl:default [DNS server returned general failure]
2025-06-26 09:36:40.170 CRITICAL (MainThread) [supervisor.supervisor] Abort update because of an issue with AppArmor: Can't fetch AppArmor profile https://version.home-assistant.io/apparmor_stable.txt: Cannot connect to host version.home-assistant.io:443 ssl:default [DNS server returned general failure]
I have tried updating my DNS to add 8.8.8.8 and 8.8.4.4, but it changes nothing. My default DNS is 192.168.1.1.
I also checked the health of my Supervisor and it is supposedly healthy.
No. I do not have AdGuard or PiHole running. I am using a UniFi Dream Router. Its address is 192.168.1.1. When I have IPv4 set to automatic, it defaults to that. I changed it to static and made the DNS 1.1.1.1. Still no difference. I keep getting the same error.
I have UniFi Dream Router(Wall) as well.
I get the feeling it is related to that.
I used to use opendns in my internet settings as DNS, but changed this to provider for this issue already. But does not make any difference.
For as far I can see, I set all the vlan settings of that network back to default.
There was a firmware update some days/weeks ago from UniFi…
I switched the homeassistant Raspberry pi lan connection from IOT vlan(10.10.133.x) to 192.168.1.x vlan network on my Unify and got ‘host_internet: true’. Although still ‘supervisor_internet: false’ after couple of retry’s it seems the supervisor is finally updating from 2025.05.5 to 2025.06.2.
Although different ip ranges, both vlans 10.10.133.x and 192.168.1.x have the exact same configuration in Unify router…
Only thing I can think of is that I initially set up the raspberry pi with home assistant on a 192.168.1.x network(different/old router)
I figured that my non-standard network setup may have tripped hass but I tested everything in and out:
ran the update from the command line ha supervisor update
DNS works from the host and from inside the containers
curl can actually download the mentionned file from the host and from inside the containers
explicitly inspecting any blocked traffic at the firewall (pfSense) did not reveal any dropped packet
tcpdump on the host shows that the update does not even trigger a DNS request
I also ran the update in debug mode:
root@host:~# ha supervisor update --log-level debug
DEBU[0000] Adding homedir to searchpath homedir=/root
INFO[0000] No configfile found
DEBU[0000] Debug flags apiToken=35REDACTED6f cfgFile= endpoint=supervisor logLevel=debug noProgress=false rawJSON=false
DEBU[0000] supervisor update args="[]"
DEBU[0000] [GenerateURI] base=supervisor command=update section=supervisor
DEBU[0000] [GenerateURI] Result uri="http://supervisor/supervisor/update" url="http://supervisor/supervisor/update" url(string)="http://supervisor/supervisor/update"
⣾ Processing... DEBU[0000] Response body="{\"result\":\"error\",\"message\":\"Abort update because of an issue with AppArmor: Can't fetch AppArmor profile https://version.home-assistant.io/apparmor_stable.txt: Cannot connect to host version.home-assistant.io:443 ssl:default [DNS server returned general failure]\"}" fields.time=4.058872ms headers="map[Content-Length:[265] Content-Type:[application/json; charset=utf-8] Date:[Thu, 17 Jul 2025 23:32:57 GMT] Server:[Python/3.13 aiohttp/3.12.13]]" received-at="2025-07-17 19:32:57.800628796 -0400 EDT m=+0.006890508" request="&{POST http://supervisor/supervisor/update HTTP/1.1 1 1 map[Accept:[application/json] Authorization:[Bearer 35REDACTED6f] User-Agent:[go-resty/2.16.5 (https://github.com/go-resty/resty)]] <nil> <nil> 0 [] false supervisor map[] map[] <nil> map[] <nil> <nil> <nil> {{}} <nil> [] map[]}" status="400 Bad Request" statuscode=400
Processing... Done.
Error: Abort update because of an issue with AppArmor: Can't fetch AppArmor profile https://version.home-assistant.io/apparmor_stable.txt: Cannot connect to host version.home-assistant.io:443 ssl:default [DNS server returned general failure]
The post here put me on an interesting track: I indeed recently changed the IP addresses of the hass host (because I wanted to get fancy with vlans and all).
Is there anything in the hass setup that maybe keeps track of an IP somewhere that needs to be ‘reset’ ?
I’ll go on searching for the probable IP the host had previously in the files of the containers.
I am not a network guy. I consider myself techy and try to stay up to date with stuff. I have been happy with Unifi. I know it is a love or hate thing, but that is besides the point in my opinion.
I was able to finally update the supervisor and I am not even sure what I did or how it happened. I think I had restarted HA multiple times. The router. Everything. But I never actually just turned off the HA machine and turned it back on. After I did that it seemed to resolve itself.
I don’t use any fancy vlans or anything. I have a default one and a Guest one, but all of my stuff is on the same VLAN. HA, streaming, work computer, etc.
I still did not figure out the root cause. But after the (first)updates went through when set on the original IP when first installing Home Assistant, I changed it back to the new IP that I gave it in the new VLAN. After that I was able to do additional updates again.
Also I had created a virtual machine for Home Assistant on my NAS and restored a backup of the raspberry PI install from above. And on this VM I had the exact problem that I could not update using the new IP from the VLAN.
