Advertisement
Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- 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-02-11:10:56:36 debug log has been initialized.
- *** [ INITIALIZING ] Sourcing setup variables
- [i] Sourcing /etc/pihole/setupVars.conf...
- *** [ DIAGNOSING ]: Core version
- [i] Core: v4.2.1 (https://discourse.pi-hole.net/t/how-do-i-update-pi-hole/249)
- [i] Branch: master
- [i] Commit: v4.2.1-0-ge967fe2
- *** [ DIAGNOSING ]: Web version
- [i] Web: v4.2 (https://discourse.pi-hole.net/t/how-do-i-update-pi-hole/249)
- [i] Branch: master
- [i] Commit: v4.2-0-g347994d
- *** [ DIAGNOSING ]: FTL version
- [✓] FTL: v4.2.1
- *** [ DIAGNOSING ]: lighttpd version
- [i] 1.4.45
- *** [ DIAGNOSING ]: php version
- [i] 7.2.10
- *** [ DIAGNOSING ]: Operating system
- [✓] Ubuntu 18.04.2 LTS
- *** [ DIAGNOSING ]: SELinux
- [i] SELinux not detected
- *** [ DIAGNOSING ]: Processor
- [i] x86_64
- *** [ DIAGNOSING ]: Networking
- [✓] IPv4 address(es) bound to the enp3s0 interface:
- 192.168.1.7/24 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)
- 192.168.1.17/24 matches the IP found in /etc/pihole/setupVars.conf
- [✓] IPv6 address(es) bound to the enp3s0 interface:
- 2600:6c5e:107f:f8c1:519a:ee1f:a03e:f621 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)
- 2600:6c5e:107f:f8c1:3124:379a:56dd:905c matches the IP found in /etc/pihole/setupVars.conf
- 2600:6c5e:107f:f8c1:70c2:e84b:72a4:248a 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)
- 2600:6c5e:107f:f8c1:bde9:1a31:cc7c:cc10 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)
- fe80::9d5a:5fb2:27f9:4d7c 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.1.1
- * Pinging 192.168.1.1...
- [✓] Gateway responded.
- [i] Default IPv6 gateway: fe80::12da:43ff:fe70:ae85
- fe80::12da:43ff:fe70:ae85
- * Pinging fe80::12da:43ff:fe70:ae85
- fe80::12da:43ff:fe70:ae85...
- [✗] Gateway did not respond. (https://discourse.pi-hole.net/t/why-is-a-default-gateway-important-for-pi-hole/3546)
- *** [ DIAGNOSING ]: Ports in use
- [::1]:631 cupsd (IPv6)
- 127.0.0.1:631 cupsd (IPv4)
- *:22 sshd (IPv4)
- *:22 sshd (IPv6)
- 127.0.0.1:5353 unbound (IPv4)
- 127.0.0.1:8953 unbound (IPv4)
- [*:80] is in use by lighttpd
- [*:80] is in use by lighttpd
- [*:53] is in use by pihole-FTL
- [*:53] is in use by pihole-FTL
- [127.0.0.1:4711] is in use by pihole-FTL
- [[::1]:4711] is in use by pihole-FTL
- *** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
- [✓] paypal.account.activity.id73165.mdnfgs.com is 0.0.0.0 via localhost (127.0.0.1)
- [✓] paypal.account.activity.id73165.mdnfgs.com is 0.0.0.0 via Pi-hole (192.168.1.17)
- [✓] doubleclick.com is 216.58.217.238 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
- [✓] bob012.web3000.com is :: via localhost (::1)
- [✓] bob012.web3000.com is :: via Pi-hole (2600:6c5e:107f:f8c1:3124:379a:56dd:905c)
- [✓] doubleclick.com is 2607:f8b0:4002:804::200e via a remote, public DNS server (2001:4860:4860::8888)
- *** [ DIAGNOSING ]: Pi-hole processes
- [✓] lighttpd daemon is active
- [✓] pihole-FTL daemon is active
- *** [ DIAGNOSING ]: Setup variables
- PIHOLE_INTERFACE=enp3s0
- IPV4_ADDRESS=192.168.1.17/24
- IPV6_ADDRESS=2600:6c5e:107f:f8c1:3124:379a:56dd:905c
- QUERY_LOGGING=true
- INSTALL_WEB_SERVER=true
- INSTALL_WEB_INTERFACE=true
- LIGHTTPD_ENABLED=true
- TEMPERATUREUNIT=F
- WEBUIBOXEDLAYOUT=boxed
- DNSMASQ_LISTENING=all
- PIHOLE_DNS_1=127.0.0.1#5353
- PIHOLE_DNS_2=127.0.0.1#5353
- DNS_FQDN_REQUIRED=true
- DNS_BOGUS_PRIV=true
- DNSSEC=false
- CONDITIONAL_FORWARDING=true
- CONDITIONAL_FORWARDING_IP=192.168.1.1
- CONDITIONAL_FORWARDING_DOMAIN=WORKGROUP
- CONDITIONAL_FORWARDING_REVERSE=1.168.192.in-addr.arpa
- BLOCKING_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 2641491 Feb 10 21:50 /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 Feb 10 16:32 /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 154 Feb 10 21:50 /etc/pihole/local.list
- 192.168.1.17 MAXINET-HomeHub
- 2600:6c5e:107f:f8c1:3124:379a:56dd:905c MAXINET-HomeHub
- 192.168.1.17 pi.hole
- 2600:6c5e:107f:f8c1:3124:379a:56dd:905c pi.hole
- -rw-r--r-- 1 root root 238 Feb 10 16:33 /etc/pihole/logrotate
- /var/log/pihole.log {
- su root syslog
- daily
- copytruncate
- rotate 5
- compress
- delaycompress
- notifempty
- nomail
- }
- /var/log/pihole-FTL.log {
- su root syslog
- weekly
- copytruncate
- rotate 3
- compress
- delaycompress
- notifempty
- nomail
- }
- *** [ DIAGNOSING ]: contents of /etc/dnsmasq.d
- -rw-r--r-- 1 root root 1715 Feb 11 09:21 /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
- dhcp-name-match=set:wpad-ignore,wpad
- dhcp-ignore-names=tag:wpad-ignore
- server=127.0.0.1
- server=127.0.0.1
- domain-needed
- bogus-priv
- except-interface=nonexisting
- server=/WORKGROUP/192.168.1.1
- server=/1.168.192.in-addr.arpa/192.168.1.1
- *** [ DIAGNOSING ]: contents of /etc/lighttpd
- -rw-r--r-- 1 root root 3102 Feb 10 16:33 /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 Feb 10 16:33 /etc/cron.d/pihole
- 15 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 15 * * * 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 1000 Feb 11 08:49 /var/log/lighttpd/error.log
- 2019-02-10 16:33:42: (log.c.217) server started
- 2019-02-10 16:34:03: (server.c.1828) server stopped by UID = 0 PID = 1
- 2019-02-10 16:34:04: (log.c.217) server started
- 2019-02-10 16:35:18: (server.c.1828) server stopped by UID = 0 PID = 1
- 2019-02-10 16:36:42: (log.c.217) server started
- 2019-02-10 17:45:19: (server.c.1828) server stopped by UID = 0 PID = 1
- 2019-02-10 17:46:38: (log.c.217) server started
- 2019-02-10 19:12:45: (mod_fastcgi.c.2543) FastCGI-stderr: PHP Warning: unlink(../custom_disable_timer): No such file or directory in /var/www/html/admin/api.php on line 72
- 2019-02-10 21:43:35: (server.c.1828) server stopped by UID = 0 PID = 1
- 2019-02-10 21:44:43: (log.c.217) server started
- 2019-02-10 21:44:51: (mod_fastcgi.c.2543) FastCGI-stderr: PHP Warning: unlink(../custom_disable_timer): No such file or directory in /var/www/html/admin/api.php on line 47
- 2019-02-11 08:19:57: (server.c.1828) server stopped by UID = 0 PID = 1
- 2019-02-11 08:49:58: (log.c.217) server started
- *** [ DIAGNOSING ]: contents of /var/log
- -rw-r--r-- 1 pihole pihole 11485 Feb 11 10:29 /var/log/pihole-FTL.log
- -----head of pihole-FTL.log------
- [2019-02-11 00:23:25.526] Resizing "/FTL-queries" from 2359296 to 2654208
- [2019-02-11 01:13:50.783] Resizing "/FTL-queries" from 2654208 to 2949120
- [2019-02-11 02:04:46.285] Resizing "/FTL-queries" from 2949120 to 3244032
- [2019-02-11 02:55:11.530] Resizing "/FTL-queries" from 3244032 to 3538944
- [2019-02-11 03:46:07.019] Resizing "/FTL-queries" from 3538944 to 3833856
- [2019-02-11 04:35:31.524] Resizing "/FTL-queries" from 3833856 to 4128768
- [2019-02-11 05:26:26.772] Resizing "/FTL-queries" from 4128768 to 4423680
- [2019-02-11 06:15:51.282] Resizing "/FTL-queries" from 4423680 to 4718592
- [2019-02-11 07:06:46.774] Resizing "/FTL-queries" from 4718592 to 5013504
- [2019-02-11 07:57:12.024] Resizing "/FTL-queries" from 5013504 to 5308416
- [2019-02-11 08:19:57.236] Shutting down...
- [2019-02-11 08:19:58.544] Finished final database update
- [2019-02-11 08:19:58.546] ########## FTL terminated after 38114660.0 ms! ##########
- [2019-02-11 08:49:59.363] Using log file /var/log/pihole-FTL.log
- [2019-02-11 08:49:59.387] ########## FTL started! ##########
- [2019-02-11 08:49:59.387] FTL branch: master
- [2019-02-11 08:49:59.387] FTL version: v4.2.1
- [2019-02-11 08:49:59.387] FTL commit: 5f98312
- [2019-02-11 08:49:59.387] FTL date: 2019-02-06 18:36:55 -0800
- [2019-02-11 08:49:59.387] FTL user: pihole
- [2019-02-11 08:49:59.388] Starting config file parsing (/etc/pihole/pihole-FTL.conf)
- [2019-02-11 08:49:59.388] SOCKET_LISTENING: only local
- [2019-02-11 08:49:59.388] AAAA_QUERY_ANALYSIS: Show AAAA queries
- [2019-02-11 08:49:59.388] MAXDBDAYS: max age for stored queries is 365 days
- [2019-02-11 08:49:59.388] RESOLVE_IPV6: Resolve IPv6 addresses
- [2019-02-11 08:49:59.388] RESOLVE_IPV4: Resolve IPv4 addresses
- [2019-02-11 08:49:59.388] DBINTERVAL: saving to DB file every minute
- [2019-02-11 08:49:59.388] DBFILE: Using /etc/pihole/pihole-FTL.db
- [2019-02-11 08:49:59.388] MAXLOGAGE: Importing up to 24.0 hours of log data
- [2019-02-11 08:49:59.388] PRIVACYLEVEL: Set to 0
- [2019-02-11 08:49:59.388] IGNORE_LOCALHOST: Show queries from localhost
- [2019-02-11 08:49:59.388] BLOCKINGMODE: Null IPs for blocked domains
- [2019-02-11 08:49:59.388] REGEX_DEBUGMODE: Inactive
- [2019-02-11 08:49:59.388] ANALYZE_ONLY_A_AND_AAAA: Disabled. Analyzing all queries
- [2019-02-11 08:49:59.388] DBIMPORT: Importing history from database
- -----tail of pihole-FTL.log------
- [2019-02-11 09:21:59.198] Resizing "/FTL-queries" from 2949120 to 3244032
- [2019-02-11 09:21:59.208] Resizing "/FTL-queries" from 3244032 to 3538944
- [2019-02-11 09:21:59.218] Resizing "/FTL-queries" from 3538944 to 3833856
- [2019-02-11 09:21:59.227] Resizing "/FTL-queries" from 3833856 to 4128768
- [2019-02-11 09:21:59.237] Resizing "/FTL-queries" from 4128768 to 4423680
- [2019-02-11 09:21:59.247] Resizing "/FTL-queries" from 4423680 to 4718592
- [2019-02-11 09:21:59.257] Resizing "/FTL-queries" from 4718592 to 5013504
- [2019-02-11 09:21:59.266] Resizing "/FTL-queries" from 5013504 to 5308416
- [2019-02-11 09:21:59.276] Resizing "/FTL-queries" from 5308416 to 5603328
- [2019-02-11 09:21:59.278] Imported 74395 queries from the long-term database
- [2019-02-11 09:21:59.278] -> Total DNS queries: 74395
- [2019-02-11 09:21:59.278] -> Cached DNS queries: 108
- [2019-02-11 09:21:59.278] -> Forwarded DNS queries: 96
- [2019-02-11 09:21:59.278] -> Exactly blocked DNS queries: 11
- [2019-02-11 09:21:59.279] -> Unknown DNS queries: 74180
- [2019-02-11 09:21:59.279] -> Unique domains: 100
- [2019-02-11 09:21:59.279] -> Unique clients: 6
- [2019-02-11 09:21:59.279] -> Known forward destinations: 1
- [2019-02-11 09:21:59.279] Successfully accessed setupVars.conf
- [2019-02-11 09:21:59.283] PID of FTL process: 4896
- [2019-02-11 09:21:59.283] Listening on port 4711 for incoming IPv4 telnet connections
- [2019-02-11 09:21:59.283] Listening on port 4711 for incoming IPv6 telnet connections
- [2019-02-11 09:21:59.283] Listening on Unix socket
- [2019-02-11 09:21:59.284] INFO: No whitelist file found
- [2019-02-11 09:21:59.284] Compiled 0 Regex filters and 0 whitelisted domains in 0.1 msec (0 errors)
- [2019-02-11 09:22:00.240] /etc/pihole/gravity.list: parsed 112857 domains (took 954.9 ms)
- [2019-02-11 09:22:07.847] New forward server: 127.0.0.1 (1/4096)
- [2019-02-11 09:25:10.962] Resizing "/FTL-strings" from 4096 to 8192
- [2019-02-11 10:07:51.665] Resizing "/FTL-strings" from 8192 to 12288
- [2019-02-11 10:28:41.535] INFO: No whitelist file found
- [2019-02-11 10:28:41.535] Compiled 0 Regex filters and 0 whitelisted domains in 0.4 msec (0 errors)
- [2019-02-11 10:28:41.673] /etc/pihole/gravity.list: parsed 0 domains (took 0.1 ms)
- [2019-02-11 10:29:13.377] INFO: No whitelist file found
- [2019-02-11 10:29:13.377] Compiled 0 Regex filters and 0 whitelisted domains in 0.3 msec (0 errors)
- [2019-02-11 10:29:13.880] /etc/pihole/gravity.list: parsed 112857 domains (took 501.9 ms)
- *** [ DIAGNOSING ]: contents of /dev/shm
- -rw------- 1 pihole pihole 16384 Feb 11 09:22 /dev/shm/FTL-client-0
- -rw------- 1 pihole pihole 16384 Feb 11 09:21 /dev/shm/FTL-client-1
- -rw------- 1 pihole pihole 16384 Feb 11 09:21 /dev/shm/FTL-client-2
- -rw------- 1 pihole pihole 16384 Feb 11 09:21 /dev/shm/FTL-client-3
- -rw------- 1 pihole pihole 16384 Feb 11 09:21 /dev/shm/FTL-client-4
- -rw------- 1 pihole pihole 16384 Feb 11 09:22 /dev/shm/FTL-client-5
- -rw------- 1 pihole pihole 163840 Feb 11 09:21 /dev/shm/FTL-clients
- -rw------- 1 pihole pihole 112 Feb 11 09:21 /dev/shm/FTL-counters
- -rw------- 1 pihole pihole 131072 Feb 11 10:37 /dev/shm/FTL-domains
- -rw------- 1 pihole pihole 163840 Feb 11 09:21 /dev/shm/FTL-forwarded
- -rw------- 1 pihole pihole 48 Feb 11 09:22 /dev/shm/FTL-lock
- -rw------- 1 pihole pihole 262144 Feb 11 09:21 /dev/shm/FTL-overTime
- -rw------- 1 pihole pihole 5603328 Feb 11 09:59 /dev/shm/FTL-queries
- -rw------- 1 pihole pihole 12288 Feb 11 10:07 /dev/shm/FTL-strings
- *** [ DIAGNOSING ]: Locale
- LANG=en_US.UTF-8
- *** [ DIAGNOSING ]: Pi-hole log
- -rw-r--r-- 1 pihole pihole 6395383 Feb 11 10:56 /var/log/pihole.log
- -----head of pihole.log------
- Feb 11 00:00:14 dnsmasq[1119]: query[A] ntp.ubuntu.com from 127.0.0.1
- Feb 11 00:00:14 dnsmasq[1119]: config error is REFUSED
- Feb 11 00:00:14 dnsmasq[1119]: query[AAAA] ntp.ubuntu.com from 127.0.0.1
- Feb 11 00:00:14 dnsmasq[1119]: config error is REFUSED
- Feb 11 00:00:14 dnsmasq[1119]: query[A] ntp.ubuntu.com from 127.0.0.1
- Feb 11 00:00:14 dnsmasq[1119]: config error is REFUSED
- Feb 11 00:00:14 dnsmasq[1119]: query[AAAA] ntp.ubuntu.com from 127.0.0.1
- Feb 11 00:00:14 dnsmasq[1119]: config error is REFUSED
- Feb 11 00:00:14 dnsmasq[1119]: query[A] ntp.ubuntu.com from 127.0.0.1
- Feb 11 00:00:14 dnsmasq[1119]: config error is REFUSED
- Feb 11 00:00:14 dnsmasq[1119]: query[AAAA] ntp.ubuntu.com from 127.0.0.1
- Feb 11 00:00:14 dnsmasq[1119]: config error is REFUSED
- Feb 11 00:00:14 dnsmasq[1119]: query[A] ntp.ubuntu.com from 127.0.0.1
- Feb 11 00:00:14 dnsmasq[1119]: config error is REFUSED
- Feb 11 00:00:14 dnsmasq[1119]: query[AAAA] ntp.ubuntu.com from 127.0.0.1
- Feb 11 00:00:14 dnsmasq[1119]: config error is REFUSED
- Feb 11 00:00:14 dnsmasq[1119]: query[A] ntp.ubuntu.com from 127.0.0.1
- Feb 11 00:00:14 dnsmasq[1119]: config error is REFUSED
- Feb 11 00:00:14 dnsmasq[1119]: query[AAAA] ntp.ubuntu.com from 127.0.0.1
- Feb 11 00:00:14 dnsmasq[1119]: config error is REFUSED
- ********************************************
- ********************************************
- [✓] ** 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: zwg6bpc1ic
- ***********************************
- ***********************************
- * 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
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement