Please follow the below template, it will help us to help you!
Expected Behaviour:
Pihole should happily run and do its merry little thing on its own, with no disruption.
Actual Behaviour:
After 11 months of good behavior, in the last few days my raspberry pi that is running pihole just seems to 'lock up'. The only light on it will be red, and there will be no communication lights around the ethernet port. My desktop will no longer have access to the internet, and can not communicate with the pihole through the browser interface. On my modem, I can't see the pihole connected.
I restart the pihole with the power on/off switch on the powercord, restarting the raspberry pi, and it works fine again with nothing else needing to be done. Just turning it off and on gets it going again.
Debug Token:
I will provide this when I get home to try and get it!
I am not the most tech saavy, and have only bought a raspberry pi to use for this purpose. I love it, and would greatly enjoy getting it working hasslefree again!
It is erratic how long it works before not working again; For example I reset it this morning when I woke up, and about 6 hours later it froze up again.
First make sure not too many power hungry USB devices are connected directly to Pi.
Disconnect all USB devices that are not necessary for the working of Pi-hole.
If that wont help, try changing AC power adapter and/or the USB cable between Pi and AC adapter.
I appreciate the response.
There is currently nothing plugged into the Pi except for an Ethernet cord and the power supply; I will swap the adaptor/cable out and see if that makes a difference.
It wasn't even that complicated. I connected my display and realized that the yellow lightning bolt symbol in the top-right corner means under-voltage. I thought that was a normal thing until this thread!
Swapped to a different power supply for a tablet, and it went away. Thank you and appreciate the quick help, I hope all my problems are this easy.
When you report that the "internet" failed, presumably actually only name service had failed.
It's usually worth testing with "ping 8.8.8.8" (ping to the numeric address of google DNS) from a client system on your local network.
That ping request should get responses as long as the IP link to the internet is functional, as it does not require functional name service to work.
If "ping google.com" fails (with a name issue usually) while "ping 8.8.8.8" gets responses, your IP path to the internet is functional, and the issue is probably in your local network.
Conversely if the ping to 8.8.8.8 fails you probably have a network issue to contend with, and potentially a failure outside your network.