As a result of this error, Home Assistant no longer notifies me of updates or am I able to install updates from the CLI.
Of course, the first thing I did was search around and found several other topics on this issue, all with different resolutions, but none have worked for me.
Some important additional information:
I was first using the Adguard add-on and had it configured as the DNS for my clients in my Draytek router (both under WAN and LAN settings).
When I change the DNS servers to 1.1.1.1, 8.8.8.8 or 9.9.9.9 in my router the problem is gone and I can update HA again.
I removed Adguard and installed pi-hole, but had the issue.
I pi-hole I changed the setting to Listen on all interfaces, permit all origins, this did not resolve the issue for me.
I power cycled the my device multiple times, this did also not help
Result of CLI command ha dns info:
locals dns://
servers dns://1.1.1.1
So, when I configure a public dns server on my router I don’t have the problem but when I configure pi-hole or adguard to be used, I keep getting the error.
yes, i’m having the exact same problem.
Only changing the dns setting on the router helps.
After updating i point it back again to the adguard / hassio ip.
just installed another home assistant installation with adguard and pointed the dns settings of my router to this new instance. let’s see if this will work. if it does, we have to find the problem why the adguard dns is not working when it’s on the same host as home assistant
I switched (back) from Adguard to Pi-hole and now I no longer have the issue. Updates are now visible again and can be installed. I did configure p-hole to listen on all devices and allow all clients. Not sure if this had any affect.
Similar problem on my hassio box since I installed a unity edgerouter as router to replace my old apple airport extreme. Very annoying.
When I log in on the hassio and perform a “host github.com” or any other server, it can find the IP address of that server. An update of homeassistant through the command line only worked when I actually defined the version number; an upgrade of hassos doesn’t work.
In the “supervisor” page on home assistant web gui it now states that a newer version of home assistant is available which is actually older than my current version - this means for me the version files do not get updated…
As an alternative/workaround: is there a way to manually fetch and install the version files?
Got the same problem.
Updated manually to 0.106.6, but now it is showing an older version (0.106.2, the one I started having problems with) as newer version. Funny enough, binary_sensor.updater is off, so in some way the system is working correctly.
I changed my provider, and so my router. I can’t put a custom public dns in the router configuration, tried to put dns configuration in Hassio, I think I managed in doing that, but still could not update via gui.
I’ve been having the same issues and I just fixed it. The problem with mine was that the supervisor version was stuck also at 195. I did “hassio ha update” and “hassio supervisor update --version 209” When I logged back in (which was a nightmare because DNS also got screwed up), BUT when I logged in I now had a message to update the OS version to 3.12 which I have never seen as an option before. Prior to this it was suggesting to downgrade to home assistant 0.104.0b0.
I think somewhere along the line the different core, supervisor, and OS became screwed up / mismatched.
I had exactly same issues. Spent ages messing about with DNS settings and manually updated HA core only for it to tell me the version I had issues with was the latest available update.
I followed above advice and update supervisor to next available version and this fixed my DNS issue ha supervisor update --version <next_supervisor_version_available>
