Display of blocked domains is 0

[Mcat12]

Are you on the latest version of Pi-hole? Since v4.0, gravity.list has just been a list of domains.

[allan_marcus]

Using 4.1, but I see an update is available. Will update now

[allan_marcus]

Pi-hole Version v4.1.1 Web Interface Version v4.1.1 FTL Version vDev (master, vDev-d42bcb7)

I see the legends for the donut charts are fixed! Well done.

The "Domains on Blacklist" still show 0.

[jfb]

Your FTL is still on dev. Run this to get the master branch

pihole checkout ftl master

What is the output of:

echo ">stats" | nc localhost 4711

[allan_marcus]

Thanks. Ran pihole checkout ftl master and version is this:

Pi-hole Version v4.1.1 Web Interface Version v4.1.1 FTL Version vDev (master, vDev-b06eedf)

echo ">stats" | nc localhost 4711

domains_being_blocked 0
dns_queries_today 31767
ads_blocked_today 1665
ads_percentage_today 5.241288
unique_domains 2069
queries_forwarded 10581
queries_cached 19521
clients_ever_seen 3
unique_clients 3
dns_queries_all_types 31767
reply_NODATA 18
reply_NXDOMAIN 2
reply_CNAME 19
reply_IP 60
privacy_level 0
status disabled

[jfb]

The "domains being blocked 0" indicates your gravity list is currently empty. Since there were ads blocked in the past 24 hours, this happened in the last 24 hours. Let's try a few things (easiest first).

pihole -r and select "repair"

[allan_marcus]

done. no change.

If it matters:

wc -l /etc/pihole/gravity.list

136336 /etc/pihole/gravity.list

So the list doesn't appear to be empty, assume that is the list

[jfb]

That is the list and it's not empty, but Pi-Hole thinks it's empty (or isn't reading it).

move that gravity list to gravity.list.old, then run pihole -g -f

[jfb]

And upload a debug log and post the token.

[allan_marcus]

idysyqxhfe

[jfb]

Looking at your debug log, your Pi-Hole is blocking domains from your gravity list, so Pi-Hole is reading gravity properly. The problem appears to be in the mismatch between your admin LTE version and your FTL version and the web interface not pulling the data from FTL. You are on an older version of the dev branch (pre- FTLDNS, I think). So, I think the solution is to get FTL onto the current master.

[SOLVED] - PiHole 4.0 4.1 - Question(s)

Hello, I have a hard coded version of pihole still running on my Raspberry Pi. I see that PiHole 4.0 is released. Does this mean everything is back up and running from previous instances where Dnsmasq was not working well. I feel like I need to do a fresh install on a fresh SD card as I am not sure if my current version will update properly with the update command. Can anyone assist, it has been a little bit since I have touched pihole Current info Pi-hole Version vDev (HEAD, v3.2.1-0-ge60…

[allan_marcus]

OK. how. When I try
pihole -up
I get
Unable to complete update, please contact Pi-hole Support

so then I tried this:
pihole checkout master

And then this
pihole checkout ftl master

[jfb]

Please try the following steps

1. sudo nano /etc/resolv.conf
2. edit 127.0.0.1 to 9.9.9.9 or your preferred third party DNS service
3. save
4. Re-run pihole -up

[allan_marcus]

cat /etc/resolv.conf
Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 8.8.8.8
root@linuxserver:/var/log# pihole -up
[i] Checking for updates...
[i] Pi-hole Core: up to date
[i] FTL: update available

[i] FTL out of date

[i] FTL Checks...

[i] Downloading and Installing FTL...curl: (22) The requested URL returned error: 404 Not Found
[✗] Downloading and Installing FTL
Error: URL https://github.com/pi-hole/FTL/releases/download/v4.1.2/ not found

[allan_marcus]

BTW, if it matters,
Linux linuxserver 3.13.0-147-generic #196-Ubuntu SMP Wed May 2 15:51:34 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

[jfb]

Your version of Ubuntu (14.04.5) is unsupported and this may be causing the problem. Have you considered updating to one of the supported versions of Ubuntu (16.04 / 16.10)?

[allan_marcus]

Ah, yes. Updating it is on my list, but since it's working (until now : - ), I didn't see a need to update. Maybe this is the impetus. thanks for your help.

[bombz]

You can also review my topic which was solved coming from an OLD dev build and updated to current master revision

[SOLVED] - PiHole 4.0 4.1 - Question(s)

Starting with V4 of Pi-Hole, dnsmasq is embedded in pihole-FTL and dnsmasq does not run as a separate process.

Feel free to post back how you make out

P.S. I just updated to the current version today as well with pihole -up
It took a moment for DNS to kick in once I rebooted the Pi, I hope you have success

Pi-hole Version v4.1.1 Web Interface Version v4.1.1 FTL Version v4.1.2

[allan_marcus]

UP graded to 16.04 last night. Still working out a few kinks in various programs, but everything seems to be working OK. Pihole is working as expected.

It would be night to have some sort of warning on install or run time about using an unsupported OS.