I am using piHole just for standard purposes of blocking tracking and so on, no fancy additional features. piHole acts as DNS, DHCP is done by FritzBox.
For family-acceptance-reason, I would prefer it to just work and not stopping to do so from time to time...
Actual Behaviour:
I acutally face two different issues.
piHole Interface suddenly not reachable due to connection refused error. Can be fixed via pihole -r and then works again for some time. This is annoying, but only for me (rest of the family does not care ). I had an issue with log2ram, as the assigned capacity was not sufficient, but I doubled log2ram size and now it seems fine.
piHole completely stops working. Suddenly, client devices cannot reach web pages anymore as they lose their DNS. I then just reboot the piHole device (BananaPi with Armbian) and everything is back ok. When this happens, I can still ping the device, but I cannot reach web interface or SSH.
Inability to access via SSH is typically an OS level issue. I don't see anything in your debug log to pinpoint a cause, but your Pi-hole has been running for 3 days and the Pi-hole logs rotate nightly.
Assuming I would face the issue again and then have to reboot the device to get it back online... would the debug log then provide any insights when being created after reboot?
Or would it be just some sort of "initial" then?
Maybe I need to approach the two issues separately... when I have access problems on the Web UI, SSH is often still reachable... So I could at least provide a debug log on with this particular issue being in place.
So, back there... after a reboot, the interface is again not reachable, connection refused. I managed to get it back ok using "pihole -r", but I created debug log before, so maybe it is possible to identify the root cause:
). I had an issue with log2ram, as the assigned capacity was not sufficient, but I doubled log2ram size and now it seems fine.