FTL offline - Lost connection to API

Hi, all. A while ago Pi-Hole stopped working and I tried to reinstall it, but I can't get it to work again.
Normally I'd do a complete reinstall of Rasbian, but I'd rather not this time, since I use the raspberry pi as a server in an on-going project.

Thanks in advance!

Expected Behaviour:

Pi-Hole working

Actual Behaviour:

Pi-Hole doesn't do anything, because FTL is offline.

Debug Token:

https://tricorder.pi-hole.net/wp2nbdjb8g

Accord to your debug log, everything looks fine and in working condition.

When the error occurs, capture (and share) the output of sudo systemctl status --full --no-pager pihole-FTL.service.

That might give us a clue on what's going on.

Right now, it seems to be up and running without any issues.

Thanks for your quick reply!

I get this when I open my admin page

and this is the response to your request:

pihole-FTL.service - LSB: pihole-FTL daemon
   Loaded: loaded (/etc/init.d/pihole-FTL; generated; vendor preset: enabled)
   Active: active (exited) since Tue 2019-07-23 19:13:20 BST; 1h 16min ago
     Docs: man:systemd-sysv-generator(8)
    Tasks: 0 (limit: 4915)
   CGroup: /system.slice/pihole-FTL.service

Jul 23 19:13:13 raspberrypihole systemd[1]: Starting LSB: pihole-FTL daemon...
Jul 23 19:13:13 raspberrypihole pihole-FTL[411]: Not running
Jul 23 19:13:19 raspberrypihole su[717]: Successful su for pihole by root
Jul 23 19:13:19 raspberrypihole su[717]: + ??? root:pihole
Jul 23 19:13:19 raspberrypihole su[717]: pam_unix(su:session): session opened for user pihole by (uid=0)
Jul 23 19:13:20 raspberrypihole pihole-FTL[411]: dnsmasq: failed to create listening socket for port 53: Address already in use
Jul 23 19:13:20 raspberrypihole systemd[1]: Started LSB: pihole-FTL daemon.

Something is using port 53 and FTLDNS cannot start because of that.

What's the output of sudo lsof -i :53 +c 0 | awk 'FNR==2{ print $1 }' ?

The output is just named. I've no idea what that is. The server I was talking about uses an entirely different port

Here you go:
https://linux.die.net/man/8/named

This was installed as part of some other software (not a part or requirement of Pi-hole).

You can either configure named for a different port or remove it (but this might have implications further down the whatever installed it in the fist place).

Pi-hole required port 53 in order to work and if that port is not available, it will behave like it does in your case.

2 Likes

Thank you so much RamSet!
That totally worked.

1 Like

Any time :wink:

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.