Upgrade Pihole ftl broke

The issue I am facing:
updated pihole dns failed.
There was a problem applying your settings.
Debugging information:
PHP error (2): fsockopen(): unable to connect to 127.0.0.1:4711 (Connection refused) in /var/www/html/admin/scripts/pi-hole/php/FTL.php:47

Details about my system:
Running on a Unifi Could key ver 1

[Guide] Installing Pi-hole on Unifi Cloudkey v1

What I have changed since installing Pi-hole:
i tried to update it which borked my install

[✓] Your debug token is: https://tricorder.pi-hole.net/RMIK5XGL/

sudo service dnsmasq status
root@UniFi-CloudKey:~# sudo service dnsmasq status
Unit dnsmasq.service could not be found.

sudo service pihole-FTL status
root@UniFi-CloudKey:~# sudo service pihole-FTL status
● pihole-FTL.service - Pi-hole FTL
   Loaded: loaded (/etc/systemd/system/pihole-FTL.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Sat 2023-01-21 23:52:57 PST; 12min ago
  Process: 23366 ExecStartPre=/opt/pihole/pihole-FTL-prestart.sh (code=exited, status=0/SUCCESS)
  Process: 23382 ExecStart=/usr/bin/pihole-FTL -f (code=exited, status=218/CAPABILITIES)
  Process: 23384 ExecStopPost=/opt/pihole/pihole-FTL-poststop.sh (code=exited, status=0/SUCCESS)
 Main PID: 23382 (code=exited, status=218/CAPABILITIES)

Jan 21 23:52:57 UniFi-CloudKey systemd[1]: Stopped Pi-hole FTL.
Jan 21 23:52:57 UniFi-CloudKey systemd[1]: pihole-FTL.service: Start request repeated too quickly.
Jan 21 23:52:57 UniFi-CloudKey systemd[1]: pihole-FTL.service: Failed with result 'exit-code'.
Jan 21 23:52:57 UniFi-CloudKey systemd[1]: Failed to start Pi-hole FTL.



Any ideas on how I might fix this?

I am at a loss here guys. Do i need to update debian os to a new version? I dont know how to get the dns server to run. Suggestions ? It worked great for a long time before the recent upgrade to new version

Can i install a older version before 5.20 or whatever? What would the command be with curl to download an older version

I really like the software, i am currently using truenas scale to run pi hole in a docker type deal, while my unifi cloud key gen 1 sits running pi hole with no dns server.

If I have do I guess i could buy a rasberry pi computer, but i dont know what version would be good, and the cloud key works so well, and it is poe powered

Please upload a fresh debug log and post the new token here. You old log auto-expired after 48 hours.

root@UniFi-CloudKey:~# sudo service dnsmasq status
Unit dnsmasq.service could not be found.

root@UniFi-CloudKey:~# sudo service pihole-FTL status
● pihole-FTL.service - Pi-hole FTL
Loaded: loaded (/etc/systemd/system/pihole-FTL.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Sun 2023-01-22 04:12:49 PST; 3 days ago
Process: 3049 ExecStartPre=/opt/pihole/pihole-FTL-prestart.sh (code=exited, status=0/SUCCESS)
Process: 3063 ExecStart=/usr/bin/pihole-FTL -f (code=exited, status=218/CAPABILITIES)
Process: 3065 ExecStopPost=/opt/pihole/pihole-FTL-poststop.sh (code=exited, status=0/SUCCESS)
Main PID: 3063 (code=exited, status=218/CAPABILITIES)

Jan 22 04:12:49 UniFi-CloudKey systemd[1]: pihole-FTL.service: Service RestartSec=5s expired, scheduling restart.
Jan 22 04:12:49 UniFi-CloudKey systemd[1]: pihole-FTL.service: Scheduled restart job, restart counter is at 5.
Jan 22 04:12:49 UniFi-CloudKey systemd[1]: Stopped Pi-hole FTL.
Jan 22 04:12:49 UniFi-CloudKey systemd[1]: pihole-FTL.service: Start request repeated too quickly.
Jan 22 04:12:49 UniFi-CloudKey systemd[1]: pihole-FTL.service: Failed with result 'exit-code'.
Jan 22 04:12:49 UniFi-CloudKey systemd[1]: Failed to start Pi-hole FTL.
root@UniFi-CloudKey:~#

  • The debug log can be uploaded to tricorder.pi-hole.net for sharing with developers only.

[?] Would you like to upload the log? [y/N] y
* Using curl for transmission.
* curl failed, contact Pi-hole support for assistance.
* Error message: curl: (22) The requested URL returned error: 500

[✗] There was an error uploading your debug log.

  • Please try again or contact the Pi-hole team for assistance.
  • A local copy of the debug log can be found at: /var/log/pihole/pihole_debug.log
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] 2023-01-25:16:41:14 debug log has been initialized.
[i] System has been running for 3 days, 17 hours, 34 minutes

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

*** [ DIAGNOSING ]: Core version
[✓] Version: v5.15
[i] Remotes: origin     https://github.com/pi-hole/pi-hole.git (fetch)
             origin     https://github.com/pi-hole/pi-hole.git (push)
[i] Branch: master
[i] Commit: v5.15-0-g9048429

*** [ DIAGNOSING ]: Web version
[✓] Version: v5.18.1
[i] Remotes: origin     https://github.com/pi-hole/AdminLTE.git (fetch)
             origin     https://github.com/pi-hole/AdminLTE.git (push)
[i] Branch: master
[i] Commit: v5.18.1-0-g30668d4

*** [ DIAGNOSING ]: FTL version
[✓] Version: v5.20.1
[i] Branch: master
[i] Commit: 47128aaf

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

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

*** [ DIAGNOSING ]: Operating system
[✓] Distro:  Debian
[✓] Version: 10
[✓] dig return code: 0
[i] dig response: "Raspbian=10,11 Ubuntu=20,22 Debian=10,11 Fedora=36,37 CentOS=8,9"
[✓] Distro and version supported

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

*** [ DIAGNOSING ]: FirewallD
[i] Firewalld service inactive

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

*** [ DIAGNOSING ]: Disk usage
   Filesystem                     Size  Used Avail Use% Mounted on
   udev                            10M     0   10M   0% /dev
   tmpfs                          404M  424K  404M   1% /run
   /dev/disk/by-label/userdata    2.9G  1.2G  1.8G  41% /mnt/.rwfs
   /dev/disk/by-partlabel/rootfs  334M  334M     0 100% /mnt/.rofs
   aufs-root                      2.9G  1.2G  1.8G  41% /
   tmpfs                         1009M     0 1009M   0% /dev/shm
   tmpfs                          5.0M     0  5.0M   0% /run/lock
   tmpfs                         1009M     0 1009M   0% /sys/fs/cgroup
   tmpfs                         1009M   30M  980M   3% /tmp
   /dev/mmcblk0p8                  11G   41M   11G   1% /srv
   /dev/mmcblk1p1                 7.2G   62M  7.2G   1% /data
   tmpfs                          202M     0  202M   0% /run/user/0

*** [ DIAGNOSING ]: Network interfaces and addresses
   1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default
       link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
       inet 127.0.0.1/8 scope host lo
          valid_lft forever preferred_lft forever
       inet6 ::1/128 scope host
          valid_lft forever preferred_lft forever
   2: eth0p: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN group default qlen 1000
       link/ether b6:fb:e4:2a:aa:a1 brd ff:ff:ff:ff:ff:ff
   3: gre0: <NOARP> mtu 1476 qdisc noop state DOWN group default
       link/gre 0.0.0.0 brd 0.0.0.0
   4: gretap0: <BROADCAST,MULTICAST> mtu 1476 qdisc noop state DOWN group default qlen 1000
       link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
   5: sit0: <NOARP> mtu 1480 qdisc noop state DOWN group default
       link/sit 0.0.0.0 brd 0.0.0.0
   6: ip6tnl0: <NOARP> mtu 1452 qdisc noop state DOWN group default
       link/tunnel6 :: brd ::
   7: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN group default qlen 1000
       link/ether b4:fb:e4:2a:aa:a1 brd ff:ff:ff:ff:ff:ff
       inet 192.168.5.3/24 brd 192.168.5.255 scope global dynamic eth0
          valid_lft 82609sec preferred_lft 82609sec
       inet6 fe80::b6fb:e4ff:fe2a:aaa1/64 scope link
          valid_lft forever preferred_lft forever

*** [ DIAGNOSING ]: Network routing table
   default via 192.168.5.1 dev eth0 proto dhcp src 192.168.5.3 metric 1024
   192.168.5.0/24 dev eth0 proto kernel scope link src 192.168.5.3
   192.168.5.1 dev eth0 proto dhcp scope link src 192.168.5.3 metric 1024

*** [ DIAGNOSING ]: Networking
[✓] IPv4 address(es) bound to the eth0 interface:
    192.168.5.3/24

[✓] IPv6 address(es) bound to the eth0 interface:
    fe80::b6fb:e4ff:fe2a:aaa1/64

[i] Default IPv4 gateway(s):
     192.168.5.1
   * Pinging first gateway 192.168.5.1...
[✓] Gateway responded.
[i] Default IPv6 gateway(s):

*** [ DIAGNOSING ]: Ports in use
    udp:192.168.5.3:68 is in use by systemd-network
    udp:0.0.0.0:5353 is in use by avahi-daemon
    udp:0.0.0.0:54274 is in use by avahi-daemon
    udp:*:5353 is in use by avahi-daemon
    udp:*:59005 is in use by avahi-daemon
    tcp:127.0.0.1:9090 is in use by ubnt-systemhub
    tcp:0.0.0.0:8080 is in use by lighttpd
    tcp:0.0.0.0:22 is in use by sshd
    tcp:127.0.0.1:25 is in use by exim4
    tcp:*:8080 is in use by lighttpd
    tcp:*:22 is in use by sshd
    tcp:[::1]:25 is in use by exim4

*** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
[✗] Failed to resolve comunicazioni.stanhome.it on lo (127.0.0.1)
[✓] No IPv4 address available on eth0p
[✗] Failed to resolve comunicazioni.stanhome.it on eth0 (192.168.5.3)
[✓] doubleclick.com is 142.250.69.206 via a remote, public DNS server (8.8.8.8)

*** [ DIAGNOSING ]: Name resolution (IPv6) using a random blocked domain and a known ad-serving domain
[✗] Failed to resolve polska-dpd.17253.space on lo (::1)
[✓] No IPv6 address available on eth0p
[✗] Failed to resolve polska-dpd.17253.space on eth0 (fe80::b6fb:e4ff:fe2a:aaa1)
[✗] Failed to resolve doubleclick.com via a remote, public DNS server (2001:4860:4860::8888)

*** [ DIAGNOSING ]: Discovering active DHCP servers (takes 10 seconds)
   Scanning all your interfaces for DHCP servers
   Timeout: 10 seconds

   WARN: Could not sendto() in send_dhcp_discover() (/__w/FTL/FTL/src/dhcp-discover.c:233): Network is unreachable
   WARN: Could not sendto() in send_dhcp_discover() (/__w/FTL/FTL/src/dhcp-discover.c:233): Network is unreachable
   WARN: Could not sendto() in send_dhcp_discover() (/__w/FTL/FTL/src/dhcp-discover.c:233): Network is unreachable
   WARN: Could not sendto() in send_dhcp_discover() (/__w/FTL/FTL/src/dhcp-discover.c:233): Network is unreachable
   * Received 305 bytes from eth0:192.168.5.1
     Offered IP address: 192.168.5.3
     Server IP address: 192.168.5.1
     Relay-agent IP address: N/A
     BOOTP server: (empty)
     BOOTP file: (empty)
     DHCP options:
      Message type: DHCPOFFER (2)
      server-identifier: 192.168.5.1
      lease-time: 86400 ( 1d )
      renewal-time: 43200 ( 12h )
      rebinding-time: 75600 ( 21h )
      netmask: 255.255.255.0
      domain-name: "localdomain"
      broadcast: 192.168.5.255
      dns-server: 192.168.5.1
      router: 192.168.5.1
      --- end of options ---

   DHCP packets received on interface eth0: 1
   DHCP packets received on interface gre0: 0
   DHCP packets received on interface ip6tnl0: 0
   DHCP packets received on interface gretap0: 0
   DHCP packets received on interface sit0: 0
   DHCP packets received on interface lo: 0
   DHCP packets received on interface eth0p: 0

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

*** [ DIAGNOSING ]: Pi-hole-FTL full status
   ● pihole-FTL.service - Pi-hole FTL
   Loaded: loaded (/etc/systemd/system/pihole-FTL.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Sun 2023-01-22 04:12:49 PST; 3 days ago
  Process: 3049 ExecStartPre=/opt/pihole/pihole-FTL-prestart.sh (code=exited, status=0/SUCCESS)
  Process: 3063 ExecStart=/usr/bin/pihole-FTL -f (code=exited, status=218/CAPABILITIES)
  Process: 3065 ExecStopPost=/opt/pihole/pihole-FTL-poststop.sh (code=exited, status=0/SUCCESS)
 Main PID: 3063 (code=exited, status=218/CAPABILITIES)

Jan 22 04:12:49 UniFi-CloudKey systemd[1]: pihole-FTL.service: Service RestartSec=5s expired, scheduling restart.
Jan 22 04:12:49 UniFi-CloudKey systemd[1]: pihole-FTL.service: Scheduled restart job, restart counter is at 5.
Jan 22 04:12:49 UniFi-CloudKey systemd[1]: Stopped Pi-hole FTL.
Jan 22 04:12:49 UniFi-CloudKey systemd[1]: pihole-FTL.service: Start request repeated too quickly.
Jan 22 04:12:49 UniFi-CloudKey systemd[1]: pihole-FTL.service: Failed with result 'exit-code'.
Jan 22 04:12:49 UniFi-CloudKey systemd[1]: Failed to start Pi-hole FTL.

*** [ DIAGNOSING ]: Setup variables
    PIHOLE_INTERFACE=eth0
    PIHOLE_DNS_1=1.1.1.1
    PIHOLE_DNS_2=1.0.0.1
    QUERY_LOGGING=true
    INSTALL_WEB_SERVER=true
    INSTALL_WEB_INTERFACE=true
    LIGHTTPD_ENABLED=true
    CACHE_SIZE=10000
    DNS_FQDN_REQUIRED=true
    DNS_BOGUS_PRIV=true
    DNSMASQ_LISTENING=local
    WEBUIBOXEDLAYOUT=boxed
    WEBTHEME=default-dark

*** [ DIAGNOSING ]: Dashboard headers
[✗] Web interface X-Header: X-Header does not match or could not be retrieved.


*** [ DIAGNOSING ]: Pi-hole FTL Query Database
-rw-rw-r-- 1 pihole pihole 0 Jan 22 00:04 /etc/pihole/pihole-FTL.db

*** [ DIAGNOSING ]: Gravity Database
-rw-rw-r-- 1 pihole pihole 12M Jan 22 04:12 /etc/pihole/gravity.db

*** [ DIAGNOSING ]: Info table
   property              value
   --------------------  ----------------------------------------
   version               15
   updated               1674389536
   gravity_count         171069
   Last gravity run finished at: Sun Jan 22 04:12:16 PST 2023

   ----- First 10 Gravity Domains -----
   localhost.localdomain
   eu1.clevertap-prod.com
   wizhumpgyros.com
   coccyxwickimp.com
   webmail-who-int.000webhostapp.com
   010sec.com
   01mspmd5yalky8.com
   0byv9mgbn0.com
   ns6.0pendns.org
   dns.0pengl.com


*** [ DIAGNOSING ]: Groups
   id    enabled  name                                                date_added           date_modified        description
   ----  -------  --------------------------------------------------  -------------------  -------------------  --------------------------------------------------
   0           1  Default                                             2023-01-21 23:28:12  2023-01-21 23:28:12  The default group

*** [ DIAGNOSING ]: Domainlist (0/1 = exact white-/blacklist, 2/3 = regex white-/blacklist)

*** [ DIAGNOSING ]: Clients

*** [ DIAGNOSING ]: Adlists
   id     enabled  group_ids     address                                                                                               date_added           date_modified        comment
   -----  -------  ------------  ----------------------------------------------------------------------------------------------------  -------------------  -------------------  --------------------------------------------------
   1            1  0             https://raw.githubusercontent.com/StevenBlack/hosts/master/hosts                                      2023-01-21 23:28:12  2023-01-21 23:28:12  Migrated from /etc/pihole/adlists.list

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

-rw-r--r-- 1 root root 0 Jan 21 23:11 /etc/pihole/custom.list

-rw-r--r-- 1 root root 65 Jan 22 04:12 /etc/pihole/local.list

-rw-r--r-- 1 root root 241 Jan 21 23:11 /etc/pihole/logrotate
   /var/log/pihole/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-rw-r-- 1 pihole root 127 Jan 21 23:52 /etc/pihole/pihole-FTL.conf
   PRIVACYLEVEL=0

-rw-r--r-- 1 root root 324 Jan 24 18:46 /etc/pihole/versions
   CORE_VERSION=v5.15
   CORE_BRANCH=master
   CORE_HASH=9048429b
   GITHUB_CORE_VERSION=v5.15.2
   GITHUB_CORE_HASH=262ffe4
   WEB_VERSION=v5.18.1
   WEB_BRANCH=master
   WEB_HASH=30668d4d
   GITHUB_WEB_VERSION=v5.18.2
   GITHUB_WEB_HASH=c3c230a
   FTL_VERSION=v5.20.1
   FTL_BRANCH=master
   FTL_HASH=47128aaf
   GITHUB_FTL_VERSION=v5.20.1
   GITHUB_FTL_HASH=47128aa

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

-rw-r--r-- 1 root root 1.4K Jan 21 23:52 /etc/dnsmasq.d/01-pihole.conf
   addn-hosts=/etc/pihole/local.list
   addn-hosts=/etc/pihole/custom.list
   localise-queries
   no-resolv
   log-queries
   log-facility=/var/log/pihole/pihole.log
   log-async
   cache-size=10000
   server=1.1.1.1
   server=1.0.0.1
   domain-needed
   expand-hosts
   bogus-priv
   local-service

-rw-r--r-- 1 root root 2.2K Jan 21 23:52 /etc/dnsmasq.d/06-rfc6761.conf
   server=/test/
   server=/localhost/
   server=/invalid/
   server=/bind/
   server=/onion/

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

-rw-r--r-- 1 root root 2.0K Jan 21 23:43 /etc/lighttpd/lighttpd.conf
   server.modules = (
        "mod_indexfile",
        "mod_access",
        "mod_alias",
        "mod_redirect",
   )
   server.document-root        = "/var/www/html"
   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                 = 8080
   server.http-parseopts = (
     "header-strict"           => "enable",# default
     "host-strict"             => "enable",# default
     "host-normalize"          => "enable",# default
     "url-normalize-unreserved"=> "enable",# recommended highly
     "url-normalize-required"  => "enable",# recommended
     "url-ctrls-reject"        => "enable",# recommended
     "url-path-2f-decode"      => "enable",# recommended highly (unless breaks app)
     "url-path-dotseg-remove"  => "enable",# recommended highly (unless breaks app)
   )
   index-file.names            = ( "index.php", "index.html" )
   url.access-deny             = ( "~", ".inc" )
   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.conf.pl"
   include "/etc/lighttpd/conf-enabled/*.conf"
   server.modules += (
        "mod_compress",
        "mod_dirlisting",
        "mod_staticfile",
   )

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

-rw-r--r-- 1 root root 1.7K Jan 21 23:52 /etc/cron.d/pihole
   12 4   * * 7   root    PATH="$PATH:/usr/sbin:/usr/local/bin/" pihole updateGravity >/var/log/pihole/pihole_updateGravity.log || cat /var/log/pihole/pihole_updateGravity.log
   00 00   * * *   root    PATH="$PATH:/usr/sbin:/usr/local/bin/" pihole flush once quiet
   @reboot root /usr/sbin/logrotate --state /var/lib/logrotate/pihole /etc/pihole/logrotate
   46 18  * * *   root    PATH="$PATH:/usr/sbin:/usr/local/bin/" pihole updatechecker
   @reboot root    PATH="$PATH:/usr/sbin:/usr/local/bin/" pihole updatechecker reboot

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

-rw-r--r-- 1 www-data www-data 4.8K Jan 25 16:39 /var/log/lighttpd/error-pihole.log
   -----head of error-pihole.log------
   2023-01-22 00:00:00: (server.c.1759) logfiles cycled UID = 0 PID = 25326
   2023-01-22 00:14:02: (gw_backend.c.476) unlink /tmp/pihole-php-fastcgi.socket-0 after connect failed: Connection refused
   2023-01-22 00:14:03: (mod_fastcgi.c.421) FastCGI-stderr: PHP Warning:  SQLite3::query(): Unable to prepare statement: 1, no such table: message in /var/www/html/admin/api_db.php on line 385
   2023-01-22 00:14:08: (mod_fastcgi.c.421) FastCGI-stderr: PHP Warning:  SQLite3::query(): Unable to prepare statement: 1, no such table: message in /var/www/html/admin/api_db.php on line 385
   2023-01-22 10:00:02: (gw_backend.c.476) unlink /tmp/pihole-php-fastcgi.socket-0 after connect failed: Connection refused
   2023-01-22 10:00:02: (mod_fastcgi.c.421) FastCGI-stderr: PHP Warning:  SQLite3::query(): Unable to prepare statement: 1, no such table: message in /var/www/html/admin/api_db.php on line 385
   2023-01-22 10:00:07: (mod_fastcgi.c.421) FastCGI-stderr: PHP Warning:  SQLite3::query(): Unable to prepare statement: 1, no such table: message in /var/www/html/admin/api_db.php on line 385
   2023-01-22 10:04:05: (mod_fastcgi.c.421) FastCGI-stderr: PHP Warning:  SQLite3::query(): Unable to prepare statement: 1, no such table: message in /var/www/html/admin/api_db.php on line 385
   2023-01-22 10:04:10: (mod_fastcgi.c.421) FastCGI-stderr: PHP Warning:  SQLite3::query(): Unable to prepare statement: 1, no such table: message in /var/www/html/admin/api_db.php on line 385
   2023-01-22 10:04:34: (mod_fastcgi.c.421) FastCGI-stderr: PHP Warning:  SQLite3::query(): Unable to prepare statement: 1, no such table: message in /var/www/html/admin/api_db.php on line 385
   2023-01-22 10:04:38: (mod_fastcgi.c.421) FastCGI-stderr: PHP Warning:  SQLite3::query(): Unable to prepare statement: 1, no such table: message in /var/www/html/admin/api_db.php on line 385
   2023-01-22 10:04:49: (mod_fastcgi.c.421) FastCGI-stderr: PHP Warning:  SQLite3::query(): Unable to prepare statement: 1, no such table: message in /var/www/html/admin/api_db.php on line 385
   2023-01-22 10:04:53: (mod_fastcgi.c.421) FastCGI-stderr: PHP Warning:  SQLite3::query(): Unable to prepare statement: 1, no such table: message in /var/www/html/admin/api_db.php on line 385
   2023-01-22 10:04:59: (mod_fastcgi.c.421) FastCGI-stderr: PHP Warning:  SQLite3::query(): Unable to prepare statement: 1, no such table: message in /var/www/html/admin/api_db.php on line 385
   2023-01-22 10:05:03: (mod_fastcgi.c.421) FastCGI-stderr: PHP Warning:  SQLite3::query(): Unable to prepare statement: 1, no such table: message in /var/www/html/admin/api_db.php on line 385
   2023-01-22 10:05:06: (mod_fastcgi.c.421) FastCGI-stderr: PHP Warning:  SQLite3::query(): Unable to prepare statement: 1, no such table: message in /var/www/html/admin/api_db.php on line 385
   2023-01-22 10:05:10: (mod_fastcgi.c.421) FastCGI-stderr: PHP Warning:  SQLite3::query(): Unable to prepare statement: 1, no such table: message in /var/www/html/admin/api_db.php on line 385
   2023-01-22 10:05:31: (mod_fastcgi.c.421) FastCGI-stderr: PHP Warning:  SQLite3::query(): Unable to prepare statement: 1, no such table: message in /var/www/html/admin/api_db.php on line 385
   2023-01-22 10:05:37: (mod_fastcgi.c.421) FastCGI-stderr: PHP Warning:  SQLite3::query(): Unable to prepare statement: 1, no such table: message in /var/www/html/admin/api_db.php on line 385
   2023-01-22 18:16:56: (gw_backend.c.476) unlink /tmp/pihole-php-fastcgi.socket-0 after connect failed: Connection refused
   2023-01-22 18:16:57: (mod_fastcgi.c.421) FastCGI-stderr: PHP Warning:  SQLite3::query(): Unable to prepare statement: 1, no such table: message in /var/www/html/admin/api_db.php on line 385
   2023-01-22 18:17:02: (mod_fastcgi.c.421) FastCGI-stderr: PHP Warning:  SQLite3::query(): Unable to prepare statement: 1, no such table: message in /var/www/html/admin/api_db.php on line 385
   2023-01-25 06:08:58: (gw_backend.c.476) unlink /tmp/pihole-php-fastcgi.socket-0 after connect failed: Connection refused
   2023-01-25 06:08:59: (mod_fastcgi.c.421) FastCGI-stderr: PHP Warning:  SQLite3::query(): Unable to prepare statement: 1, no such table: message in /var/www/html/admin/api_db.php on line 385
   2023-01-25 06:09:04: (mod_fastcgi.c.421) FastCGI-stderr: PHP Warning:  SQLite3::query(): Unable to prepare statement: 1, no such table: message in /var/www/html/admin/api_db.php on line 385

   -----tail of error-pihole.log------
   2023-01-22 00:14:08: (mod_fastcgi.c.421) FastCGI-stderr: PHP Warning:  SQLite3::query(): Unable to prepare statement: 1, no such table: message in /var/www/html/admin/api_db.php on line 385
   2023-01-22 10:00:02: (gw_backend.c.476) unlink /tmp/pihole-php-fastcgi.socket-0 after connect failed: Connection refused
   2023-01-22 10:00:02: (mod_fastcgi.c.421) FastCGI-stderr: PHP Warning:  SQLite3::query(): Unable to prepare statement: 1, no such table: message in /var/www/html/admin/api_db.php on line 385
   2023-01-22 10:00:07: (mod_fastcgi.c.421) FastCGI-stderr: PHP Warning:  SQLite3::query(): Unable to prepare statement: 1, no such table: message in /var/www/html/admin/api_db.php on line 385
   2023-01-22 10:04:05: (mod_fastcgi.c.421) FastCGI-stderr: PHP Warning:  SQLite3::query(): Unable to prepare statement: 1, no such table: message in /var/www/html/admin/api_db.php on line 385
   2023-01-22 10:04:10: (mod_fastcgi.c.421) FastCGI-stderr: PHP Warning:  SQLite3::query(): Unable to prepare statement: 1, no such table: message in /var/www/html/admin/api_db.php on line 385
   2023-01-22 10:04:34: (mod_fastcgi.c.421) FastCGI-stderr: PHP Warning:  SQLite3::query(): Unable to prepare statement: 1, no such table: message in /var/www/html/admin/api_db.php on line 385
   2023-01-22 10:04:38: (mod_fastcgi.c.421) FastCGI-stderr: PHP Warning:  SQLite3::query(): Unable to prepare statement: 1, no such table: message in /var/www/html/admin/api_db.php on line 385
   2023-01-22 10:04:49: (mod_fastcgi.c.421) FastCGI-stderr: PHP Warning:  SQLite3::query(): Unable to prepare statement: 1, no such table: message in /var/www/html/admin/api_db.php on line 385
   2023-01-22 10:04:53: (mod_fastcgi.c.421) FastCGI-stderr: PHP Warning:  SQLite3::query(): Unable to prepare statement: 1, no such table: message in /var/www/html/admin/api_db.php on line 385
   2023-01-22 10:04:59: (mod_fastcgi.c.421) FastCGI-stderr: PHP Warning:  SQLite3::query(): Unable to prepare statement: 1, no such table: message in /var/www/html/admin/api_db.php on line 385
   2023-01-22 10:05:03: (mod_fastcgi.c.421) FastCGI-stderr: PHP Warning:  SQLite3::query(): Unable to prepare statement: 1, no such table: message in /var/www/html/admin/api_db.php on line 385
   2023-01-22 10:05:06: (mod_fastcgi.c.421) FastCGI-stderr: PHP Warning:  SQLite3::query(): Unable to prepare statement: 1, no such table: message in /var/www/html/admin/api_db.php on line 385
   2023-01-22 10:05:10: (mod_fastcgi.c.421) FastCGI-stderr: PHP Warning:  SQLite3::query(): Unable to prepare statement: 1, no such table: message in /var/www/html/admin/api_db.php on line 385
   2023-01-22 10:05:31: (mod_fastcgi.c.421) FastCGI-stderr: PHP Warning:  SQLite3::query(): Unable to prepare statement: 1, no such table: message in /var/www/html/admin/api_db.php on line 385
   2023-01-22 10:05:37: (mod_fastcgi.c.421) FastCGI-stderr: PHP Warning:  SQLite3::query(): Unable to prepare statement: 1, no such table: message in /var/www/html/admin/api_db.php on line 385
   2023-01-22 18:16:56: (gw_backend.c.476) unlink /tmp/pihole-php-fastcgi.socket-0 after connect failed: Connection refused
   2023-01-22 18:16:57: (mod_fastcgi.c.421) FastCGI-stderr: PHP Warning:  SQLite3::query(): Unable to prepare statement: 1, no such table: message in /var/www/html/admin/api_db.php on line 385
   2023-01-22 18:17:02: (mod_fastcgi.c.421) FastCGI-stderr: PHP Warning:  SQLite3::query(): Unable to prepare statement: 1, no such table: message in /var/www/html/admin/api_db.php on line 385
   2023-01-25 06:08:58: (gw_backend.c.476) unlink /tmp/pihole-php-fastcgi.socket-0 after connect failed: Connection refused
   2023-01-25 06:08:59: (mod_fastcgi.c.421) FastCGI-stderr: PHP Warning:  SQLite3::query(): Unable to prepare statement: 1, no such table: message in /var/www/html/admin/api_db.php on line 385
   2023-01-25 06:09:04: (mod_fastcgi.c.421) FastCGI-stderr: PHP Warning:  SQLite3::query(): Unable to prepare statement: 1, no such table: message in /var/www/html/admin/api_db.php on line 385
   2023-01-25 16:38:55: (gw_backend.c.476) unlink /tmp/pihole-php-fastcgi.socket-0 after connect failed: Connection refused
   2023-01-25 16:38:57: (mod_fastcgi.c.421) FastCGI-stderr: PHP Warning:  SQLite3::query(): Unable to prepare statement: 1, no such table: message in /var/www/html/admin/api_db.php on line 385
   2023-01-25 16:39:02: (mod_fastcgi.c.421) FastCGI-stderr: PHP Warning:  SQLite3::query(): Unable to prepare statement: 1, no such table: message in /var/www/html/admin/api_db.php on line 385

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

-rw-r--r-- 1 pihole pihole 0 Jan 21 23:15 /var/log/pihole/FTL.log
   -----head of FTL.log------

   -----tail of FTL.log------

*** [ DIAGNOSING ]: contents of /dev/shm

*** [ DIAGNOSING ]: contents of /etc

-rw-r--r-- 1 root root 24 Jan 21 23:52 /etc/dnsmasq.conf
   conf-dir=/etc/dnsmasq.d

lrwxrwxrwx 1 root root 32 Jan 21 23:11 /etc/resolv.conf -> /run/systemd/resolve/resolv.conf
   nameserver 192.168.5.1

*** [ DIAGNOSING ]: Pi-hole diagnosis messages
Error: in prepare, no such table: message

*** [ DIAGNOSING ]: Locale
    LANG=C

*** [ DIAGNOSING ]: Pi-hole log
-rw-r----- 1 pihole pihole 0 Jan 21 23:15 /var/log/pihole/pihole.log
   -----head of pihole.log------

   -----tail of pihole.log------

********************************************
********************************************
[✓] ** FINISHED DEBUGGING! **

   * The debug log can be uploaded to tricorder.pi-hole.net for sharing with developers only.

[?] Would you like to upload the log? [y/N] y
    * Using curl for transmission.
    * curl failed, contact Pi-hole support for assistance.
    * Error message: curl: (22) The requested URL returned error: 500

[✗] There was an error uploading your debug log.
   * Please try again or contact the Pi-hole team for assistance.
   * A local copy of the debug log can be found at: /var/log/pihole/pihole_debug.log

root@UniFi-CloudKey:~# ^C

Does it matter if I have 2 pi holes running? I have this one that has the problem with DNS 192.168.5.3

And then I have the pihole running on my truenas scale server at 192.168.5.100/9089
I can shut the server one down if needed.

[✓] Your debug token is: https://tricorder.pi-hole.net/ePWswlxy/
[i] Logs are deleted 48 hours after upload.

Sorry I turned off the server pi hole. reset dns from router back to stock and then re tried to get a code and it worked this time ill leave it like for for a few days.

And sorry if I am not doing this correctly, I only dabble in linux to make my truenas work and I know dos a bit etc but, I am more of a script kiddy finding ways to use hard ware in ways it wasn't designed.

The Error message: curl: (22) The requested URL returned error: 500 message wasn't your fault. Our server had an issue.

Oh, well the dns end wont boot.

Error

There was a problem applying your settings.
Debugging information:
PHP error (2): fsockopen(): unable to connect to 127.0.0.1:4711 (Connection refused) in /var/www/html/admin/scripts/pi-hole/php/FTL.php:47

FTL Information

The FTL service is offline!
off the website.

A post was split to a new topic: DNS service not running

Please check your route "sudo route -v" if you don't have a default route
that got wiped on an update somehow. It should be something like what is below:

Kernel IP routing table
default fire 0.0.0.0 UG 0 0 0 ens160
192.168.xxx.x 0.0.0.0 255.255.255.0 U 0 0 0 ens160

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