Compatibility problem with Raspberry Pi 9.4?

Help
1

Please follow the below template, it will help us to help you!

Expected Behaviour:

PiHole properly installing and/or working after installation with terminal (Bash command).

Actual Behaviour:

Unable to access PiHole admin console over network after upgrade to Pi v. 9.4. Attempted to reinstall/reconfigure Raspberry Pi from scratch. I upgraded to version 9.4 first, and PiHole fails installation about midway through. After this, the Raspberry Pi itself is also unable to load web pages.

Debug Token:

Not available because after attempted fresh installation, the terminal doesn't respond to PiHole commands.

2

What exactly is the error you get?

3

Initially, when I tried to update PiHole after doing a sudo upgrade of the Pi firmware, the PiHole install screen said "unable to install, detected kernel upgrade." PiHole still seemed to be doing its job on the network, but I couldn't access the admin console from my web browser on my main computer.

Flash forward now to a fully wiped fresh Raspberry Pi.

Now when I try to do a fresh install of PiHole with the fully upgraded firmware (after a reboot), the install just quits midway into it. After which, all internet connectivity seems to just break.

4

Can you ping/resolve a host after the Internet connectivity doesn't work ?

If not, edit /etc/resolv.conf from 127.0.0.1 to a known DNS like google's 8.8.8.8, see if that restores connectivity.

When the installer quits, does it output any error or is the same Kernel Upgrade one?

Can you post an exact message?

5

Yes, I can ping Google from the command line. But I can't reach google.com from the web browser.

So it appears to be a DNS resolving issue, maybe? My description of "internet connectivity broken" might have been slightly exaggerated.

6

See if you can use the IP that the ping command resolves for google.com, in the browser. It should take you to google.

As for the install error, after you installed the system, did you run an apt update and apt upgrade BEFORE you installed pi-hole?

7

Yes, I ran an apt-update/upgrade BEFORE installing PiHole.

Unfortunately, I've rebooted since the install and I can't scroll back up to show exactly where the installer just stopped. But there was no error code when I tried to install it the second time.

Oddly: typing in the Google IP manually into Chromium times out, though I can still ping it from the console. This is weird.

8

What happens now when you try to install pi-hole ?

9

"Could not resolve host"

10

edit /etc/resolv.con from 127.0.0.1 to 8.8.8.8

try it again.

11

I can't seem to get sufficient priveleges to write into resolv.conf

12

sudo nano /etc/resolv.conf

or any other editor ...

13

Got it, back up and running.

PiHole installed, but it failed to display the screen that shows me my password for the admin console. IIRC, that happened somewhere toward the end when I first installed it.

The management console is up and running again. Showing a pending update to the newest FTL version.

14

Ok, the installer stops after "Starting FTL service" and just returns to the command prompt.

Also displays an error of "unable to get latest release"

15

what does pihole status and pihole -v output ?

16

Status
DNS service is running
Pi-hole blocking is Enabled

-v
Pi-Hole version is 3.3.1
AdminLTE version is 3.3
/opt/pihole/version.sh: line 19: pihole-FTL: command not found
Latest FTL version is v3.0

17

try running a pihole -r and repair

also you might want to upload the logs and get a debug token for the devs

run pihole -d, upload to tricorder and provide the debug token.

18

Ran the repair script

Debug token is:
s3fsh3hu7j

And many thanks for the quick attention.

19

Well, it looks like everything is up and running now. Was it really just the resolv.conf file?

Is changing that to the Google IP change the behavior of how PiHole will function?

20

If you just change /etc/resolv.conf on the Raspberry Pi device itself, then there's really not a big difference. That's the server Raspbian will use (for things like curl or apt get).

Pi-hole itself will still use the upstreams that you have configured for DNS resolution, the /etc/resolv.conf is purely for the Raspberry Pi to query. If you are using the RPi as a workstation then you will lose the blocking but since a vast majority of users are just using the Raspberry Pi for Pi-hole you'll be fine.

1 Like