Please follow the below template, it will help us to help you!
Expected Behaviour:
I've updated this morning to the latest 4.1.1 and I am seeing lots of issues. Everything has been running fine before.
Please note that I am running Cloudflare DoH, is has been confirmed as per here and worked fine up until the upgrade:
Issues I am seeing:
- Status / reply missing in the dashboard fir clients, see the picture
- Unable to resolve correctly, ie:
pi@p1:~ $ cf
ERRO[0001] Update check failed error="Post https://update.equinox.io/check: dial tcp: lookup update.equinox.io on 127.0.0.1:53: server misbehaving"
pi@p1:~ $
pi@p1:~ $ sudo apt-get update
Err:1 http://raspbian.raspberrypi.org/raspbian stretch InRelease
Temporary failure resolving 'raspbian.raspberrypi.org'
Err:2 http://archive.raspberrypi.org/debian stretch InRelease
Temporary failure resolving 'archive.raspberrypi.org'
Reading package lists... Done
W: Failed to fetch http://raspbian.raspberrypi.org/raspbian/dists/stretch/InRelease Temporary failure resolving 'raspbian.raspberrypi.org'
W: Failed to fetch http://archive.raspberrypi.org/debian/dists/stretch/InRelease Temporary failure resolving 'archive.raspberrypi.org'
W: Some index files failed to download. They have been ignored, or old ones used instead.
pi@p1:~ $
[✓] ** 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.
Actual Behaviour:
Debug Token:
I am unable to get one:
[?] Would you like to upload the log? [y/N] y
* Using openssl for transmission.
[✗] 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_debug-sanitized.log
pi@p1:~ $ pihole -d
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-16:12:29:17 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-gde7aa5a3
*** [ DIAGNOSING ]: FTL version
[✓] FTL: v4.1.2 (https://discourse.pi-hole.net/t/how-do-i-update-pi-hole/249)
*** [ DIAGNOSING ]: lighttpd version
[i] 1.4.45
*** [ DIAGNOSING ]: php version
[i] 7.0.30
*** [ DIAGNOSING ]: Operating system
[✓] Raspbian GNU/Linux 9 (stretch)
*** [ DIAGNOSING ]: SELinux
[i] SELinux not detected
*** [ DIAGNOSING ]: Processor
[✓] armv7l
*** [ DIAGNOSING ]: Networking
[✓] IPv4 address(es) bound to the eth0 interface:
10.1.1.2/24 matches the IP found in /etc/pihole/setupVars.conf
[✓] IPv6 address(es) bound to the eth0 interface:
fe80::4faa:21ca:4d08:5142 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: 10.1.1.1
* Pinging 10.1.1.1...
[✓] Gateway responded.
*** [ DIAGNOSING ]: Ports in use
127.0.0.1:42081 cloudflare (IPv4)
127.0.0.1:54 cloudflare (IPv4)
*:22 sshd (IPv4)
*:22 sshd (IPv6)
[*: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
dig: '' is not a legal name (unexpected end of input)
[✗] Failed to resolve via localhost (127.0.0.1)
dig: '' is not a legal name (unexpected end of input)
[✗] Failed to resolve via Pi-hole (10.1.1.2)
[✓] doubleclick.com is 216.58.206.78 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
dig: '' is not a legal name (unexpected end of input)
[✗] Failed to resolve via localhost (::1)
dig: '' is not a legal name (unexpected end of input)
[✗] Failed to resolve via Pi-hole (fd08:2e5:9779:1:b22a:43a0:672d:f6d7)
[✗] Failed to resolve doubleclick.com 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
TEMPERATUREUNIT=C
WEBUIBOXEDLAYOUT=boxed
PIHOLE_INTERFACE=eth0
IPV4_ADDRESS=10.1.1.2/24
IPV6_ADDRESS=fd08:2e5:9779:1:b22a:43a0:672d:f6d7
PIHOLE_DNS_1=
PIHOLE_DNS_2=
QUERY_LOGGING=true
INSTALL_WEB_SERVER=true
INSTALL_WEB_INTERFACE=true
LIGHTTPD_ENABLED=true
BLOCKING_ENABLED=true
*** [ DIAGNOSING ]: Dashboard and block page
[✗] Block page X-Header: X-Header does not match or could not be retrieved.
HTTP/1.1 200 OK
Content-type: text/html; charset=UTF-8
Date: Wed, 16 Jan 2019 12:29:23 GMT
Server: lighttpd/1.4.45
[✓] Web interface X-Header: X-Pi-hole: The Pi-hole Web interface is working!
*** [ DIAGNOSING ]: Gravity list
-rw-r--r-- 1 root root 0 Jan 16 12:20 /etc/pihole/gravity.list
-----head of gravity.list------
-----tail of gravity.list------
*** [ DIAGNOSING ]: contents of /etc/pihole
-rw-r--r-- 1 root root 381 Oct 8 18:47 /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 0 Sep 30 21:31 /etc/pihole/blacklist.txt
-rw-r--r-- 1 root root 112 Jan 16 12:20 /etc/pihole/local.list
10.1.1.2 p1
fd08:2e5:9779:1:b22a:43a0:672d:f6d7 p1
10.1.1.2 pi.hole
fd08:2e5:9779:1:b22a:43a0:672d:f6d7 pi.hole
-rw-r--r-- 1 root root 234 Jan 16 12:13 /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 2027 Jan 8 22:05 /etc/pihole/whitelist.txt
analytics.google.com
analytics.twitter.com
graph.facebook.com
spclient.wg.spotify.com
uk-london.privateinternetaccess.com
privateinternetaccess.com
ocsp.apple.com
pictures.zooplus.com
ssl.microsofttranslator.com
mobile.pipe.aria.microsoft.com
f-log-extension.grammarly.io
settings-win.data.microsoft.com
sls.update.microsoft.com
client.wns.windows.com
audio-fac.spotify.com
metrics.icloud.com
lcprd1.samsungcloudsolution.net
osb.samsungqbe.com
time.samsungcloudsolution.com
cdn.samsungcloudsolution.com
acr0.samsungcloudsolution.com
referrer.disqus.com
platform.linkedin.com
c.disquscdn.com
disqus.com
instagram.com
s.youtube.com
sentry.io
telemetry.malwarebytes.com
e.crashlytics.com
clickserve.dartsearch.net
ad.doubleclick.net
stat.nate.com
cyad1.nate.com
nate.com
ichnaea.netflix.com
graph.instagram.com
stats.appsflyer.com
device-api.urbanairship.com
gurgle.zdbb.net
fastlane.rubiconproject.com
incoming.telemetry.mozilla.org
mcafee12.tt.omtrdc.net
etoro.com
google-analytics.com
googleadservices.com
googletagmanager.com
googletagservices.com
samsungotn.net
f1.media.brightcove.com
metrics.fe.apple-dns.net
stocks-analytics-events.apple.com
js-agent.newrelic.com
ssl.google-analytics.com
bam.nr-data.net
doubleclick.com
www.google-analytics.com
d.xp1.ru4.com
www.googleadservices.com
fls-eu.amazon.com
pagead2.googlesyndication.com
srx.main.ebayrtm.com
pixel.everesttech.net
ssl2anyone3.com
rainydaymarketing.go2affise.com
r.remarketingpixel.com
t.paypal.com
aax-eu.amazon-adsystem.com
googleads.g.doubleclick.net
assets.adobedtm.com
csi.gstatic.com
tracker.affirm.com
adservice.google.com
www.googletagmanager.com
cdn-eu-ec.yottaa.net
try.abtasty.com
dcinfos.abtasty.com
www.dwin1.com
www.upsellit.com
tags.tiqcdn.com
alb.reddit.com
log.olark.com
cdn.optimizely.com
www-google-analytics.l.google.com
profile.localytics.com
analytics.localytics.com
engage1.silverpop.com
reports.crashlytics.com
settings.crashlytics.com
ip-api.com
pro.ip-api.com
api.amplitude.com
app.pendo.io
cdn.ravenjs.com
va.tawk.to
widget.privy.com
*** [ DIAGNOSING ]: contents of /etc/dnsmasq.d
-rw-r--r-- 1 root root 1383 Jan 16 12:14 /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
interface=eth0
*** [ DIAGNOSING ]: contents of /etc/lighttpd
-rw-r--r-- 1 root root 3102 Jan 16 12:13 /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 16 12:13 /etc/cron.d/pihole
25 4 * * 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
57 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 315 Jan 16 12:18 /var/log/lighttpd/error.log
2019-01-13 06:25:02: (server.c.1534) logfiles cycled UID = 0 PID = 1464
2019-01-16 12:14:09: (server.c.1828) server stopped by UID = 0 PID = 1
2019-01-16 12:14:10: (log.c.217) server started
2019-01-16 12:17:48: (server.c.1828) server stopped by UID = 0 PID = 1
2019-01-16 12:18:05: (log.c.217) server started
*** [ DIAGNOSING ]: contents of /var/log
-rw-r--r-- 1 pihole pihole 10022 Jan 16 12:20 /var/log/pihole-FTL.log
-----head of pihole-FTL.log------
[2019-01-16 12:14:22.309] Using log file /var/log/pihole-FTL.log
[2019-01-16 12:14:22.309] ########## FTL started! ##########
[2019-01-16 12:14:22.309] FTL branch: master
[2019-01-16 12:14:22.309] FTL version: v4.1.2
[2019-01-16 12:14:22.309] FTL commit: b06eedf
[2019-01-16 12:14:22.309] FTL date: 2018-12-21 14:43:34 -0600
[2019-01-16 12:14:22.309] FTL user: pihole
[2019-01-16 12:14:22.309] Starting config file parsing (/etc/pihole/pihole-FTL.conf)
[2019-01-16 12:14:22.309] SOCKET_LISTENING: only local
[2019-01-16 12:14:22.310] AAAA_QUERY_ANALYSIS: Show AAAA queries
[2019-01-16 12:14:22.310] MAXDBDAYS: max age for stored queries is 365 days
[2019-01-16 12:14:22.310] RESOLVE_IPV6: Resolve IPv6 addresses
[2019-01-16 12:14:22.310] RESOLVE_IPV4: Resolve IPv4 addresses
[2019-01-16 12:14:22.310] DBINTERVAL: saving to DB file every minute
[2019-01-16 12:14:22.310] DBFILE: Using /etc/pihole/pihole-FTL.db
[2019-01-16 12:14:22.310] MAXLOGAGE: Importing up to 24.0 hours of log data
[2019-01-16 12:14:22.310] PRIVACYLEVEL: Set to 0
[2019-01-16 12:14:22.310] IGNORE_LOCALHOST: Show queries from localhost
[2019-01-16 12:14:22.310] BLOCKINGMODE: Null IPs for blocked domains
[2019-01-16 12:14:22.310] REGEX_DEBUGMODE: Inactive
[2019-01-16 12:14:22.310] ANALYZE_ONLY_A_AND_AAAA: Disabled. Analyzing all queries
[2019-01-16 12:14:22.310] DBIMPORT: Importing history from database
[2019-01-16 12:14:22.310] PIDFILE: Using /var/run/pihole-FTL.pid
[2019-01-16 12:14:22.310] PORTFILE: Using /var/run/pihole-FTL.port
[2019-01-16 12:14:22.310] SOCKETFILE: Using /var/run/pihole/FTL.sock
[2019-01-16 12:14:22.310] WHITELISTFILE: Using /etc/pihole/whitelist.txt
[2019-01-16 12:14:22.310] BLACKLISTFILE: Using /etc/pihole/black.list
[2019-01-16 12:14:22.310] GRAVITYFILE: Using /etc/pihole/gravity.list
[2019-01-16 12:14:22.310] REGEXLISTFILE: Using /etc/pihole/regex.list
[2019-01-16 12:14:22.310] SETUPVARSFILE: Using /etc/pihole/setupVars.conf
[2019-01-16 12:14:22.310] AUDITLISTFILE: Using /etc/pihole/auditlog.list
[2019-01-16 12:14:22.310] Finished config file parsing
[2019-01-16 12:14:22.311] Skipping empty regex filter on line 1
[2019-01-16 12:14:22.311] Compiled 2 Regex filters and 96 whitelisted domains in 0.5 msec (0 errors)
[2019-01-16 12:14:22.312] Database successfully initialized
-----tail of pihole-FTL.log------
[2019-01-16 12:18:09.171] Compiled 2 Regex filters and 96 whitelisted domains in 1.9 msec (0 errors)
[2019-01-16 12:18:09.201] Database successfully initialized
[2019-01-16 12:18:09.220] Notice: Increasing queries struct size from 0 to 10000
[2019-01-16 12:18:09.220] Notice: Increasing domains struct size from 0 to 1000
[2019-01-16 12:18:09.220] Notice: Increasing clients struct size from 0 to 10
[2019-01-16 12:18:09.220] New forward server: 127.0.0.1 (0/0)
[2019-01-16 12:18:09.220] Notice: Increasing forwarded struct size from 0 to 4
[2019-01-16 12:18:09.221] Notice: Increasing overTime struct size from 0 to 100
[2019-01-16 12:18:09.234] Notice: Increasing clients struct size from 10 to 20
[2019-01-16 12:18:09.294] Notice: Increasing domains struct size from 1000 to 2000
[2019-01-16 12:18:09.317] Notice: Increasing queries struct size from 10000 to 20000
[2019-01-16 12:18:09.364] Notice: Increasing overTime struct size from 100 to 200
[2019-01-16 12:18:09.427] Notice: Increasing queries struct size from 20000 to 30000
[2019-01-16 12:18:09.451] Imported 21207 queries from the long-term database
[2019-01-16 12:18:09.452] -> Total DNS queries: 21207
[2019-01-16 12:18:09.452] -> Cached DNS queries: 2133
[2019-01-16 12:18:09.452] -> Forwarded DNS queries: 16688
[2019-01-16 12:18:09.452] -> Exactly blocked DNS queries: 1616
[2019-01-16 12:18:09.452] -> Unknown DNS queries: 770
[2019-01-16 12:18:09.452] -> Unique domains: 1655
[2019-01-16 12:18:09.452] -> Unique clients: 16
[2019-01-16 12:18:09.452] -> Known forward destinations: 1
[2019-01-16 12:18:09.452] Successfully accessed setupVars.conf
[2019-01-16 12:18:09.462] PID of FTL process: 614
[2019-01-16 12:18:09.462] Listening on port 4711 for incoming IPv4 telnet connections
[2019-01-16 12:18:09.462] Listening on port 4711 for incoming IPv6 telnet connections
[2019-01-16 12:18:09.463] Listening on Unix socket
[2019-01-16 12:18:09.466] Skipping empty regex filter on line 1
[2019-01-16 12:18:09.467] Compiled 2 Regex filters and 96 whitelisted domains in 0.6 msec (0 errors)
[2019-01-16 12:18:09.468] /etc/pihole/black.list: parsed 0 domains (took 0.0 ms)
[2019-01-16 12:18:09.468] /etc/pihole/gravity.list: parsed 0 domains (took 0.0 ms)
[2019-01-16 12:20:24.877] Skipping empty regex filter on line 1
[2019-01-16 12:20:24.877] Compiled 2 Regex filters and 96 whitelisted domains in 0.6 msec (0 errors)
[2019-01-16 12:20:24.878] /etc/pihole/black.list: parsed 0 domains (took 0.0 ms)
[2019-01-16 12:20:24.878] /etc/pihole/gravity.list: parsed 0 domains (took 0.0 ms)
*** [ DIAGNOSING ]: Locale
LANG=en_GB.UTF-8
*** [ DIAGNOSING ]: Pi-hole log
-rw-r--r-- 1 pihole pihole 5329260 Jan 16 12:29 /var/log/pihole.log
-----head of pihole.log------
Jan 16 00:00:05 dnsmasq[619]: 443760 10.1.1.40/51787 query[A] plex.tv from 10.1.1.40
Jan 16 00:00:05 dnsmasq[619]: 443760 10.1.1.40/51787 forwarded plex.tv to 127.0.0.1
Jan 16 00:00:05 dnsmasq[619]: 443760 10.1.1.40/51787 reply plex.tv is 63.32.24.1
Jan 16 00:00:05 dnsmasq[619]: 443760 10.1.1.40/51787 reply plex.tv is 63.32.153.75
Jan 16 00:00:05 dnsmasq[619]: 443760 10.1.1.40/51787 reply plex.tv is 52.16.193.193
Jan 16 00:00:05 dnsmasq[619]: 443760 10.1.1.40/51787 reply plex.tv is 52.30.248.117
Jan 16 00:00:05 dnsmasq[619]: 443760 10.1.1.40/51787 reply plex.tv is 54.72.69.247
Jan 16 00:00:05 dnsmasq[619]: 443760 10.1.1.40/51787 reply plex.tv is 54.76.102.118
Jan 16 00:00:05 dnsmasq[619]: 443760 10.1.1.40/51787 reply plex.tv is 54.77.150.142
Jan 16 00:00:05 dnsmasq[619]: 443760 10.1.1.40/51787 reply plex.tv is 54.246.140.185
Jan 16 00:00:16 dnsmasq[619]: 443761 10.1.1.118/52780 query[A] www.privateinternetaccess.com from 10.1.1.118
Jan 16 00:00:16 dnsmasq[619]: 443761 10.1.1.118/52780 forwarded www.privateinternetaccess.com to 127.0.0.1
Jan 16 00:00:16 dnsmasq[619]: 443761 10.1.1.118/52780 reply www.privateinternetaccess.com is <CNAME>
Jan 16 00:00:16 dnsmasq[619]: 443761 10.1.1.118/52780 reply privateinternetaccess.com.edgekey.net is <CNAME>
Jan 16 00:00:16 dnsmasq[619]: 443761 10.1.1.118/52780 reply e14857.ksd.akamaiedge.net is 23.214.161.118
Jan 16 00:00:21 dnsmasq[619]: 443762 10.1.1.118/59614 query[A] api-0.core.keybaseapi.com from 10.1.1.118
Jan 16 00:00:21 dnsmasq[619]: 443762 10.1.1.118/59614 forwarded api-0.core.keybaseapi.com to 127.0.0.1
Jan 16 00:00:21 dnsmasq[619]: 443762 10.1.1.118/59614 reply api-0.core.keybaseapi.com is 52.206.151.214
Jan 16 00:00:21 dnsmasq[619]: 443762 10.1.1.118/59614 reply api-0.core.keybaseapi.com is 52.201.34.133
Jan 16 00:00:25 dnsmasq[619]: 443763 10.1.1.124/64566 query[A] news.iadsdk.apple.com from 10.1.1.124
********************************************
********************************************
[✓] ** 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] y
* Using openssl for transmission.
[✗] 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_debug-sanitized.log
pi@p1:~ $