Expected Behaviour:
Pi-hole to be blocking ads.
Actual Behaviour:
Not blocking ads, web server shows very little ads being blocking despite a domains on adlist number to be over 127,000. I have searched the forum for other topics related to this behavior and none of the remedies seems to fix my issue but I will be glad to troubleshoot from the beginning and move on from there.
Debug Token:
You will have to forgive me as I am a very novice user of this system. How do I do the debug token? When I do the command in pihole it spits out a ton of information and I didn't want to inundate the post with a ton of information.
Did you add the Steven Black ad list in the installation wizard?
from pihole you can run pihole -d or go from the gui go to `tools>generate debug log' you need only post the token that is generated.
When I try to create debug token I get this message:
[✗] 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/pihole_debug.log
From the pihole you could try pihole -r and choose repair. See if that resolves the issue.
I did the command you told to me to and eventually got this error:
[✗] Retrieval of supported OS list failed. dig failed with return code 10.
-
Unable to determine if the detected OS (Raspbian 11) is supported*
-
Possible causes for this include:*
-
- Firewall blocking certain DNS lookups from Pi-hole device*
-
- ns1.pi-hole.net being blocked (required to obtain TXT record from versions.pi-hole.net containing supported operating systems)*
-
- Other internet connectivity issues*
I know my pihole has does not have connection issues so I did the command listed:
sudo PIHOLE_SKIP_OS_CHECK=true pihole -r
And that worked until I got this error:
[✗] Downloading and Installing FTL
It looks like the device on which you're running Pihole doesn't have network connectivity, or something along those lines.
If you go to a command prompt on the device running Pihole and run these commands:
ping cloudflare.com
ping 1.1.1.1
What are the results of each?
Here are my results.
For ping cloudflare command I get:
ping: cloudflare.com: Temporary failure in name resolution
For ping 1.1.1.1 command I get:
PING 1.1.1.1 (1.1.1.1) 56(84) bytes of data.
Are you running it on a raspberry pi? and if so is it a zero?
That is correct, it is on a Raspberry Pi Zero W.
What OS / version are you running. You can run / post the following command from the pihole and also, is it a pizerow or pizerow2?
cat /etc/os-release
After running that command I get this:
PRETTY_NAME="Raspbian GNU/Linux 11 (bullseye)"
NAME="Raspbian GNU/Linux"
VERSION_ID="11"
VERSION="11 (bullseye)"
VERSION_CODENAME=bullseye
ID=raspbian
ID_LIKE=debian
HOME_URL="http://www.raspbian.org/"
SUPPORT_URL="RaspbianForums - Raspbian"
BUG_REPORT_URL="RaspbianBugs - Raspbian"
And it is running on the Pi Zero W.
That a full release behind but is certainly a supported OS so not sure why that unsupported OS error. Is this a fresh OS install?
You may want to try a fresh from scratch install using
https://downloads.raspberrypi.com/raspios_lite_armhf/images/raspios_lite_armhf-2024-03-15/2024-03-15-raspios-bookworm-armhf-lite.img.xz
Thats the 32 bit version of Raspbian Bookworm. There are some differences between the two ( Bullsesye uses dhcpv5 while Bookworm uses netmanager ).
Another possiblity is that your SD card has issues and maybe the install of Pihole or the OS got corrupted?
I have been suspected that maybe my SD card has been going bad. And when I did the fresh install I do remember choosing the 32 bit version.
I will see if I can get another sd card and do the install you are suggesting and report back what I find.
I thought the OS check was dependent on a successful DNS lookup of the URL containing the supported OS list, maybe I'm remembering incorrectly.
In any case, you're not going to get far if the script can't resolve DNS lookups, which based on the "ping cloudflare.com" test, you're not doing successfully.
Quoting from Failure dns name resolution and unrecognized service dnsmasq, try the change below:
This will temporarily reset the nameserver on the Pi to bypass Pi-Hole DNS.
sudo nano /etc/resolv.conf
Edit the nameserver line to nameserver 9.9.9.9 or your preferred third party DNS service, save and exit
After that, try the ping cloudflare.com again and see if it's resolving. If so, try the Pihole install script again and share the results.
The issue here is not related to the OS. It's a network issue.
Pi-hole is not able to download the supported OS list and download new files, resulting in errors.
This will temporarily reset the nameserver on the Pi to bypass Pi-Hole DNS.
sudo nano /etc/resolv.conf
Edit the nameserver line to nameserver 9.9.9.9 or your preferred third party DNS service, save and exit
Run
pihole -d
and upload the debug log.
1 Like
Doing this I am still unable to get a debug token, same error as before:
[?] Would you like to upload the log? [y/N] y
* Using curl for transmission.
* curl failed, contact Pi-hole support for assistance.
* Error message: curl: (6) Could not resolve host: tricorder.pi-hole.net
[✗] 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/pihole_debug.log
What if you try:
dig tricorder.pi-hole.net
Can you copy/paste the result here?
If that errors out, you've still got a DNS resolution problem, as Pihole is really not involved in this test at all.
