Blacklist problem

Hi there, I am contacting you because I have a problem with my PI-Hole. As you can see from the screenshots, I have all counter at zero, but the one indicating the requests. I have installed pi-hole again but the problem is still there. I am waiting for your support. Thank you in advance. Regards,
Francesco

hi,

go to the left in tools, update list and click update list. this should load the blocklist.

you can also rn the command

pihole -d
from the command line.

make sure to reboot your pi after that

Good morning, thank you very much for your reply.
I have performed both suggested commands, but the problem remains.
Attached you can find the log file generated by pi-hole.
Thanks again

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-03-09:08:31:09 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-ge48aa29

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

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

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

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

*** [ DIAGNOSING ]: Operating system
[✓] Ubuntu 17.10

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

*** [ DIAGNOSING ]: Processor
[i] x86_64

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

[✓] IPv6 address(es) bound to the ens32 interface:
fe80::efc8:d227:c11d:ac47 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.1.3

  • Pinging 192.168.1.3...
    [✓] Gateway responded.

*** [ DIAGNOSING ]: Ports in use
is in use by
is in use by
[5355] is in use by systemd-r
[53] is in use by dnsmasq
[80] is in use by lighttpd
[4711] is in use by pihole-FTL
[631] is in use by cupsd

*** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
[✗] Failed to resolve via localhost (127.0.0.1)
[✗] Failed to resolve via Pi-hole (192.168.1.7)
[✓] doubleclick.com is 216.58.205.110 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=true
PIHOLE_INTERFACE=ens32
IPV4_ADDRESS=192.168.1.7/24
IPV6_ADDRESS=
PIHOLE_DNS_1=8.8.8.8
PIHOLE_DNS_2=8.8.4.4
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 0 mar 9 08:15 /etc/pihole/gravity.list
-----head of gravity.list------

-----tail of gravity.list------

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

-rw-r--r-- 1 root root 1290 mar 6 14:47 /etc/pihole/adlists.list
http://dsi.ut-capitole.fr/blacklists/download/ads.tar.gz
http://dsi.ut-capitole.fr/blacklists/download/adult.tar.gz
http://dsi.ut-capitole.fr/blacklists/download/bitcoin.tar.gz
http://dsi.ut-capitole.fr/blacklists/download/child.tar.gz
http://dsi.ut-capitole.fr/blacklists/download/cryptojacking.tar.gz
http://dsi.ut-capitole.fr/blacklists/download/ddos.tar.gz
http://dsi.ut-capitole.fr/blacklists/download/malware.tar.gz
http://dsi.ut-capitole.fr/blacklists/download/manga.tar.gz
http://dsi.ut-capitole.fr/blacklists/download/phishing.tar.gz
http://dsi.ut-capitole.fr/blacklists/download/porn.tar.gz
http://dsi.ut-capitole.fr/blacklists/download/sexual_education.tar.gz
https://raw.githubusercontent.com/ZeroDot1/CoinBlockerLists/master/hosts
https://raw.githubusercontent.com/chadmayfield/pihole-blocklists/master/lists/pi_blocklist_porn_all.list
https://raw.githubusercontent.com/hoshsadiq/adblock-nocoin-list/master/nocoin.txt
https://raw.githubusercontent.com/chadmayfield/pihole-blocklists/master/lists/pi_blocklist_porn_top1m.list

-rw-r--r-- 1 root root 37 mar 9 08:15 /etc/pihole/local.list
192.168.1.7 DNS1
192.168.1.7 pi.hole

-rw-r--r-- 1 root root 238 mar 8 17:09 /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
}

-rw-r--r-- 1 root root 45 mar 6 14:49 /etc/pihole/whitelist.txt
dsi.ut-capitole.fr
raw.githubusercontent.com

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

-rw-r--r-- 1 root root 1722 mar 8 17:09 /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=8.8.8.8
server=8.8.4.4
domain-needed
bogus-priv
dnssec
trust-anchor=.,19036,8,2,49AAC11D7B6F6446702E54A1607371607A1A41855200FD2CE1CDDE32F24E8FB5
trust-anchor=.,20326,8,2,E06D44B80B8F1D39A95C0B0D7C65D08458E880409BBC683457104237C7F8EC8D
interface=ens32

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

