Closed nickmomrik closed 6 years ago
I set my router back to the default DNS, rebooted the Pi, and restarted Pi-hole. It loads properly and is able to update the blocklists. I reset DNS on the router to point to the Pi and ads start getting blocked again. If I reboot the Pi, it breaks again.
Seems to be solved by setting the DNS servers in system-connections/resin-sample
which is listed as optional in the Hass.io installation instructions. I would suggest mentioning this in the Pi-hole addon instructions.
@nickmomrik Are you setting the DNS to localhost in this case in the resin-settings?
No that's what you don't want. It needs to go outside to get it's DNS instead of trying to use itself. I'm pretty sure I used the Google DNS servers listed in those docs, which I also use in my Pi-hole config.
This thread has been automatically locked because it has not had recent activity. Please open a new issue for related bugs and link to relevant comments in this thread.
Problem/Motivation
I rebooted my Raspberry Pi. When everything started back up Home Assistant was asking me to authenticate everything again, but wouldn't work. Eventually I disabled the Pi-hole addon and everything else started working again.
Expected behavior
I expect Pi-hole to work after a reboot.
Actual behavior
I can't get the addon to work again after several reboots and reinstalling the addon several times. When I start it, here is the log:
When it's "running" I start getting all kinds of connection errors in home-assistant.log like this...
Steps to reproduce
I started using Hass.io last weekend and this same thing started happening (triggered by a reboot), but I didn't track it down at the time. I reinstalled everything on the Raspberry Pi from scratch and then it started happening again after a reboot.
Anything I should be looking at to fix this problem? Need any more info?