FTL out of date - Unable to complete update, please contact Pi-hole Support

Help
1

Expected Behaviour:

'pihole -up' to update all components of my installation - Pi-hole Core, Web Interface, and FTL

Actual Behaviour:

Running 'pihole -up' on my CentOS 8 installation shows me that Pi-hole Core and Web Interface are both up to date, but then says:

[i] FTL: update available
[i] FTL out of date, it will be updated by the installer.

But the installer never updates anything. At the end of the update, I get the message:

Unable to complete update, please contact Pi-hole Support

Debug Token:

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

2

No ideas?

Playing around with things this morning, I visted "Release Pi-hole FTL v5.3.1 · pi-hole/FTL · GitHub" and downloaded the latest binary for my architecture there. I replaced the pihole-FTL binary in /usr/bin on my system and restarted pihole-FTL.

Now when I do a "pihole -up" from the CLI, it shows that my pihole-FTL is up to date. However, the web interface is still showing that there is an update available, so something is out of sync doing the update that way.

I'll probably downgrade back to the original version since I don't have any problems with the older version and don't want to create more problems in the future moving forward with this being mismatched. But if anyone has any ideas of where I should go from here, it would be greatly appreciated.

3

What is the output of the following from the Pi terminal:

pihole -v

As of now, the latest release is:

  Pi-hole version is v5.2 (Latest: v5.2)
  AdminLTE version is v5.2 (Latest: v5.2)
  FTL version is v5.3.1 (Latest: v5.3.1)
4

When I copy the new binary over, I get:

pihole -v

Pi-hole version is v5.2 (Latest: v5.2)
AdminLTE version is v5.2 (Latest: v5.2)
FTL version is v5.3.1 (Latest: v5.3.1)

And actually, looking at the admin UI in a private window of my browser it is also showing the latest FTL version. So I'm guessing the old FTL status was caused by a bad cached page someplace.

Is it OK to leave the upgrade in place the way that I've manually done it then? I don't necessarily want to cause problems with future updates in the future if/when this particular bug gets resolved?

Thanks!

5

It should be OK to leave the current version in place. The web admin page should catch up in 24 hours with the correct update information.

6

Awesome! Thank you so much for your response and feedback!

7

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.