-rw-r--r-- 1 root root 3027 mar 8 17:09 /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 1495 mar 8 17:09 /etc/cron.d/pihole
13 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
7 16 * * * 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 654 mar 9 08:30 /var/log/lighttpd/error.log
2018-03-06 14:23:40: (log.c.217) server started
2018-03-06 14:24:02: (server.c.1828) server stopped by UID = 0 PID = 1
2018-03-06 14:24:02: (log.c.217) server started
2018-03-06 14:45:09: (server.c.1828) server stopped by UID = 0 PID = 1
2018-03-06 14:46:03: (log.c.217) server started
2018-03-08 17:03:09: (server.c.1828) server stopped by UID = 0 PID = 1
2018-03-08 17:03:40: (log.c.217) server started
2018-03-08 17:09:12: (server.c.1828) server stopped by UID = 0 PID = 1
2018-03-08 17:09:31: (log.c.217) server started
2018-03-09 08:29:39: (server.c.1828) server stopped by UID = 0 PID = 1
2018-03-09 08:30:12: (log.c.217) server started

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

-rw-r--r-- 1 pihole pihole 7750 mar 9 08:30 /var/log/pihole-FTL.log
[2018-03-09 00:00:15.156] New client: 192.168.1.3 gateway (1/10)
[2018-03-09 00:00:15.194] New forward server: 8.8.8.8 google-public-dns-a.google.com (1/4)
[2018-03-09 00:00:15.199] New client: 127.0.0.1 localhost (2/10)
[2018-03-09 00:00:15.247] Notice: Increasing domains struct size from 1000 to 2000 (536.30 KB)
[2018-03-09 00:00:15.340] Notice: Increasing queries struct size from 10000 to 20000 (997.74 KB)
[2018-03-09 00:00:15.358] Notice: Increasing domains struct size from 2000 to 3000 (1.03 MB)
[2018-03-09 00:00:15.536] Notice: Increasing domains struct size from 3000 to 4000 (1.09 MB)
[2018-03-09 00:00:15.544] Notice: Increasing queries struct size from 20000 to 30000 (1.53 MB)
[2018-03-09 00:00:15.701] Notice: Increasing domains struct size from 4000 to 5000 (1.58 MB)
[2018-03-09 00:00:15.782] Notice: Increasing queries struct size from 30000 to 40000 (2.03 MB)
[2018-03-09 00:00:15.998] Notice: Increasing domains struct size from 5000 to 6000 (2.08 MB)
[2018-03-09 00:00:16.211] Notice: Increasing queries struct size from 40000 to 50000 (2.52 MB)
[2018-03-09 00:00:16.435] Notice: Increasing domains struct size from 6000 to 7000 (2.57 MB)
[2018-03-09 00:00:16.566] Notice: Increasing queries struct size from 50000 to 60000 (3.02 MB)
[2018-03-09 00:00:16.786] Notice: Increasing domains struct size from 7000 to 8000 (3.06 MB)
[2018-03-09 00:00:16.893] Notice: Increasing queries struct size from 60000 to 70000 (3.51 MB)
[2018-03-09 00:00:16.920] Notice: Increasing overTime struct size from 100 to 200 (3.51 MB)
[2018-03-09 00:00:17.243] Notice: Increasing queries struct size from 70000 to 80000 (3.97 MB)
[2018-03-09 00:00:17.269] Imported 71742 queries from the long-term database
[2018-03-09 00:00:17.270] Reading from /var/log/pihole.log (rw-r--r--)
[2018-03-09 08:14:19.727] Notice: Increasing domains struct size from 8000 to 9000 (4.01 MB)
[2018-03-09 08:15:38.908] NOTICE: Received signal SIGHUP - re-reading gravity files
[2018-03-09 08:15:38.919] Gravity list entries: 0
[2018-03-09 08:15:38.919] No blacklist present
[2018-03-09 08:15:38.919] No wildcard blocking list present

