You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After reboot Pihole can't update Gravity -- all connections were refused. It didn't answer to any requests, all of them were refused.
All dig commands finished with an error. If I use external DNS server, e.g. dig @8.8.8.8 google.com it was ok.
Here is debug log: https://sitnikov.eu/pastebin/J21uAtL_nIILL_Xl0boxs
Only what helped is to update netplan and add there google DNS:
network:
version: 2
ethernets:
enp5s0:
addresses:
- "192.168.0.9/24"
nameservers:
addresses:
- 192.168.0.9 # This is Pihole Server
- 8.8.8.8 # This what I add to solve the issue.
search:
- fritz.box
gateway4: 192.168.0.1
And Pihole Diagnosis is full of following error:
2024-03-01 23:12:06 DNSMASQ_WARN Warning in dnsmasq core:
ignoring nameserver 192.168.0.9 - local interface
Check out [our documentation](https://docs.pi-hole.net/ftldns/dnsmasq_warn/) for further information.
IDK why it was broken, but basically I tires pihole -r, but repair fails with an error Unable to reset /var/www/html/admin, exiting installer. This was "expected" as I do use my own webserver.
However I run it again and select "reconfigure" goes over wizard with no changes done, all defaults and pihole seems working again. From this point of view Ticket could be closed, however if you still have time to check logs to understand why it happens and how to avoid it. I will appreciate it. 🍺
Versions
Platform
Expected behavior
After reboot Pihole can work as expected.
Actual behavior / bug
After reboot Pihole can't update Gravity -- all connections were refused. It didn't answer to any requests, all of them were refused.
All
dig
commands finished with an error. If I use external DNS server, e.g.dig @8.8.8.8 google.com
it was ok.Here is debug log: https://sitnikov.eu/pastebin/J21uAtL_nIILL_Xl0boxs
Only what helped is to update
netplan
and add there google DNS:And Pihole Diagnosis is full of following error:
Steps to reproduce
Steps to reproduce the behavior:
Debug Token
Screenshots
The text was updated successfully, but these errors were encountered: