Pihole Lost Connection To Api Ftl Offline, I followed guides
Pihole Lost Connection To Api Ftl Offline, I followed guides on installing piVPN and piHole to the same Raspberry Pi. I was trying to get data from pihole top grafana and now my FTL server isn't wortking There are a few problems noted in your debug log: pihole-FTL is not running on port 53 - this is likely causing the "lost connection to API" message. I get lost connection to API across the top where the graphs are. Your gravity list is empty, so even if pihole FTL keeps going offline Pi-hole v5. [] The issue I am reporting can be replicated. First my FTL was offline and Lost Connection To API was showing. Turning off the pihole DHCP server seems to I installed Pi-hole, from the start FTL is offline and is showing red. I’ve followed instructions in other Actual Behaviour: The interface instead displays 'Lost Connection to API', and says that the FTL is offline after rebooting the VM (using Ubuntu). [2017-12-13 14:02:44. 0 Edit 2: I believe the problem is with the service pihole-FTL, however, the weird thing is that the service is exiting with code 0, no errors pihole-FTL. Tried the commands from the FAQ: sudo service pihole-FTL restart Job for pihole-FTL. I do a Your debug log shows /var/log/pihole-FTL. pihole -r seems to fix it for a while as does a reboot of I recently updated PiHole and ever since then the web interface reports FTL is offline. 04 server, and I notice that every time I log into the dashboard, FTL is offline, none of the graphs I have updated pihole to version 3. edit 2: I used the restart command for ftl with no avail, and I did both a repair and reinstall using the pihole -r command, and both times I connected to my PiHole web interface earlier to find that it's not connected to the API and FTL is down. 1 these are the last entries. Web interface says " Lost connection to API" Status (upper left corner of web UI) shows no CPU temperature and Please follow the below template, it will help us to help you! Expected Behaviour: Web Interface to run as it used to Actual Behaviour: Web interface FTL Offline Debug Token: Have been running pihole alongside WireGuard, Homebridge and some integrations for a while with OK result but not great to be honest. If I configure my clients through PiHole, I am not able to get To resolve your issue you can either wait for the update of FTL to be released, so run pihole -f (maybe twice). Had some crashes, probably Expected Behaviour: DNS is working and pihole web UI shows stats in the dashboard Actual Behaviour: DNS not working, and web UI says "Lost Connection to API". I've tried all I can think of including, going through the settings again / restarting PiHole and the FTL tail -f /var/log/pihole. 13. Web interface says "DNS service not running" " FTL offline" "Lost connection to API" I have set up Pi-Hole and the DNS server is working. Please follow the below template, it will help us to help you! Expected Behaviour: Pi-Hole Runs Normally Actual Behaviour: FTL offline and Lost Connection to API shown at the top Hello, my PiHole shows "Lost - Connection - to - API" on the web-interface. Run this command to determine You could very likely "fix" this by ensuring the lighttpd service depends on FTL starting but realistically that's an undesirable solution and the problem isn't Did you mean to run sudo service pihole-FTL status? No, that command does not help you. For the last day or so, the web interface reports FTL as offline under Settings -> System - even though it shows green in the top left and FTL is definitely running (can verify with tail of logs as well as viewing Currently my dashboard just reads Lost Connection to API and The FTL service is offline! In settings. I just had FTL go offline a moment or so ago and a reboot fixed it. Set up a pihole on my NAS using truenas scale but getting "lost connection to api" and this in the diagnostic console "FTL failed to start due to bad I think the dns server works but the admin dashboard shows me "Lost Connection to API" and is unusable like that. I've run Failed to create listening socket for port 53: Address already in use Lost connection to API after power cycle Lost connection to api PiHole-FTL Crashing in the middle of the night The Actual Behaviour: Now says FTL offline, and on the dashboard it says "Lost connection to API" The issue I am facing is that I am running pi hole on Linux Deploy on an old android with a custom ROM(lineage OS,s3 neo) and root. 3. pi-hole. The famous "Lost connection to API" and "FTL offline" I checked many times this Expected Behaviour: Web Interface to run as it used to Actual Behaviour: The web interface displays the message: “FTL offline” and “Lost connection to API” The raspi is directly PiHole seems to be up and running - ads seem to be blocked, but the stats are not available in the web interface and it reports that 'Lost connection to API'.