just updated , only blocklist in web interface stays on 0 seems like web interface problem ... still blocking , anybode with the same issue
same problem here
How to role back this module?
@michaelamsterdam @MaDa please run
pihole -up
pihole -g
and have a look if this fixes your problems.
If it doesn't help, please provide the exact commands you used for checking out first FTLDNS and now this branch.
thank you. the issue is fixed.
I am seeing issues with pihole NOT blocking after doing a pihole -up and pihole -g this morning. I am on the FTLDNS branch only and did not explicitly pull in the regex branch. The dashboard graphs shows no blocks as well empirical evidence of going to a known blocked site and seeing it.
My log contains lines like:
Apr 25 06:42:20 dnsmasq[9890]: bad address at /etc/pihole/gravity.list line 1
Apr 25 06:42:20 dnsmasq[9890]: bad address at /etc/pihole/gravity.list line 2
Apr 25 06:42:20 dnsmasq[9890]: bad address at /etc/pihole/gravity.list line 3
Apr 25 06:42:20 dnsmasq[9890]: bad address at /etc/pihole/gravity.list line 4
Apr 25 06:42:20 dnsmasq[9890]: bad address at /etc/pihole/gravity.list line 5
...
while processing gravity.list.
No changes were made to config prior to or after doing the update. I ran a debug and the token is: vrj2lsdo9o
Please try a
sudo service pihole-FTL restart
Also, what is the output of
head /etc/pihole/gravity.list
?
I have restarted a few times, even rebooted the pi. My gravity file looks 'good'. With output:
pi@gyre:/etc/pihole $ head gravity.list
-rotation.de
-sso.anbtr.com
-traffic.com
0--foodwarez.da.ru
0-0-0-0-0-0proxy.tserv.se
0-0-0.6te.net
0-168.com
0-29.com
0-2u.com
0-day.us
pi@gyre:/etc/pihole $ wc -l gravity.list
566172 gravity.list
Previously (before today's update), my log file only had a couple of these while parsing gravity.list:
Apr 24 17:09:40 dnsmasq[610]: bad name at /etc/pihole/gravity.list line 99089
Apr 24 17:09:43 dnsmasq[610]: bad name at /etc/pihole/gravity.list line 474383
After the update, nearly all of the entries in gravity.list are like:
Apr 25 09:04:33 dnsmasq[663]: bad address at /etc/pihole/gravity.list line 443827
Apr 25 09:04:33 dnsmasq[663]: bad address at /etc/pihole/gravity.list line 443828
Apr 25 09:04:33 dnsmasq[663]: bad address at /etc/pihole/gravity.list line 443829
Apr 25 09:04:33 dnsmasq[663]: bad address at /etc/pihole/gravity.list line 443830
The message has changed from bad name to bad address.
Hmm, are you still running dnsmasq as your DNS server? Note that it should have been replaced by the most recent version of pihole-FTL which also provides DNS services.
I am not:
pi@gyre:~ $ systemctl status dnsmasq
● dnsmasq.service - dnsmasq - A lightweight DHCP and caching DNS server
Loaded: loaded (/lib/systemd/system/dnsmasq.service; disabled; vendor preset: enabled)
Active: inactive (dead)
The only update I saw this morning was to pihole-core. There was no incoming change to pihole-FTL. It does seem like the custom FTL dnsmasq is having issue with the gravity.list format, based on the log messages.
"bad address" issue reproduced early this AM as well. Upgrade path:
- v3.3.1
- FTLDNS per the blog post
- ftl new/regex per the blog post
Gravity list looks a lot like @tomporter518's.
Tried pihole -g --force but no dice. Had to get to work, so I didn't get to spend time troubleshooting further.
Yeah, I agree. Could you, just out of curiosity check if there are any spaces or tabs in the first line of your gravity file?
Like
-rotation.de_
where _ is symbolic for a space?
Could you try to put in another simple domain like
doesanyhownotexist.com
into the very first line of gravity.list and restart pihole-FTL? Please ensure that there are no spaces/tabs here, too.
Also could you run
tail -n 100 /var/log/pihole-FTL.log | pihole tricorder
and give me the provided token?
Would be cool if you could show us the exact first lines of your gravity.list as well. Also if there is any space or tab (if so, try removing it or put in another first line like I suggested above).
@DL6ER lol Sorry man you're right. I should have done that this AM. 
I will perform the upgrade again today when I'm done with work, try to reproduce again, provide more details.
There does not appear to be any whitespace on/in the gravity.list lines. I added the above 'fake' (I think) domain as the first line my gravity.list and restarted pihole-FTL.
I first hit vidzi.tv, which I know should be blocked but was not. It's token is: 2g0b21wrnp
Then I used doesanyhownotexist.com, which gave me a not found. It's token is: hoja8byp9v
No spaces or tabs; and, it seems to happen as soon as I switch to the FTLDNS branch:
Pi-hole Version v3.3.1 Web Interface Version v3.3 FTL Version v3.0:
chipster@Pi-Hole:/etc/pihole $ head gravity.list
192.168.1.9 -rotation.de
192.168.1.9 -sso.anbtr.com
192.168.1.9 -traffic.com
192.168.1.9 0--foodwarez.da.ru
192.168.1.9 0-0-0-0-0-0-0-0-0-0-0-0-0-18-0-0-0-0-0-0-0-0-0-0-0-0-0.info
192.168.1.9 0-0-0-0-0-0-0-0-0-0-0-0-0-33-0-0-0-0-0-0-0-0-0-0-0-0-0.info
192.168.1.9 0-0-0-0-0-0proxy.tserv.se
192.168.1.9 0-0-0.6te.net
192.168.1.9 0-168.com
192.168.1.9 0-29.com
------------------------
echo "FTLDNS" | sudo tee /etc/pihole/ftlbranch
pihole checkout core FTLDNS
pihole checkout web FTLDNS
Pi-hole Version vDev (FTLDNS, v3.3-130-g2e6a937) Web Interface Version v3.3 FTL Version vDev (FTLDNS, vDev-3656ba2)
chipster@Pi-Hole:/etc/pihole $ head gravity.list
-rotation.de
-sso.anbtr.com
-traffic.com
0--foodwarez.da.ru
0-0-0-0-0-0-0-0-0-0-0-0-0-18-0-0-0-0-0-0-0-0-0-0-0-0-0.info
0-0-0-0-0-0-0-0-0-0-0-0-0-33-0-0-0-0-0-0-0-0-0-0-0-0-0.info
0-0-0-0-0-0proxy.tserv.se
0-0-0.6te.net
0-168.com
0-29.com
Debug token: x7adas9odw
Ah, thanks. From your debug logs, I see that the FTLDNS branch is not up-to-date. It is missing support for our new simple domain format. However, the regex branch will be fine if you try that one.
@PromoFaux if you get a chance... on the FTL repo, there is nothing else in development, so a merge development -> FTLDNS seems most obvious here.
https://github.com/pi-hole/FTL/pull/261
@tomporter518 @Chipster please run pihole -up and try again
Worked like a charm! Thanks! 
1 Like
I thought there might be a missing merge or commit. I'm up and pi-holing again.
1 Like
This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.