Please follow the below template, it will help us to help you!
Expected Behaviour:
I expected that the FTL service would run as it has for years. I have recently followed the instructions to setup DNS over HTTPS (Redirecting...). After doing that my FTL service will no longer stay active on its own.
Actual Behaviour:
Whenever I go to the IP-address/admin (cause pi.hole won't work) it says "lost connection to API". It also says that the FTL service is not running. At that point, if I run "sudo service pihole-FTL restart" or "sudo reboot" everything starts working again. But it will only work for a couple of hours and I have to do it again.
Any help is appreciated.
I really don't enjoy having to check that every couple of hours to see if it is working. I guess I could create an alias so its easy to restart the FTL service, even have it run automatically every hour or so.
It might be worth mentioning I am also using pivpn. I am not certain what things may be interfering with each other so I want to just put it all out there.
I am happy to provide any other information as requested though you may have to tell me exactly what command to run to get the necessary info. Thanks guys for an awesome piece of software
Your debug log shows that you added a number of block lists, which are blocking almost 3.8 million domains. There is a possibility that you could be running out of memory, as Pi-Hole carries the gravity list in memory.
Take a look in htop or top and see how much memory is free.
Also, when FTL stops working, there may be an error entry in one of these logs. Review the logs for any error messages:
As long as you have free memory, you aren't having a problem. You have about half your memory available, so I don't think memory is the problem here.
Since you recently installed DoH and it worked prior to this, it is likely that the problem is related to this new install. As a test, I would revert back to your previous upstream DNS server and see if the problem resolves. That would eliminate one potential source of the problem.
I will try reverting after I get the error to occur again so that I can check those logs.
It seems to happen somewhat frequently like at least a few times a day so I will report back with the logs to see if it is something obvious. If it is not obvious I will revert and let you know if the issue stopped occurring. Thanks for looking into it.
