Hello,
I've installed Pi-hole a while ago on an old Raspberry Pi 1 and until now, everything worked fine. I've upgraded Raspbian to v. 12 (Bookworm) some time ago.
I've noticed today that if I want to update Pi-hole, I get a message with "Unsupported OS detected: Raspbian 12". I don't really understand why, as Debian 12 is in the list of supported OS. Is it because it's the Raspbian variant?
Pi-hole seems to work still but the FTL part has an update that I can't apply because of this and I'm not sure if I should force it with the env var, nor if the error is normal.
EDIT: whoops, I just saw that there's a different line for RaspberryPi OS/Raspbian in the compatibility table and mentions Bullseye (11) at best, which explains the error message...
Is there a reason for this? I.e. has support for the Pi OS been dropped, or is it just delayed for that version? Are there known issues with it or is it safe to force the update?
Yeah, I've seen that afterwards. Any idea if support will come later or if it's been dropped? or if it's fine to force the update, if there are known issues with Pi OS 12?
Well, Raspbian/Raspberry Pi OS is just a Debian-based distro with extra specific repos. I saw that Debian 12 stable had been released, checked that the Pi-specific repos had a bookworm branch, changed the sources.list and did a dist-upgrade.
Please upload a debug log and post just the token URL that is generated after the log is uploaded by running the following command from the Pi-hole host terminal:
Well, I used the Pi installer. I really can't remember, though, if my last installation dates from before the change of name from Raspbian to Raspberry Pi OS. I might have installed it when it was the version based on Debian 9 or 10, and then upgraded to newer versions when they were released.
I don't really understand why you think I'm running Debian and it's showing the OS as Raspbian.
Because there has been no release of a Raspberry Pi OS 12 (Bookworm). Their latest release is 11 (Bullseye). Screen capture from their software page today:
For an out of the box Raspbian 11 install on one of my Pi's, it looks like this:
cat /etc/apt/sources.list
deb http://raspbian.raspberrypi.org/raspbian/ bullseye main contrib non-free rpi
# Uncomment line below then 'apt-get update' to enable 'apt-get source'
#deb-src http://raspbian.raspberrypi.org/raspbian/ bullseye main contrib non-free rpi
Yes, but as I said, I changed the sources from bullseye to bookworm and did a dist-upgrade.
sources.list:
deb http://raspbian.raspberrypi.org/raspbian/ bookworm main contrib non-free rpi
# Uncomment line below then 'apt-get update' to enable 'apt-get source'
#deb-src http://raspbian.raspberrypi.org/raspbian/ bookworm main contrib non-free rpi
Yeah, I'm a bit hesitant to use the bypass, I was wondering if someone already tried it and could confirm that everything worked fine.
I'll probably try it but just in case, if someone has concrete experience on this...
BTW, it seems that the official release of Raspbian/Raspberry Pi OS 12 is october. Can we expect a quick upgrade of Pi-hole to support it or there's no ETA? Because if it's just a matter of weeks, it could be preferable for me to wait for it.
I've done that In August and pihole works with a minor restriction in my case.
I've DHCP enabled and would normally set my DNS to unbound in my raspis localhost.
However, thats broken for me. If you switch the DNS for now to a public Server, it all works fine for now. I have to check out the unbound config again, when I have the time.
I'm in the same situation. Can you please tell me how exactly you "forced the update"? Update what to what version? And how? Please and thank you in advance.
When running pihole -up, I got the following message initially (before posting here):
If you are seeing this message and you do have a supported OS, please contact support.
https://docs.pi-hole.net/main/prerequisites/#supported-operating-systems
If you wish to attempt to continue anyway, you can try one of the following commands to skip this check:
e.g: If you are seeing this message on a fresh install, you can run:
curl -sSL https://install.pi-hole.net | sudo PIHOLE_SKIP_OS_CHECK=true bash
If you are seeing this message after having run pihole -up:
sudo PIHOLE_SKIP_OS_CHECK=true pihole -r
(In this case, your previous run of pihole -up will have already updated the local repository)
Given that I had just run pihole -up and that it reloaded the repos' content, I used the command mentioned:
sudo PIHOLE_SKIP_OS_CHECK=true pihole -r
Apparently, the -r option is used to repair the installation, so I'm not sure if it was actually the proper one to use (-up might be the one to use? maybe without sudo?) but it seems to have done the trick.
If you don't have the same message as above with the command mentioned when trying to update, you might not be in the same situation.
Nice. Is there something specific to do on my side or can I just assume that it'll simply work when using the update next time (instead of having to force it)?
