--Note - I am a new user to pi and development etc. If you have a solution to my issue, please explain in layman's terms!
Pi-hole randomly stops working(not 100% sure if its pi-hole or my network).
Pi-3b with raspberry pi lite
No actual errors but any device using the DNS server for pi-hole that I set up will not be able to connect to the internet.
Can anyone assist me with this issue? This time it ran for about a day and a half and then just stopped. I had to reboot the server again.
Please send us a new debug token, as your old one has expired.
It ran for almost 7 days this time without issues and then stopped. I had to reboot it.
Your debug log shows your Pi-hole to be configured for your RPi's eth0 network interface.
That interface is down:
*** [ DIAGNOSING ]: Network interfaces and addresses
2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000
*** [ DIAGNOSING ]: Networking
[✗] No IPv4 address(es) found on the eth0 interface.
[✗] No IPv6 address(es) found on the eth0 interface.
Check if your RPi's ethernet port is properly connected, and make sure the cable isn't faulty.
If you intend to connect through your RPi's wlan0 interface instead, run
pihole -r
with Reconfigure for the correct interface.
I question the problem being the ethernet cable/connection as I never had an issue until setting up the pi-3 with pi-hole. Not saying it couldn't be, but it's run fine for at least 10 years with zero issues.
When you say I can switch to Wlan0 interface, I assume that means I could run the pihole -r command for the pi and then turn on my wifi on the computer and turn off the ethernet?
I am not literate when it comes to networking but can make my way around computers.
Only switch to wlan0 if you have been intending to use it.
But you sound more as if you have always been using eth0 in the past, and in that case, you'd have to find out why that interface is down.
Switching your ethernet cable for a known good one would be an easy way to verify whether the cable would cause it, or maybe the socket has lost its grip and the cable is just loosely attached.
Another cause may be a misconfigured interface, e.g. if you'd assigned the same IP address to both your wlan0 and eth0 network, or if your aspired IP (192.168.1.33) would collide with other devices, or if your RPi's ethernet port or that of your other-end router or switch would be failing,...
None of those issues would be related to Pi-hole, but rather to networking in general, so it may be recommendable to additionally consult other forums as well. That's not to say we wont' continue to try to help you here, but our main area of competence is Pi-hole. Forums specialising in your OS's networking may have quicker or better suggestions.
That is starting to make sense. I set the IP address for the Pi-hole to a static IP in my router's web settings. I wonder if that is causing issues. Thank you for the guidance, it should help me get started and move in the right direction.
This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.