*** [ DIAGNOSING ]: Pi-hole log
-rw-r--r-- 1 dnsmasq root 5385330 mar 9 08:31 /var/log/pihole.log
-----head of pihole.log------
Mar 9 00:01:02 dnsmasq[1949]: 20387 192.168.1.5/60955 query[A] 06737290a042d3c392516af6899699d9da125821.idtcsd.net from 192.168.1.5
Mar 9 00:01:02 dnsmasq[1949]: 20387 192.168.1.5/60955 forwarded 06737290a042d3c392516af6899699d9da125821.idtcsd.net to 8.8.4.4
Mar 9 00:01:02 dnsmasq[1949]: 20387 192.168.1.5/60955 forwarded 06737290a042d3c392516af6899699d9da125821.idtcsd.net to 8.8.8.8
Mar 9 00:01:02 dnsmasq[1949]: 20387 192.168.1.5/60955 validation result is INSECURE
Mar 9 00:01:02 dnsmasq[1949]: 20387 192.168.1.5/60955 reply 06737290a042d3c392516af6899699d9da125821.idtcsd.net is 54.228.205.96
Mar 9 00:01:02 dnsmasq[1949]: 20387 192.168.1.5/60955 reply 06737290a042d3c392516af6899699d9da125821.idtcsd.net is 54.228.205.188
Mar 9 00:01:02 dnsmasq[1949]: 20388 192.168.1.3/30074 query[PTR] 188.1.168.192.in-addr.arpa from 192.168.1.3
Mar 9 00:01:02 dnsmasq[1949]: 20388 192.168.1.3/30074 config 192.168.1.188 is NXDOMAIN
Mar 9 00:01:02 dnsmasq[1949]: 20389 192.168.1.3/30074 query[A] gateway.weather.oregonscientific.com from 192.168.1.3
Mar 9 00:01:02 dnsmasq[1949]: 20389 192.168.1.3/30074 cached gateway.weather.oregonscientific.com is
Mar 9 00:01:02 dnsmasq[1949]: 20389 192.168.1.3/30074 cached 06737290a042d3c392516af6899699d9da125821.idtcsd.net is 54.228.205.188
Mar 9 00:01:02 dnsmasq[1949]: 20389 192.168.1.3/30074 cached 06737290a042d3c392516af6899699d9da125821.idtcsd.net is 54.228.205.96
Mar 9 00:01:02 dnsmasq[1949]: 20390 192.168.1.3/30074 query[AAAA] gateway.weather.oregonscientific.com from 192.168.1.3
Mar 9 00:01:02 dnsmasq[1949]: 20390 192.168.1.3/30074 cached gateway.weather.oregonscientific.com is
Mar 9 00:01:02 dnsmasq[1949]: 20390 192.168.1.3/30074 cached 06737290a042d3c392516af6899699d9da125821.idtcsd.net is NODATA-IPv6
Mar 9 00:01:02 dnsmasq[1949]: 20391 192.168.1.3/11349 query[A] wildcard-talkgadget.l.google.com from 192.168.1.3
Mar 9 00:01:02 dnsmasq[1949]: 20391 192.168.1.3/11349 forwarded wildcard-talkgadget.l.google.com to 8.8.8.8
Mar 9 00:01:02 dnsmasq[1949]: 20392 192.168.1.5/60124 query[A] wildcard-talkgadget.l.google.com from 192.168.1.5
Mar 9 00:01:02 dnsmasq[1949]: 20392 192.168.1.5/60124 forwarded wildcard-talkgadget.l.google.com to 8.8.8.8
Mar 9 00:01:02 dnsmasq[1949]: 20393 192.168.1.3/46543 query[A] wildcard-talkgadget.l.google.com from 192.168.1.3

I found the problem.
The lists provided by dsi.ut-capitole.fr/blacklists are not accepted by pihole because they are archives. I replaced them with others in * .txt and * .list format and now everything is ok.
Thank you

1 Like

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