FTL offine & Lost connection to API

always the same problem : FTL offine
Thanks for help

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] 2019-01-18:16:30:13 debug log has been initialized.

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

*** [ DIAGNOSING ]: Core version
[i] Core: v4.1.1 (https://discourse.pi-hole.net/t/how-do-i-update-pi-hole/249)
[i] Branch: master
[i] Commit: v4.1.1-0-g8d85d46

*** [ DIAGNOSING ]: Web version
[i] Web: v4.1.1 (https://discourse.pi-hole.net/t/how-do-i-update-pi-hole/249)
[i] Branch: master
[i] Commit: v4.1.1-0-gde7aa5a

*** [ DIAGNOSING ]: FTL version
[✓] FTL: v4.1.2

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

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

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

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

*** [ DIAGNOSING ]: Processor
[✓] armv7l

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

[✓] IPv6 address(es) bound to the eth0 interface:
   fe80::d263:b4ff:fe00:d846 does not match the IP found in /etc/pihole/setupVars.conf (https://discourse.pi-hole.net/t/use-ipv6-ula-addresses-for-pi-hole/2127)

   ^ 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.31.1
   * Pinging 192.168.31.1...
[✓] Gateway responded.

*** [ DIAGNOSING ]: Ports in use
[127.0.0.1:53] is in use by pihole-FTL
[[::1]:53] is in use by pihole-FTL
*:22 sshd (IPv4)
*:22 sshd (IPv6)
[*:80] is in use by lighttpd
[*:80] is in use by lighttpd

*** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
[✓] 612100.cn is  via localhost (127.0.0.1)
[✗] Failed to resolve 612100.cn via Pi-hole (192.168.31.40)
[✓] doubleclick.com is 216.58.208.238 via a remote, public DNS server (8.8.8.8)

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

*** [ DIAGNOSING ]: Setup variables
    BLOCKING_ENABLED=true
    PIHOLE_INTERFACE=eth0
    IPV4_ADDRESS=192.168.31.40/24
    IPV6_ADDRESS=
    PIHOLE_DNS_1=9.9.9.9
    PIHOLE_DNS_2=149.112.112.112
    QUERY_LOGGING=true
    INSTALL_WEB_SERVER=true
    INSTALL_WEB_INTERFACE=true
    LIGHTTPD_ENABLED=true

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

*** [ DIAGNOSING ]: Gravity list
-rw-r--r-- 1 root root 2635634 Jan 18 08:48 /etc/pihole/gravity.list
   -----head of gravity.list------
   0.0.0.0
   0.r.msn.com
   0.start.bz
   000.0x1f4b0.com

   -----tail of gravity.list------
   zzz.clickbank.net
   zzzezeroe.fr
   zzzpooeaz-france.com
   zzzrtrcm2.com

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

-rw-r--r-- 1 root root 381 Jan 18 08:16 /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 44 Jan 18 08:48 /etc/pihole/local.list
   192.168.31.40 Pi-Hole
   192.168.31.40 pi.hole

-rw-r--r-- 1 root root 234 Jan 18 08:48 /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
   }

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

-rw-r--r-- 1 root root 1421 Jan 18 08:48 /etc/dnsmasq.d/01-pihole.conf
   addn-hosts=/etc/pihole/gravity.list
   addn-hosts=/etc/pihole/black.list
   addn-hosts=/etc/pihole/local.list
   user=pihole
   group=pihole
   localise-queries
   no-resolv
   cache-size=10000
   log-queries
   log-facility=/var/log/pihole.log
   local-ttl=2
   log-async
   server=9.9.9.9
   server=149.112.112.112
   interface=eth0

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

-rw-r--r-- 1 root root 3102 Jan 18 08:48 /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 1704 Jan 18 08:48 /etc/cron.d/pihole
   52 3   * * 7   root    PATH="$PATH:/usr/local/bin/" pihole updateGravity >/var/log/pihole_updateGravity.log || cat /var/log/pihole_updateGravity.log
   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
   27 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 1017 Jan 18 08:53 /var/log/lighttpd/error.log
   2019-01-18 07:31:25: (log.c.217) server started 
   2019-01-18 07:32:49: (server.c.1828) server stopped by UID = 0 PID = 1 
   2019-01-18 07:32:49: (log.c.217) server started 
   2019-01-18 07:47:50: (server.c.1828) server stopped by UID = 0 PID = 1 
   2019-01-18 07:47:51: (log.c.217) server started 
   2019-01-18 07:48:48: (server.c.1828) server stopped by UID = 0 PID = 1 
   2019-01-18 07:48:59: (log.c.217) server started 
   2019-01-18 08:00:39: (server.c.1828) server stopped by UID = 0 PID = 1 
   2019-01-18 08:00:41: (log.c.217) server started 
   2019-01-18 08:17:31: (server.c.1828) server stopped by UID = 0 PID = 1 
   2019-01-18 08:17:32: (log.c.217) server started 
   2019-01-18 08:48:06: (server.c.1828) server stopped by UID = 0 PID = 1 
   2019-01-18 08:48:06: (log.c.217) server started 
   2019-01-18 08:49:37: (server.c.1828) server stopped by UID = 0 PID = 1 
   2019-01-18 08:49:51: (log.c.217) server started 
   2019-01-18 08:53:13: (server.c.1828) server stopped by UID = 0 PID = 1 
   2019-01-18 08:53:24: (log.c.217) server started 

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

-rw-r--r-- 1 pihole pihole 35118 Jan 18 08:53 /var/log/pihole-FTL.log
   -----head of pihole-FTL.log------
   [2019-01-18 07:32:55.209] Using log file /var/log/pihole-FTL.log
   [2019-01-18 07:32:55.210] ########## FTL started! ##########
   [2019-01-18 07:32:55.210] FTL branch: master
   [2019-01-18 07:32:55.210] FTL version: v4.1.2
   [2019-01-18 07:32:55.211] FTL commit: b06eedf
   [2019-01-18 07:32:55.211] FTL date: 2018-12-21 14:43:34 -0600
   [2019-01-18 07:32:55.211] FTL user: pihole
   [2019-01-18 07:32:55.211] Starting config file parsing (/etc/pihole/pihole-FTL.conf)
   [2019-01-18 07:32:55.211]    SOCKET_LISTENING: only local
   [2019-01-18 07:32:55.211]    AAAA_QUERY_ANALYSIS: Show AAAA queries
   [2019-01-18 07:32:55.212]    MAXDBDAYS: max age for stored queries is 365 days
   [2019-01-18 07:32:55.212]    RESOLVE_IPV6: Resolve IPv6 addresses
   [2019-01-18 07:32:55.213]    RESOLVE_IPV4: Resolve IPv4 addresses
   [2019-01-18 07:32:55.213]    DBINTERVAL: saving to DB file every minute
   [2019-01-18 07:32:55.213]    DBFILE: Using /etc/pihole/pihole-FTL.db
   [2019-01-18 07:32:55.213]    MAXLOGAGE: Importing up to 24.0 hours of log data
   [2019-01-18 07:32:55.213]    PRIVACYLEVEL: Set to 0
   [2019-01-18 07:32:55.214]    IGNORE_LOCALHOST: Show queries from localhost
   [2019-01-18 07:32:55.214]    BLOCKINGMODE: Null IPs for blocked domains
   [2019-01-18 07:32:55.216]    REGEX_DEBUGMODE: Inactive
   [2019-01-18 07:32:55.216]    ANALYZE_ONLY_A_AND_AAAA: Disabled. Analyzing all queries
   [2019-01-18 07:32:55.216]    DBIMPORT: Importing history from database
   [2019-01-18 07:32:55.216]    PIDFILE: Using /var/run/pihole-FTL.pid
   [2019-01-18 07:32:55.216]    PORTFILE: Using /var/run/pihole-FTL.port
   [2019-01-18 07:32:55.216]    SOCKETFILE: Using /var/run/pihole/FTL.sock
   [2019-01-18 07:32:55.217]    WHITELISTFILE: Using /etc/pihole/whitelist.txt
   [2019-01-18 07:32:55.217]    BLACKLISTFILE: Using /etc/pihole/black.list
   [2019-01-18 07:32:55.218]    GRAVITYFILE: Using /etc/pihole/gravity.list
   [2019-01-18 07:32:55.218]    REGEXLISTFILE: Using /etc/pihole/regex.list
   [2019-01-18 07:32:55.218]    SETUPVARSFILE: Using /etc/pihole/setupVars.conf
   [2019-01-18 07:32:55.218]    AUDITLISTFILE: Using /etc/pihole/auditlog.list
   [2019-01-18 07:32:55.218] Finished config file parsing
   [2019-01-18 07:32:55.218] INFO: No whitelist file found
   [2019-01-18 07:32:55.219] Compiled 0 Regex filters and 0 whitelisted domains in 0.2 msec (0 errors)
   [2019-01-18 07:32:55.221] db_init() - Cannot open database (14): unable to open database file

   -----tail of pihole-FTL.log------
   [2019-01-18 08:53:23.747]    MAXDBDAYS: max age for stored queries is 365 days
   [2019-01-18 08:53:23.749]    RESOLVE_IPV6: Resolve IPv6 addresses
   [2019-01-18 08:53:23.749]    RESOLVE_IPV4: Resolve IPv4 addresses
   [2019-01-18 08:53:23.749]    DBINTERVAL: saving to DB file every minute
   [2019-01-18 08:53:23.749]    DBFILE: Using /etc/pihole/pihole-FTL.db
   [2019-01-18 08:53:23.749]    MAXLOGAGE: Importing up to 24.0 hours of log data
   [2019-01-18 08:53:23.749]    PRIVACYLEVEL: Set to 0
   [2019-01-18 08:53:23.749]    IGNORE_LOCALHOST: Show queries from localhost
   [2019-01-18 08:53:23.751]    BLOCKINGMODE: Null IPs for blocked domains
   [2019-01-18 08:53:23.752]    REGEX_DEBUGMODE: Inactive
   [2019-01-18 08:53:23.752]    ANALYZE_ONLY_A_AND_AAAA: Disabled. Analyzing all queries
   [2019-01-18 08:53:23.752]    DBIMPORT: Importing history from database
   [2019-01-18 08:53:23.752]    PIDFILE: Using /var/run/pihole-FTL.pid
   [2019-01-18 08:53:23.752]    PORTFILE: Using /var/run/pihole-FTL.port
   [2019-01-18 08:53:23.752]    SOCKETFILE: Using /var/run/pihole/FTL.sock
   [2019-01-18 08:53:23.752]    WHITELISTFILE: Using /etc/pihole/whitelist.txt
   [2019-01-18 08:53:23.754]    BLACKLISTFILE: Using /etc/pihole/black.list
   [2019-01-18 08:53:23.754]    GRAVITYFILE: Using /etc/pihole/gravity.list
   [2019-01-18 08:53:23.754]    REGEXLISTFILE: Using /etc/pihole/regex.list
   [2019-01-18 08:53:23.754]    SETUPVARSFILE: Using /etc/pihole/setupVars.conf
   [2019-01-18 08:53:23.754]    AUDITLISTFILE: Using /etc/pihole/auditlog.list
   [2019-01-18 08:53:23.754] Finished config file parsing
   [2019-01-18 08:53:23.756] INFO: No whitelist file found
   [2019-01-18 08:53:23.756] Compiled 0 Regex filters and 0 whitelisted domains in 1.4 msec (0 errors)
   [2019-01-18 08:53:23.773] Database successfully initialized
   [2019-01-18 08:53:23.775] Imported 0 queries from the long-term database
   [2019-01-18 08:53:23.775]  -> Total DNS queries: 0
   [2019-01-18 08:53:23.775]  -> Cached DNS queries: 0
   [2019-01-18 08:53:23.776]  -> Forwarded DNS queries: 0
   [2019-01-18 08:53:23.776]  -> Exactly blocked DNS queries: 0
   [2019-01-18 08:53:23.776]  -> Unknown DNS queries: 0
   [2019-01-18 08:53:23.776]  -> Unique domains: 0
   [2019-01-18 08:53:23.776]  -> Unique clients: 0
   [2019-01-18 08:53:23.776]  -> Known forward destinations: 0
   [2019-01-18 08:53:23.776] Successfully accessed setupVars.conf

*** [ DIAGNOSING ]: Locale
    LANG=

*** [ DIAGNOSING ]: Pi-hole log
-rw-r--r-- 1 pihole pihole 0 Jan 18 08:53 /var/log/pihole.log
   -----head of pihole.log------


********************************************
********************************************
[✓] ** 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: 4g9qxqw58b
***********************************
***********************************

   * 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

Looks like the DNS resolution is not working ...

sudo systemctl status pihole-FTL.service

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