Pihole Failing to Upgrade

Help
1

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

If you are Experiencing issues with a Pi-hole install that has non-standard elements (e.g you are using nginx instead of lighttpd, or there is some other aspect of your install that is customised) - please use the Community Help category.

Expected Behaviour:

Running pihole -up from SSH shell successfully updates the pihole installation to the latest

Actual Behaviour:

Error thrown: 'E: Package 'dialog' has no installation candidate' and appears to fail to update. Pi-hole version is stuck on 5.11.3 and FTL version is stuck on 5.15 (Web Interface is 5.13).

Debug Token:

https://tricorder.pi-hole.net/SWfztVeX/

2

Please post the complete output of sudo apt update.

3 
pi@raspberrypi:~ $ sudo apt update
Hit:1 http://archive.raspberrypi.org/debian buster InRelease
Get:2 http://raspbian.raspberrypi.org/raspbian bullseye InRelease [15.0 kB]
Fetched 15.0 kB in 1s (14.4 kB/s)
Reading package lists... Done
Building dependency tree
Reading state information... Done
All packages are up to date.
4

Output of the following, please:

pihole -up

5 
pi@raspberrypi:~ $ pihole -up
  [✓] Update local cache of available packages
  [i] Existing PHP installation detected : PHP version 7.3.31-1~deb10u1
  [✓] Checking for git
  [✓] Checking for iproute2
  [i] Checking for dialog (will be installed)
  [✓] Checking for ca-certificates
  [i] Waiting for package manager to finish (up to 30 seconds)
  [i] Processing apt-get install(s) for: dialog, please wait...

E: Package 'dialog' has no installation candidate
6

Those are not compatible. Your OS shows as Buster. Did you try to do an OS upgrade?

7

I am unsure, but I have been messing around with it, so it's very possible. Is there anything that I can do to move to the recommended OS/version? I would hate to have to wipe since I've got everything working seamlessly (both PiHole and PiVPN).

8

So there is nothing to do here except flash and re-build the pihole? I'm about to bite the bullet, but thought I would check just to make sure...

9

Or you could check and see why you have two different versions specified in your /etc/apt/sources.list.d/ files.