"FTL offline" and "Lost connection to API"

#1

First:
I installed this rpi2 at my home, it was working fine and doing two jobs:
updating ddns on my “own” server and running pi.hole
I made just one modification, moving logs to a connected USB-Stick.
I tried it at home, with several times rebooting and everything was fine.
Yesterday I installed it to my mums network and now it’s not working anymore. (just the pi.hole)

Everything I’ve found to this error didn’t help! That’s why I’m writing here now.

THNX for helping!
Greets Ralf aka synth

Debug Token:

[Replace this text with the debug token provided from running pihole -d (or running the debug script through the web interface]
Here it is:
=====================================================
This process collects information from your Pi-hole, and optionally uploads it to a unique and random directory on tricorder.pi-hole.net.

The intent of this script is to allow users to self-diagnose their installations. This is accomplished by running tests against our software and providing the user with links to FAQ articles when a problem is detected. Since we are a small team and Pi-hole has been growing steadily, it is our hope that this will help us spend more time on development.

NOTE: All log files auto-delete after 48 hours and ONLY the Pi-hole developers can access your data via the given token. We have taken these extra steps to secure your data and will work to further reduce any personal information gathered.

*** [ INITIALIZING ]
[i] 2018-02-17:12:38:19 debug log has been initiated.

*** [ INITIALIZING ] Sourcing setup variables
[i] Sourcing /etc/pihole/setupVars.conf…

*** [ DIAGNOSING ]: Core version
[i] Core: v3.2.1 (How do I update Pi-hole?)
[i] Branch: master
[i] Commit: v3.2.1-0-ge602008

*** [ DIAGNOSING ]: Web version
[i] Web: v3.2.1 (How do I update Pi-hole?)
[i] Branch: master
[i] Commit: v3.2.1-0-g31dddd8

*** [ DIAGNOSING ]: FTL version
[✓] FTL: v3.0

*** [ DIAGNOSING ]: dnsmasq version
[i] 2.76

*** [ DIAGNOSING ]: lighttpd version
[i] 1.4.45

*** [ DIAGNOSING ]: php version
[i] 7.0.27

*** [ DIAGNOSING ]: Operating system
[✓] Raspbian GNU/Linux 9 (stretch)

*** [ DIAGNOSING ]: SELinux
[i] SELinux not detected

*** [ DIAGNOSING ]: Processor
/opt/pihole/piholeDebug.sh: Zeile 474: $’[\E[32m✓\E[0m] \E[32marmv7l\E[0m’: Kommando nicht gefunden.

*** [ DIAGNOSING ]: Networking
[✓] IPv4 address(es) bound to the eth0 interface:
192.168.131.15/24 matches the IP found in /etc/pihole/setupVars.conf

[✓] IPv6 address(es) bound to the eth0 interface:
fe80::c2b2:f886:cd1c:3b60 does not match the IP found in /etc/pihole/setupVars.conf (Use IPv6 ULA addresses for Pi-hole)

^ Please note that you may have more than one IP address listed.
As long as one of them is green, and it matches what is in /etc/pihole/setupVars.conf, there is no need for concern.

The link to the FAQ is for an issue that sometimes occurs when the IPv6 address changes, which is why we check for it.

[i] Default IPv4 gateway: 192.168.131.1

  • Pinging 192.168.131.1…
    [✓] Gateway responded.

*** [ DIAGNOSING ]: Ports in use
[22] is in use by sshd
[53] is in use by dnsmasq
[80] is in use by lighttpd

*** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
[✓] ad.doubleclick.net.37380.9294.302br.net is 192.168.131.15 via localhost (127.0.0.1)
[✓] ad.doubleclick.net.37380.9294.302br.net is 192.168.131.15 via Pi-hole (192.168.131.15)
[✓] doubleclick.com is 172.217.17.46 via a remote, public DNS server (8.8.8.8)

*** [ DIAGNOSING ]: Pi-hole processes
[✓] dnsmasq daemon is active
[✓] lighttpd daemon is active
[✓] pihole-FTL daemon is active

*** [ DIAGNOSING ]: Setup variables
DNSMASQ_LISTENING=single
DNS_FQDN_REQUIRED=true
DNS_BOGUS_PRIV=true
DNSSEC=false
TEMPERATUREUNIT=C
WEBUIBOXEDLAYOUT=traditional
PIHOLE_INTERFACE=eth0
IPV4_ADDRESS=192.168.131.15/24
IPV6_ADDRESS=
PIHOLE_DNS_1=85.214.20.141
PIHOLE_DNS_2=213.73.91.35
QUERY_LOGGING=true
INSTALL_WEB=true
LIGHTTPD_ENABLED=1

*** [ DIAGNOSING ]: Dashboard and block page
[✓] X-Pi-hole: A black hole for Internet advertisements.
[✓] X-Pi-hole: The Pi-hole Web interface is working!

*** [ DIAGNOSING ]: Gravity list
-rw-r–r-- 1 root root 4438979 Feb 17 12:23 /etc/pihole/gravity.list
-----head of gravity.list------
192.168.131.15 0.0.0.0
192.168.131.15 0000mps.webpreview.dsl.net
192.168.131.15 0001.2waky.com
192.168.131.15 000dom.revenuedirect.com

-----tail of gravity.list------
192.168.131.15 zzsyw.com
192.168.131.15 zztxdown.com
192.168.131.15 zzz.clickbank.net
192.168.131.15 zz.zeroredirect1.com

*** [ DIAGNOSING ]: contents of /etc/pihole

-rw-r–r-- 1 root root 633 Feb 10 16:29 /etc/pihole/adlists.list
https://raw.githubusercontent.com/StevenBlack/hosts/master/hosts
https://mirror1.malwaredomains.com/files/justdomains
http://sysctl.org/cameleon/hosts
https://zeustracker.abuse.ch/blocklist.php?download=domainblocklist
https://s3.amazonaws.com/lists.disconnect.me/simple_tracking.txt
https://s3.amazonaws.com/lists.disconnect.me/simple_ad.txt
https://hosts-file.net/ad_servers.txt

-rw-r–r-- 1 root root 46 Feb 17 12:23 /etc/pihole/local.list
192.168.131.15 pi-hole
192.168.131.15 pi.hole

-rw-r–r-- 1 root root 234 Feb 17 12:23 /etc/pihole/logrotate
/var/log/pihole.log {
su root root
daily
copytruncate
rotate 5
compress
delaycompress
notifempty
nomail
}
/var/log/pihole-FTL.log {
su root root
weekly
copytruncate
rotate 3
compress
delaycompress
notifempty
nomail
}

-rw-r–r-- 1 root root 223 Feb 10 16:34 /etc/pihole/whitelist.txt
raw.githubusercontent.com
mirror1.malwaredomains.com
sysctl.org
zeustracker.abuse.ch
s3.amazonaws.com
hosts-file.net
foto-legler.com
foto-legler.de
kasserver.com
schwiethal.homeserver.com
wired.com
www.googleadservices.com

*** [ DIAGNOSING ]: contents of /etc/dnsmasq.d

-rw-r–r-- 1 root root 1538 Feb 17 12:23 /etc/dnsmasq.d/01-pihole.conf
addn-hosts=/etc/pihole/gravity.list
addn-hosts=/etc/pihole/black.list
addn-hosts=/etc/pihole/local.list
localise-queries
no-resolv
cache-size=10000
log-queries
log-facility=/var/log/pihole.log
local-ttl=2
log-async
server=85.214.20.141
server=213.73.91.35
domain-needed
bogus-priv
interface=eth0

*** [ DIAGNOSING ]: contents of /etc/lighttpd

-rw-r–r-- 1 root root 3027 Feb 17 12:23 /etc/lighttpd/lighttpd.conf
server.modules = (
“mod_access”,
“mod_accesslog”,
“mod_auth”,
“mod_expire”,
“mod_compress”,
“mod_redirect”,
“mod_setenv”,
“mod_rewrite”
)
server.document-root = "/var/www/html"
server.error-handler-404 = "pihole/index.php"
server.upload-dirs = ( “/var/cache/lighttpd/uploads” )
server.errorlog = "/var/log/lighttpd/error.log"
server.pid-file = "/var/run/lighttpd.pid"
server.username = "www-data"
server.groupname = "www-data"
server.port = 80
accesslog.filename = "/var/log/lighttpd/access.log"
accesslog.format = "%{%s}t|%V|%r|%s|%b"
index-file.names = ( “index.php”, “index.html”, “index.lighttpd.html” )
url.access-deny = ( “~”, “.inc”, “.md”, “.yml”, “.ini” )
static-file.exclude-extensions = ( “.php”, “.pl”, “.fcgi” )
compress.cache-dir = "/var/cache/lighttpd/compress/"
compress.filetype = ( “application/javascript”, “text/css”, “text/html”, “text/plain” )
include_shell "/usr/share/lighttpd/use-ipv6.pl " + server.port
include_shell "/usr/share/lighttpd/create-mime.assign.pl"
include_shell “find /etc/lighttpd/conf-enabled -name ‘*.conf’ -a ! -name ‘letsencrypt.conf’ -printf ‘include “%p”
’ 2>/dev/null”
$HTTP[“url”] =~ “^/admin/” {

   setenv.add-response-header = (
       "X-Pi-hole" => "The Pi-hole Web interface is working!",
       "X-Frame-Options" => "DENY"
   )
   $HTTP["url"] =~ ".ttf$" {

       setenv.add-response-header = ( "Access-Control-Allow-Origin" => "*" )
   }

}
$HTTP[“url”] =~ “^/admin/.(.*)” {
url.access-deny = ("")
}
include_shell “cat external.conf 2>/dev/null”

*** [ DIAGNOSING ]: contents of /etc/cron.d

-rw-r–r-- 1 root root 1629 Feb 17 12:23 /etc/cron.d/pihole
4 4 * * 7 root PATH="$PATH:/usr/local/bin/" pihole updateGravity
00 00 * * * root PATH="$PATH:/usr/local/bin/" pihole flush once quiet
@reboot root /usr/sbin/logrotate /etc/pihole/logrotate
*/10 * * * * root PATH="$PATH:/usr/local/bin/" pihole updatechecker local
37 12 * * * root PATH="$PATH:/usr/local/bin/" pihole updatechecker remote
@reboot root PATH="$PATH:/usr/local/bin/" pihole updatechecker remote reboot

*** [ DIAGNOSING ]: contents of /var/log/lighttpd

-rw-r–r-- 1 www-data www-data 4432 Feb 17 12:26 /var/log/lighttpd/error.log
2018-02-10 16:28:12: (log.c.217) server started
2018-02-10 16:29:53: (server.c.1828) server stopped by UID = 0 PID = 1
2018-02-10 16:29:54: (log.c.217) server started
2018-02-10 16:33:09: (mod_fastcgi.c.2543) FastCGI-stderr: PHP Warning: preg_split(): Delimiter must not be alphanumeric or backslash in /var/www/html/admin/scripts/pi-hole/php/auth.php on line 122
2018-02-10 16:33:09: (mod_fastcgi.c.2543) FastCGI-stderr: PHP Warning: Invalid argument supplied for foreach() in /var/www/html/admin/scripts/pi-hole/php/auth.php on line 123
2018-02-10 16:33:14: (mod_fastcgi.c.2543) FastCGI-stderr: PHP Warning: preg_split(): Delimiter must not be alphanumeric or backslash in /var/www/html/admin/scripts/pi-hole/php/auth.php on line 122
2018-02-10 16:33:14: (mod_fastcgi.c.2543) FastCGI-stderr: PHP Warning: Invalid argument supplied for foreach() in /var/www/html/admin/scripts/pi-hole/php/auth.php on line 123
2018-02-10 16:33:28: (mod_fastcgi.c.2543) FastCGI-stderr: PHP Warning: preg_split(): Delimiter must not be alphanumeric or backslash in /var/www/html/admin/scripts/pi-hole/php/auth.php on line 122
2018-02-10 16:33:28: (mod_fastcgi.c.2543) FastCGI-stderr: PHP Warning: Invalid argument supplied for foreach() in /var/www/html/admin/scripts/pi-hole/php/auth.php on line 123
2018-02-10 16:33:40: (mod_fastcgi.c.2543) FastCGI-stderr: PHP Warning: preg_split(): Delimiter must not be alphanumeric or backslash in /var/www/html/admin/scripts/pi-hole/php/auth.php on line 122
2018-02-10 16:33:40: (mod_fastcgi.c.2543) FastCGI-stderr: PHP Warning: Invalid argument supplied for foreach() in /var/www/html/admin/scripts/pi-hole/php/auth.php on line 123
2018-02-10 16:33:50: (mod_fastcgi.c.2543) FastCGI-stderr: PHP Warning: preg_split(): Delimiter must not be alphanumeric or backslash in /var/www/html/admin/scripts/pi-hole/php/auth.php on line 122
2018-02-10 16:33:50: (mod_fastcgi.c.2543) FastCGI-stderr: PHP Warning: Invalid argument supplied for foreach() in /var/www/html/admin/scripts/pi-hole/php/auth.php on line 123
2018-02-10 16:34:08: (mod_fastcgi.c.2543) FastCGI-stderr: PHP Warning: preg_split(): Delimiter must not be alphanumeric or backslash in /var/www/html/admin/scripts/pi-hole/php/auth.php on line 122
2018-02-10 16:34:08: (mod_fastcgi.c.2543) FastCGI-stderr: PHP Warning: Invalid argument supplied for foreach() in /var/www/html/admin/scripts/pi-hole/php/auth.php on line 123
2018-02-10 16:34:22: (mod_fastcgi.c.2543) FastCGI-stderr: PHP Warning: preg_split(): Delimiter must not be alphanumeric or backslash in /var/www/html/admin/scripts/pi-hole/php/auth.php on line 122
2018-02-10 16:34:22: (mod_fastcgi.c.2543) FastCGI-stderr: PHP Warning: Invalid argument supplied for foreach() in /var/www/html/admin/scripts/pi-hole/php/auth.php on line 123
2018-02-10 16:34:28: (mod_fastcgi.c.2543) FastCGI-stderr: PHP Warning: preg_split(): Delimiter must not be alphanumeric or backslash in /var/www/html/admin/scripts/pi-hole/php/auth.php on line 122
2018-02-10 16:34:28: (mod_fastcgi.c.2543) FastCGI-stderr: PHP Warning: Invalid argument supplied for foreach() in /var/www/html/admin/scripts/pi-hole/php/auth.php on line 123
2018-02-10 16:34:33: (mod_fastcgi.c.2543) FastCGI-stderr: PHP Warning: preg_split(): Delimiter must not be alphanumeric or backslash in /var/www/html/admin/scripts/pi-hole/php/auth.php on line 122
2018-02-10 16:34:33: (mod_fastcgi.c.2543) FastCGI-stderr: PHP Warning: Invalid argument supplied for foreach() in /var/www/html/admin/scripts/pi-hole/php/auth.php on line 123
2018-02-10 18:00:41: (server.c.1828) server stopped by UID = 0 PID = 1
2018-02-10 18:00:58: (log.c.217) server started
2018-02-11 14:06:41: (server.c.1828) server stopped by UID = 0 PID = 1
2018-02-11 14:06:57: (log.c.217) server started

*** [ DIAGNOSING ]: contents of /var/log

lrwxrwxrwx 1 root root 42 Feb 11 14:22 /var/log/pihole-FTL.log -> /media/4GB-PI-HOLE/logfiles/pihole-FTL.log

*** [ DIAGNOSING ]: Pi-hole log
lrwxrwxrwx 1 root root 38 Feb 11 14:15 /var/log/pihole.log -> /media/4GB-PI-HOLE/logfiles/pihole.log
-----head of pihole.log------
Feb 17 00:00:18 dnsmasq[494]: query[A] ip1.dynupdate.no-ip.com from 192.168.131.1
Feb 17 00:00:18 dnsmasq[494]: cached ip1.dynupdate.no-ip.com is
Feb 17 00:00:18 dnsmasq[494]: cached xip.aws.noip.net is 34.196.162.199
Feb 17 00:00:18 dnsmasq[494]: cached xip.aws.noip.net is 52.203.111.135
Feb 17 00:00:18 dnsmasq[494]: query[A] xip.aws.noip.net from 192.168.131.1
Feb 17 00:00:18 dnsmasq[494]: cached xip.aws.noip.net is 52.203.111.135
Feb 17 00:00:18 dnsmasq[494]: cached xip.aws.noip.net is 34.196.162.199
Feb 17 00:00:18 dnsmasq[494]: query[A] ip1.dynupdate.no-ip.com from 192.168.131.1
Feb 17 00:00:18 dnsmasq[494]: cached ip1.dynupdate.no-ip.com is
Feb 17 00:00:18 dnsmasq[494]: cached xip.aws.noip.net is 34.196.162.199
Feb 17 00:00:18 dnsmasq[494]: cached xip.aws.noip.net is 52.203.111.135
Feb 17 00:00:18 dnsmasq[494]: query[A] xip.aws.noip.net from 192.168.131.1
Feb 17 00:00:18 dnsmasq[494]: cached xip.aws.noip.net is 52.203.111.135
Feb 17 00:00:18 dnsmasq[494]: cached xip.aws.noip.net is 34.196.162.199
Feb 17 00:00:18 dnsmasq[494]: query[A] netgear.api.oemdns.com from 192.168.131.1
Feb 17 00:00:18 dnsmasq[494]: forwarded netgear.api.oemdns.com to 213.73.91.35
Feb 17 00:00:18 dnsmasq[494]: forwarded netgear.api.oemdns.com to 85.214.20.141
Feb 17 00:00:18 dnsmasq[494]: reply netgear.api.oemdns.com is 8.23.224.110
Feb 17 00:00:49 dnsmasq[494]: query[A] ip1.dynupdate.no-ip.com from 192.168.131.1
Feb 17 00:00:49 dnsmasq[494]: cached ip1.dynupdate.no-ip.com is



[✓] ** 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] n
* Log will NOT be uploaded to tricorder.

0 Likes

#2

Your versions are mismatched (using 3.2.1 with FTL 3.0). Run pihole -up to update.

0 Likes

#3

Hey, thank you, but still the same Problem. :frowning:

0 Likes

#4

Make a new debug token

0 Likes

#5

All right, here it is, but it’s not updating FTL:

This process collects information from your Pi-hole, and optionally uploads it to a unique and random directory on tricorder.pi-hole.net.

The intent of this script is to allow users to self-diagnose their installations. This is accomplished by running tests against our software and providing the user with links to FAQ articles when a problem is detected. Since we are a small team and Pi-hole has been growing steadily, it is our hope that this will help us spend more time on development.

NOTE: All log files auto-delete after 48 hours and ONLY the Pi-hole developers can access your data via the given token. We have taken these extra steps to secure your data and will work to further reduce any personal information gathered.

*** [ INITIALIZING ]
[i] 2018-02-17:16:58:02 debug log has been initialized.

*** [ INITIALIZING ] Sourcing setup variables
[i] Sourcing /etc/pihole/setupVars.conf…

*** [ DIAGNOSING ]: Core version
[i] Core: v3.3 (How do I update Pi-hole?)
[i] Branch: master
[i] Commit: v3.3-0-g1e87850

*** [ DIAGNOSING ]: Web version
[i] Web: v3.3 (How do I update Pi-hole?)
[i] Branch: master
[i] Commit: v3.3-0-ge48aa295

*** [ DIAGNOSING ]: FTL version
[✓] FTL: v3.0

*** [ DIAGNOSING ]: dnsmasq version
[i] 2.76

*** [ DIAGNOSING ]: lighttpd version
[i] 1.4.45

*** [ DIAGNOSING ]: php version
[i] 7.0.27

*** [ DIAGNOSING ]: Operating system
[✓] Raspbian GNU/Linux 9 (stretch)

*** [ DIAGNOSING ]: SELinux
[i] SELinux not detected

*** [ DIAGNOSING ]: Processor

*** [ DIAGNOSING ]: Networking
[✓] IPv4 address(es) bound to the eth0 interface:
192.168.131.15/24 matches the IP found in /etc/pihole/setupVars.conf

[✓] IPv6 address(es) bound to the eth0 interface:
fe80::c2b2:f886:cd1c:3b60 does not match the IP found in /etc/pihole/setupVars.conf (Use IPv6 ULA addresses for Pi-hole)

^ Please note that you may have more than one IP address listed.
As long as one of them is green, and it matches what is in /etc/pihole/setupVars.conf, there is no need for concern.

The link to the FAQ is for an issue that sometimes occurs when the IPv6 address changes, which is why we check for it.

[i] Default IPv4 gateway: 192.168.131.1

  • Pinging 192.168.131.1…
    [✓] Gateway responded.

*** [ DIAGNOSING ]: Ports in use
[22] is in use by sshd
[53] is in use by dnsmasq
[80] is in use by lighttpd

*** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
[✓] mbn.com.ua is 192.168.131.15 via localhost (127.0.0.1)
[✓] mbn.com.ua is 192.168.131.15 via Pi-hole (192.168.131.15)
[✓] doubleclick.com is 172.217.17.46 via a remote, public DNS server (8.8.8.8)

*** [ DIAGNOSING ]: Pi-hole processes
[✓] dnsmasq daemon is active
[✓] lighttpd daemon is active
[✓] pihole-FTL daemon is active

*** [ DIAGNOSING ]: Setup variables
DNSMASQ_LISTENING=single
DNS_FQDN_REQUIRED=true
DNS_BOGUS_PRIV=true
DNSSEC=false
TEMPERATUREUNIT=C
WEBUIBOXEDLAYOUT=traditional
PIHOLE_INTERFACE=eth0
IPV4_ADDRESS=192.168.131.15/24
IPV6_ADDRESS=
PIHOLE_DNS_1=85.214.20.141
PIHOLE_DNS_2=213.73.91.35
QUERY_LOGGING=true
INSTALL_WEB=true
LIGHTTPD_ENABLED=1

*** [ DIAGNOSING ]: Dashboard and block page
[✓] X-Pi-hole: A black hole for Internet advertisements.
[✓] X-Pi-hole: The Pi-hole Web interface is working!

*** [ DIAGNOSING ]: Gravity list
-rw-r–r-- 1 root root 4438979 Feb 17 12:45 /etc/pihole/gravity.list
-----head of gravity.list------
192.168.131.15 0.0.0.0
192.168.131.15 0000mps.webpreview.dsl.net
192.168.131.15 0001.2waky.com
192.168.131.15 000dom.revenuedirect.com

-----tail of gravity.list------
192.168.131.15 zzsyw.com
192.168.131.15 zztxdown.com
192.168.131.15 zzz.clickbank.net
192.168.131.15 zz.zeroredirect1.com

*** [ DIAGNOSING ]: contents of /etc/pihole

-rw-r–r-- 1 root root 633 Feb 10 16:29 /etc/pihole/adlists.list
https://raw.githubusercontent.com/StevenBlack/hosts/master/hosts
https://mirror1.malwaredomains.com/files/justdomains
http://sysctl.org/cameleon/hosts
https://zeustracker.abuse.ch/blocklist.php?download=domainblocklist
https://s3.amazonaws.com/lists.disconnect.me/simple_tracking.txt
https://s3.amazonaws.com/lists.disconnect.me/simple_ad.txt
https://hosts-file.net/ad_servers.txt

-rw-r–r-- 1 root root 46 Feb 17 12:45 /etc/pihole/local.list
192.168.131.15 pi-hole
192.168.131.15 pi.hole

-rw-r–r-- 1 root root 234 Feb 17 12:45 /etc/pihole/logrotate
/var/log/pihole.log {
su root root
daily
copytruncate
rotate 5
compress
delaycompress
notifempty
nomail
}
/var/log/pihole-FTL.log {
su root root
weekly
copytruncate
rotate 3
compress
delaycompress
notifempty
nomail
}

-rw-r–r-- 1 root root 223 Feb 10 16:34 /etc/pihole/whitelist.txt
raw.githubusercontent.com
mirror1.malwaredomains.com
sysctl.org
zeustracker.abuse.ch
s3.amazonaws.com
hosts-file.net
foto-legler.com
foto-legler.de
kasserver.com
schwiethal.homeserver.com
wired.com
www.googleadservices.com

*** [ DIAGNOSING ]: contents of /etc/dnsmasq.d

-rw-r–r-- 1 root root 1544 Feb 17 12:45 /etc/dnsmasq.d/01-pihole.conf
addn-hosts=/etc/pihole/gravity.list
addn-hosts=/etc/pihole/black.list
addn-hosts=/etc/pihole/local.list
localise-queries
no-resolv
cache-size=10000
log-queries=extra
log-facility=/var/log/pihole.log
local-ttl=2
log-async
server=85.214.20.141
server=213.73.91.35
domain-needed
bogus-priv
interface=eth0

*** [ DIAGNOSING ]: contents of /etc/lighttpd

-rw-r–r-- 1 root root 3027 Feb 17 12:45 /etc/lighttpd/lighttpd.conf
server.modules = (
“mod_access”,
“mod_accesslog”,
“mod_auth”,
“mod_expire”,
“mod_compress”,
“mod_redirect”,
“mod_setenv”,
“mod_rewrite”
)
server.document-root = "/var/www/html"
server.error-handler-404 = "pihole/index.php"
server.upload-dirs = ( “/var/cache/lighttpd/uploads” )
server.errorlog = "/var/log/lighttpd/error.log"
server.pid-file = "/var/run/lighttpd.pid"
server.username = "www-data"
server.groupname = "www-data"
server.port = 80
accesslog.filename = "/var/log/lighttpd/access.log"
accesslog.format = "%{%s}t|%V|%r|%s|%b"
index-file.names = ( “index.php”, “index.html”, “index.lighttpd.html” )
url.access-deny = ( “~”, “.inc”, “.md”, “.yml”, “.ini” )
static-file.exclude-extensions = ( “.php”, “.pl”, “.fcgi” )
compress.cache-dir = "/var/cache/lighttpd/compress/"
compress.filetype = ( “application/javascript”, “text/css”, “text/html”, “text/plain” )
include_shell "/usr/share/lighttpd/use-ipv6.pl " + server.port
include_shell "/usr/share/lighttpd/create-mime.assign.pl"
include_shell “find /etc/lighttpd/conf-enabled -name ‘*.conf’ -a ! -name ‘letsencrypt.conf’ -printf ‘include “%p”
’ 2>/dev/null”
$HTTP[“url”] =~ “^/admin/” {

   setenv.add-response-header = (
       "X-Pi-hole" => "The Pi-hole Web interface is working!",
       "X-Frame-Options" => "DENY"
   )
   $HTTP["url"] =~ ".ttf$" {
       
       setenv.add-response-header = ( "Access-Control-Allow-Origin" => "*" )
   }

}
$HTTP[“url”] =~ “^/admin/.(.*)” {
url.access-deny = ("")
}
include_shell “cat external.conf 2>/dev/null”

*** [ DIAGNOSING ]: contents of /etc/cron.d

-rw-r–r-- 1 root root 1496 Feb 17 12:45 /etc/cron.d/pihole
56 3 * * 7 root PATH="$PATH:/usr/local/bin/" pihole updateGravity
00 00 * * * root PATH="$PATH:/usr/local/bin/" pihole flush once quiet
@reboot root /usr/sbin/logrotate /etc/pihole/logrotate
*/10 * * * * root PATH="$PATH:/usr/local/bin/" pihole updatechecker local
38 18 * * * root PATH="$PATH:/usr/local/bin/" pihole updatechecker remote
@reboot root PATH="$PATH:/usr/local/bin/" pihole updatechecker remote reboot

*** [ DIAGNOSING ]: contents of /var/log/lighttpd

-rw-r–r-- 1 www-data www-data 4674 Feb 17 12:49 /var/log/lighttpd/error.log
2018-02-10 16:28:12: (log.c.217) server started
2018-02-10 16:29:53: (server.c.1828) server stopped by UID = 0 PID = 1
2018-02-10 16:29:54: (log.c.217) server started
2018-02-10 16:33:09: (mod_fastcgi.c.2543) FastCGI-stderr: PHP Warning: preg_split(): Delimiter must not be alphanumeric or backslash in /var/www/html/admin/scripts/pi-hole/php/auth.php on line 122
2018-02-10 16:33:09: (mod_fastcgi.c.2543) FastCGI-stderr: PHP Warning: Invalid argument supplied for foreach() in /var/www/html/admin/scripts/pi-hole/php/auth.php on line 123
2018-02-10 16:33:14: (mod_fastcgi.c.2543) FastCGI-stderr: PHP Warning: preg_split(): Delimiter must not be alphanumeric or backslash in /var/www/html/admin/scripts/pi-hole/php/auth.php on line 122
2018-02-10 16:33:14: (mod_fastcgi.c.2543) FastCGI-stderr: PHP Warning: Invalid argument supplied for foreach() in /var/www/html/admin/scripts/pi-hole/php/auth.php on line 123
2018-02-10 16:33:28: (mod_fastcgi.c.2543) FastCGI-stderr: PHP Warning: preg_split(): Delimiter must not be alphanumeric or backslash in /var/www/html/admin/scripts/pi-hole/php/auth.php on line 122
2018-02-10 16:33:28: (mod_fastcgi.c.2543) FastCGI-stderr: PHP Warning: Invalid argument supplied for foreach() in /var/www/html/admin/scripts/pi-hole/php/auth.php on line 123
2018-02-10 16:33:40: (mod_fastcgi.c.2543) FastCGI-stderr: PHP Warning: preg_split(): Delimiter must not be alphanumeric or backslash in /var/www/html/admin/scripts/pi-hole/php/auth.php on line 122
2018-02-10 16:33:40: (mod_fastcgi.c.2543) FastCGI-stderr: PHP Warning: Invalid argument supplied for foreach() in /var/www/html/admin/scripts/pi-hole/php/auth.php on line 123
2018-02-10 16:33:50: (mod_fastcgi.c.2543) FastCGI-stderr: PHP Warning: preg_split(): Delimiter must not be alphanumeric or backslash in /var/www/html/admin/scripts/pi-hole/php/auth.php on line 122
2018-02-10 16:33:50: (mod_fastcgi.c.2543) FastCGI-stderr: PHP Warning: Invalid argument supplied for foreach() in /var/www/html/admin/scripts/pi-hole/php/auth.php on line 123
2018-02-10 16:34:08: (mod_fastcgi.c.2543) FastCGI-stderr: PHP Warning: preg_split(): Delimiter must not be alphanumeric or backslash in /var/www/html/admin/scripts/pi-hole/php/auth.php on line 122
2018-02-10 16:34:08: (mod_fastcgi.c.2543) FastCGI-stderr: PHP Warning: Invalid argument supplied for foreach() in /var/www/html/admin/scripts/pi-hole/php/auth.php on line 123
2018-02-10 16:34:22: (mod_fastcgi.c.2543) FastCGI-stderr: PHP Warning: preg_split(): Delimiter must not be alphanumeric or backslash in /var/www/html/admin/scripts/pi-hole/php/auth.php on line 122
2018-02-10 16:34:22: (mod_fastcgi.c.2543) FastCGI-stderr: PHP Warning: Invalid argument supplied for foreach() in /var/www/html/admin/scripts/pi-hole/php/auth.php on line 123
2018-02-10 16:34:28: (mod_fastcgi.c.2543) FastCGI-stderr: PHP Warning: preg_split(): Delimiter must not be alphanumeric or backslash in /var/www/html/admin/scripts/pi-hole/php/auth.php on line 122
2018-02-10 16:34:28: (mod_fastcgi.c.2543) FastCGI-stderr: PHP Warning: Invalid argument supplied for foreach() in /var/www/html/admin/scripts/pi-hole/php/auth.php on line 123
2018-02-10 16:34:33: (mod_fastcgi.c.2543) FastCGI-stderr: PHP Warning: preg_split(): Delimiter must not be alphanumeric or backslash in /var/www/html/admin/scripts/pi-hole/php/auth.php on line 122
2018-02-10 16:34:33: (mod_fastcgi.c.2543) FastCGI-stderr: PHP Warning: Invalid argument supplied for foreach() in /var/www/html/admin/scripts/pi-hole/php/auth.php on line 123
2018-02-10 18:00:41: (server.c.1828) server stopped by UID = 0 PID = 1
2018-02-10 18:00:58: (log.c.217) server started
2018-02-11 14:06:41: (server.c.1828) server stopped by UID = 0 PID = 1
2018-02-11 14:06:57: (log.c.217) server started

*** [ DIAGNOSING ]: contents of /var/log

lrwxrwxrwx 1 root root 42 Feb 11 14:22 /var/log/pihole-FTL.log -> /media/4GB-PI-HOLE/logfiles/pihole-FTL.log

*** [ DIAGNOSING ]: Pi-hole log
lrwxrwxrwx 1 root root 38 Feb 11 14:15 /var/log/pihole.log -> /media/4GB-PI-HOLE/logfiles/pihole.log
-----head of pihole.log------
Feb 17 12:41:56 dnsmasq[478]: query[A] ip1.dynupdate.no-ip.com from 192.168.131.1
Feb 17 12:41:56 dnsmasq[478]: cached ip1.dynupdate.no-ip.com is
Feb 17 12:41:56 dnsmasq[478]: forwarded ip1.dynupdate.no-ip.com to 213.73.91.35
Feb 17 12:41:56 dnsmasq[478]: forwarded ip1.dynupdate.no-ip.com to 85.214.20.141
Feb 17 12:41:56 dnsmasq[478]: reply ip1.dynupdate.no-ip.com is
Feb 17 12:41:56 dnsmasq[478]: reply xip.aws.noip.net is 34.196.162.199
Feb 17 12:41:56 dnsmasq[478]: reply xip.aws.noip.net is 52.203.111.135
Feb 17 12:41:56 dnsmasq[478]: query[A] xip.aws.noip.net from 192.168.131.1
Feb 17 12:41:56 dnsmasq[478]: cached xip.aws.noip.net is 52.203.111.135
Feb 17 12:41:56 dnsmasq[478]: cached xip.aws.noip.net is 34.196.162.199
Feb 17 12:41:56 dnsmasq[478]: query[A] ip1.dynupdate.no-ip.com from 192.168.131.1
Feb 17 12:41:56 dnsmasq[478]: cached ip1.dynupdate.no-ip.com is
Feb 17 12:41:56 dnsmasq[478]: cached xip.aws.noip.net is 34.196.162.199
Feb 17 12:41:56 dnsmasq[478]: cached xip.aws.noip.net is 52.203.111.135
Feb 17 12:41:56 dnsmasq[478]: query[A] xip.aws.noip.net from 192.168.131.1
Feb 17 12:41:56 dnsmasq[478]: cached xip.aws.noip.net is 52.203.111.135
Feb 17 12:41:56 dnsmasq[478]: cached xip.aws.noip.net is 34.196.162.199
Feb 17 12:41:56 dnsmasq[478]: query[A] netgear.api.oemdns.com from 192.168.131.1
Feb 17 12:41:56 dnsmasq[478]: cached netgear.api.oemdns.com is 8.23.224.110
Feb 17 12:42:27 dnsmasq[478]: query[A] ip1.dynupdate.no-ip.com from 192.168.131.1



[✓] ** 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.

[i] Debug script running in automated mode
* Using openssl for transmission.



[✓] Your debug token is: x16c49nysc



  • 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-sanitized.log
0 Likes

#6

It’s easier when you just post the token, not the whole log, so people don’t have to scroll a ton ;).

Run sudo service pihole-FTL restart

0 Likes

#7

All right …
but … sadly … it keeps the same, FTL still offline. :frowning:



[✓] Your debug token is: bypxxfgyto



0 Likes

#8

Your log shows FTL as active… can you run through the debug steps listed here:

0 Likes

#9

When I started and it’s written that I should kill the process I got the feedback, that there’s no process like this running …
all right, ok the debugging ends with:

[New Thread 0x76d21470 (LWP 12613)]
[2018-02-17 22:50:07.370] Listening on port 4711 for incoming IPv4 telnet connections
[2018-02-17 22:50:07.371] Found 4 IPv4 and 2 IPv6 capable interfaces
[2018-02-17 22:50:07.371] Listening on port 4711 for incoming IPv6 telnet connections
[2018-02-17 22:50:07.372] Error on binding on Unix socket /var/run/pihole/FTL.sock: No such file or directory (2)
[Thread 0x76d21470 (LWP 12613) exited]
[Inferior 1 (process 12605) exited with code 01]

0 Likes

#10

What is the output of these commands?

ls -al /var/run/
ls -al /var/run/pihole/
0 Likes

#11

ls -al /var/run:
pi@pi-hole:~ $ ls -al /var/run/
insgesamt 40
drwxr-xr-x 25 root root 820 Feb 18 13:40 .
drwxr-xr-x 21 root root 4096 Feb 10 16:11 …
-rw------- 1 root root 0 Feb 17 12:49 agetty.reload
drwxr-xr-x 2 avahi avahi 80 Feb 17 12:49 avahi-daemon
drwxr-xr-x 2 root root 60 Feb 17 12:49 blkid
drwxr-xr-x 2 root root 80 Feb 17 12:49 console-setup
-rw-r–r-- 1 root root 4 Feb 17 12:49 crond.pid
---------- 1 root root 0 Feb 17 12:49 crond.reboot
drwxr-xr-x 2 root root 60 Feb 17 12:49 dbus
drwxr-xr-x 3 root root 60 Feb 17 12:49 dhcpcd
-rw-r–r-- 1 root root 4 Feb 17 12:49 dhcpcd.pid
srw-rw---- 1 root root 0 Feb 17 12:49 dhcpcd.sock
srw-rw-rw- 1 root root 0 Feb 17 12:49 dhcpcd.unpriv.sock
drwxr-xr-x 2 root root 80 Feb 17 12:49 dnsmasq
lrwxrwxrwx 1 root root 25 Feb 17 12:49 initctl -> /run/systemd/initct l/fifo
drwxr-x— 2 www-data www-data 60 Feb 17 12:49 lighttpd
-rw-r–r-- 1 root root 4 Feb 17 12:49 lighttpd.pid
drwxrwxrwt 3 root root 80 Feb 17 12:49 lock
drwxr-xr-x 3 root root 60 Nov 3 2016 log
-rw-r–r-- 1 root root 71 Feb 18 13:40 motd.dynamic
drwxr-xr-x 2 root root 60 Nov 3 2016 mount
drwxr-xr-x 2 root root 100 Feb 17 12:49 network
-rw-r–r-- 1 pi pi 5 Feb 17 22:54 pihole-FTL.pid
-rw-r–r-- 1 pi pi 4 Feb 17 22:54 pihole-FTL.port
drwxr-xr-x 2 root root 40 Feb 17 12:49 plymouth
drwxr-xr-x 4 root root 80 Feb 17 12:49 resolvconf
drwxr-xr-x 2 root root 40 Feb 17 12:49 rpcbind
dr-xr-xr-x 11 root root 0 Nov 3 2016 rpc_pipefs
-rw-r–r-- 1 root root 3 Feb 17 12:49 rsyslogd.pid
drwxrwxr-x 3 root utmp 60 Feb 17 22:46 screen
drwxr-xr-x 2 root root 40 Feb 17 12:49 sendsigs.omit.d
lrwxrwxrwx 1 root root 8 Feb 17 12:49 shm -> /dev/shm
drwxr-xr-x 2 root root 40 Feb 17 12:49 sshd
-rw-r–r-- 1 root root 4 Feb 17 12:49 sshd.pid
drwxr-xr-x 2 root root 60 Feb 17 12:49 sysconfig
drwxr-xr-x 17 root root 420 Feb 17 22:46 systemd
srw-rw-rw- 1 root root 0 Feb 17 12:49 thd.socket
drwxr-xr-x 2 root root 60 Nov 3 2016 tmpfiles.d
drwxr-xr-x 7 root root 160 Feb 17 12:49 udev
drwxr-xr-x 3 root root 60 Feb 18 06:25 user
-rw-rw-r-- 1 root utmp 3840 Feb 18 13:40 utmp

ls -al /var/run/pihole/ <-- not found

0 Likes

#12

Check this issue:

You can try running these steps (from the issue):

sudo rm /usr/bin/pihole-FTL
sudo pihole -r
0 Likes

#13

Sadly … nothing helps :frowning:
i’m nearby setting up a new SD-Card and switching it.

Just tried to repair and reconfigure with pihole -r … got this nice meage:
[✗] Downloading and Installing FTL
Error: Unable to get latest release location from GitHub
[✗] FTL Engine not installed

0 Likes

#14

What is the output of sudo service dnsmasq status

Try sudo service dnsmasq restart and then pihole -r

0 Likes

#15

It seems I am having the exact same issue as @synth here. My pihole is updated automatically via cron every Monday morning. This morning, some things were not working as expected. I logged in to pihole to see FTL not running. Tried to manually upgrade using -up. Did a dist-upgrade just to be sure. Tried the things described in this thread. FTL remains stopped.
My debug token is 7q3x89kv4v.

0 Likes

#16

@Mcat12

sudo service dsmasq status
● dnsmasq.service - dnsmasq - A lightweight DHCP and caching DNS server
Loaded: loaded (/lib/systemd/system/dnsmasq.service; enabled; vendor preset: enabled)
Active: active (running) since Sun 2018-02-18 20:07:55 CET; 16h ago
Process: 491 ExecStartPost=/etc/init.d/dnsmasq systemd-start-resolvconf (code=exited, status=0/SUCCESS)
Process: 467 ExecStart=/etc/init.d/dnsmasq systemd-exec (code=exited, status=0/SUCCESS)
Process: 450 ExecStartPre=/usr/sbin/dnsmasq --test (code=exited, status=0/SUCCESS)
Main PID: 489 (dnsmasq)
CGroup: /system.slice/dnsmasq.service
└─489 /usr/sbin/dnsmasq -x /run/dnsmasq/dnsmasq.pid -u dnsmasq -r /run/dnsmasq/resolv.conf -7 /etc/dnsmasq.d,.dpkg-dist,.dpkg-old,.dpkg-new --loca

Feb 18 20:07:54 pi-hole systemd[1]: Starting dnsmasq - A lightweight DHCP and caching DNS server…
Feb 18 20:07:54 pi-hole dnsmasq[450]: dnsmasq: Syntaxprüfung OK.
Feb 18 20:07:55 pi-hole systemd[1]: Started dnsmasq - A lightweight DHCP and caching DNS server.
lines 1-13/13 (END)

sudo service dnsmasq restart and pihole -r
looks everything fine … just
[✗] Backing up index.lighttpd.html
No default index.lighttpd.html file found… not backing up

and still no FTL offline and no API-Connection

0 Likes

#17

I am also having this issue this morning. I get no local name resolution on the server either until I went into /etc/resolv.conf and set the dns to 127.0.0.1. For some reason it was set to my gateway IP address? I ran a pihole -up and it messed up the resolv.conf again and broke the API like above. I restored from backup and got them working and won’t touch them until i see some options here.

0 Likes

#18

Make a new debug token.

0 Likes

#19

It looks like the core repo didn’t update. What is the output of pihole -up?

0 Likes

#20

@Mcat12 Thanks a lot for taking a look at the debug. I manually ran -up again and indeed, that looks like what causes the problem for my install:
pihole -up
[i] Checking for updates…
error: inflate: data stream error (invalid code lengths set)
error: failed to read object ffd31d83307a9ab521d83b32dcf4538d8bed7a03 at offset 554870 from .git/objects/pack/pack-96630346bfb09d14f90add8d6c31f37168c1ffd0.pack
fatal: packed object ffd31d83307a9ab521d83b32dcf4538d8bed7a03 (stored in .git/objects/pack/pack-96630346bfb09d14f90add8d6c31f37168c1ffd0.pack) is corrupt
fatal: The remote end hung up unexpectedly
[i] Pi-hole Core: up to date
[i] FTL: up to date
[i] Web Interface: up to date

  [✓] Everything is up to date!

Makes me wonder what I did to break things :open_mouth:
Also, I would very much appreciate any and all pointers on how to fix this.

0 Likes