FTL Offline Lost connection to API (clean install)

Help
1

Hi,

I'm running on a new clean vm: Ubuntu server 16.04 LTS and a clean install of pihole.
Server side looks ok?

The web admin states FTL offline, and lost connection to API.

I have tried everything.....but to no evail. Please help with some guidance.

I have run pihole -r and -g many times.
changes resolver to 8.8.8.8

and I can not obtain a token....

Debug Token:

when I try to get my debug token I get 403 Permission Denied (when trying to login wit my guthub account)

2

You will not be able to see the debug log, only the developers can see the log but we need the token generated and displayed for you so that we can find which log belongs to your Pi-hole.

3

Is this the token? 8tcdalww8h!

8tcdalww8h!

8tcdalww8h!
4

Yes.

Your debug log shows a potential conflict between process "named" and pihole-FTL.

*** [ DIAGNOSING ]: Ports in use
[*:53] is in use by pihole-FTL
[127.0.0.1:53] is in use by pihole-FTL
[192.168.1.29:53] is in use by pihole-FTL
127.0.0.1:953 named (IPv4)
[::1]:953 named (IPv6)

What is the output of this command from the Pi-Hole host terminal? This will show all processes running on ports used by Pi-Hole.

sudo netstat -nltup | grep 'Proto\|:53 \|:67 \|:80 \|:471'

And this, which will show the status of pihole-FTL:

sudo service pihole-FTL status

5

sudo netstat -nltup | grep 'Proto|:53 |:67 |:80 |:471'

[sudo] password for rdm:

Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name
tcp        0      0 0.0.0.0:80              0.0.0.0:*               LISTEN      13141/lighttpd  
tcp        0      0 192.168.1.29:53         0.0.0.0:*               LISTEN      1080/named      
tcp        0      0 127.0.0.1:53            0.0.0.0:*               LISTEN      1080/named      
tcp6       0      0 :::80                   :::*                    LISTEN      13141/lighttpd  
tcp6       0      0 :::53                   :::*                    LISTEN      1080/named      
udp        0      0 192.168.1.29:53         0.0.0.0:*                           1080/named      
udp        0      0 127.0.0.1:53            0.0.0.0:*                           1080/named      
udp6       0      0 :::53                   :::*                                1080/named

sudo service pihole-FTL status

● pihole-FTL.service - LSB: pihole-FTL daemon
   Loaded: loaded (/etc/init.d/pihole-FTL; bad; vendor preset: enabled)
   Active: active (exited) since Tue 2019-04-30 21:12:25 AEST; 2h 18min ago
     Docs: man:systemd-sysv-generator(8)
  Process: 13256 ExecStop=/etc/init.d/pihole-FTL stop (code=exited, status=0/SUCCESS)
  Process: 13263 ExecStart=/etc/init.d/pihole-FTL start (code=exited, status=0/SUCCESS)
Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.
6

Process named is on port 53 and will interfere with pihole-FTL.

Run
ps -fp 1080
and see if this returns the actual process running as named. Then, disable that process and relaunch pihole-FTL.

1 Like
7

not sure what I'm doing here: this is the output.

ps -fp 1080
UID        PID  PPID  C STIME TTY          TIME CMD
bind      1080     1  0 Apr30 ?        00:07:54 /usr/sbin/named -f -u bind
8

This output tells you that BIND is running on port 53. This is a DNS server that may have been installed with your base OS installation.

This thread has the removal instructions: Problem after updating "lost connection to api" - #8 by deHakkelaar

9

Thanks…you’re the best. Working!!!

10

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