Putting in the DNS Records in the resolved.conf and then hitting ha network reload did the tricks!! You guys saved me a lot of pain - big thanks!
I love yoooouu!
1 Like
for me, I had my HAOS connected to my PC’s ethernet port because I had just finished setting it up and used my PC’s internet during the installation proccess. I needed to connect it to my router’s ethernet in order to install addons.
Solved. My router was giving each DHCP client a FILTERING DNS server 9.9.9.9 After changing the DNS server to 8.8.8.8 (Google, non-filtering) my home assistant booted correctly.
Tested 2x first with the wrong SSD then with the right SSD.
set DNS (in ha app network menu, not tweaking with resolv.conf via ssh…) to 1.1.1.1 did the trick… But strangely, when later, I tried to set it back to my router’s address which act as primary DNS and still it was working, even after reboot!
No idea,what this to-and-fro manoeuvre fixed but it fixed it.
I prefer by far this way so I have DNS control centralized in 1 place…
In my case I was getting the error of supervisor not having internet access when I was trying to recover add-on back-up.
Now it works flawlessly with original settings = router’s address