## Expected Behaviour:
I installed Pi-hole about a year ago and have experienced these restart problems basically from the beginning. I have been too lazy to actually write a post about it on this forum so here I finally am. I'm not a technical expert so this might come across as somewhat noob'ish.
I run Pi-hole (version 5.3.1) on a Raspberry Pi Zero 1.3 that uses a 2A Micro USB charger. I installed it using this guideline: https://linustechtips.com/topic/1094810-pi-hole-setup-tutorial/ and use it on specific devices like my iPhone 7 and iMac (macOS Big Sur 11.4). So, I do not use it on my entire network. I use Cloudflared as my upstream DNS resolver (127.0.0.1#5053).
The expected behaviour basically is that Pi-hole runs without needing it to get restarted every morning (and sometimes multiple times on 1 day).
## Actual Behaviour:
The problem I have with using Pi-hole is that I usually have to restart it every morning and sometimes during the daytime because it doesn't resolve any websites at that specific instance. I sometimes notice that websites do resolve on my iMac and don't on my iPhone. I'm not sure whether this is a coincidence or part of the problem I have.
Once I experience the above problem I always restart the system (Pi-hole) which makes it work properly again. I don't want to automatically restart Pi-hole every morning because that circumvents the cause of the problem which I would really like to resolve.
## Debug Token:
I ran the debug script the moment DNS didn't resolve (above problem) which I saved on my local computer because I didn't receive a token ID once the script was done. If you could explain to me how I could upload this to the Pi-hole team properly, that would be great.
I could run the script while Pi-hole runs successfully of course but I assume that wouldn't get me the same result as when it is experiencing the above problem.
Again, if I forgot to mention something or if you need any more information just let me know.
If you run the pihole -d command from the command line, at the end of the script you will be asked if you want to upload the log. Answer yes, the log should upload and you will receive a token in exchange.
...
********************************************
********************************************
[✓] ** FINISHED DEBUGGING! **
* The debug log can be uploaded to tricorder.pi-hole.net for sharing with developers only.
* For more information, see: https://pi-hole.net/2016/11/07/crack-our-medical-tricorder-win-a-raspberry-pi-3/
* If available, we'll use openssl to upload the log, otherwise it will fall back to netcat.
[?] Would you like to upload the log? [y/N] y
* Using curl for transmission.
***********************************
***********************************
[✓] Your debug token is: https://tricorder.pi-hole.net/zB8hS05C/
***********************************
***********************************
* Provide the token above to the Pi-hole team for assistance at
* https://discourse.pi-hole.net
* Your log will self-destruct on our server after 48 hours.
* A local copy of the debug log can be found at: /var/log/pihole_debug.log
I answered yes once I ran the script during the DNS resolving problem. However, since I didn't have internet access at the time, I guess the log didn't get uploaded and I didn't get a token ID.
Is it useful to run it right now despite the fact that everything runs smoothly now (I don't have the above problem right now)?
I tried to re-install cloudflared but couldn't get it to work again. I'll try to use recursive from now on. Might be a good idea to upgrade my Raspberry Pi Zero 1.3 to a proper Raspberry Pi as well in the future. Thanks for your help anyway @jfb .
Output from /var/log/syslog:
==> /var/log/syslog <==
Aug 21 20:10:45 raspberrypi systemd[15030]: Reached target Basic System.
Aug 21 20:10:45 raspberrypi systemd[1]: Started User Manager for UID 1000.
Aug 21 20:10:45 raspberrypi systemd[15030]: Reached target Default.
Aug 21 20:10:45 raspberrypi systemd[15030]: Startup finished in 913ms.
Aug 21 20:10:45 raspberrypi systemd[1]: Started Session c15 of user pi.
Aug 21 20:10:45 raspberrypi cloudflared[374]: time="2021-08-21T20:10:45+01:00" level=error msg="failed to connect to an HTTPS backend "https://1.1.1.1/dns-query\"" error="failed to perform an HTTPS request: Post https://1.1.1.1/dns-query: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)"
Aug 21 20:10:47 raspberrypi cloudflared[374]: time="2021-08-21T20:10:47+01:00" level=error msg="failed to connect to an HTTPS backend "https://1.0.0.1/dns-query\"" error="failed to perform an HTTPS request: Post https://1.0.0.1/dns-query: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)"
Aug 21 20:10:49 raspberrypi cloudflared[374]: time="2021-08-21T20:10:49+01:00" level=error msg="failed to connect to an HTTPS backend "https://1.0.0.1/dns-query\"" error="failed to perform an HTTPS request: Post https://1.0.0.1/dns-query: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)"
Aug 21 20:10:50 raspberrypi cloudflared[374]: time="2021-08-21T20:10:50+01:00" level=error msg="failed to connect to an HTTPS backend "https://1.0.0.1/dns-query\"" error="failed to perform an HTTPS request: Post https://1.0.0.1/dns-query: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)"
Aug 21 20:10:53 raspberrypi cloudflared[374]: time="2021-08-21T20:10:53+01:00" level=error msg="failed to connect to an HTTPS backend "https://1.1.1.1/dns-query\"" error="failed to perform an HTTPS request: Post https://1.1.1.1/dns-query: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)"
