Something has gone wrong, contact support

General beta
1

I have pi-hole on rpi4 bookworm, all working well, no issues - though, yesterday, when doing routine check/daily update, it threw an error, then, again, same error

Something has gone wrong, contact support

Linux rpi2 6.12.47+rpt-rpi-v8 #1 SMP PREEMPT Debian 1:6.12.47-1+rpt1~bookworm (2025-09-16) aarch64

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Sat Nov 15 16:35:01 2025
voytek@rpi2:~ $ sudo pihole -up
[✓] Building dependency package pihole-meta.deb
[✓] Installing Pi-hole dependency package

[i] Checking for updates...
[i] Pi-hole Core:     up to date
[i] Web Interface:    up to date
[i] FTL:              Something has gone wrong, contact support
voytek@rpi2:~ $ sudo pihole -up
[✓] Building dependency package pihole-meta.deb
[✓] Installing Pi-hole dependency package

[i] Checking for updates...
[i] Pi-hole Core:     up to date
[i] Web Interface:    up to date
[i] FTL:              Something has gone wrong, contact support
voytek@rpi2:

anyhow, after a brief wait, tried again - no issues, updated fine, or rather, was up to date - no error anymore

voytek@rpi2:~ $ sudo pihole -up
[✓] Building dependency package pihole-meta.deb
[✓] Installing Pi-hole dependency package

[i] Checking for updates...
[i] Pi-hole Core:     up to date
[i] Web Interface:    up to date
[i] FTL:              up to date

[✓] Everything is up to date!
voytek@rpi2:

just now, tried again, new update available, updated no issues as it usually does

as I don’t recall such issues before, thought to report, just in case

thanks for pi-hole, what a great idea and tool!

[✓] Update complete!

Core
Version is v6.2.2-17-gbbd3504 (Latest: null)
Branch is development
Hash is bbd35045 (Latest: bbd35045)
Web
Version is v6.3-29-geb975e5 (Latest: null)
Branch is development
Hash is eb975e5f (Latest: eb975e5f)
FTL
Version is vDev-b5529c3 (Latest: null)
Branch is development
Hash is b5529c30 (Latest: b5529c30)
voytek@rpi2:~ $ uname -a
Linux rpi2 6.12.47+rpt-rpi-v8 #1 SMP PREEMPT Debian 1:6.12.47-1+rpt1~bookworm (2025-09-16) aarch64 GNU/Linux
2

This error message is printed when there is an issue during the download of FTL binary file.

Apparently it was just a temporary Internet failure (or a server failure) and the update was successful when the network connection was working again.

If it happens again, please report back, but I think it was just a temporary glitch.

1 Like
3

getting it again, this time on beta pihole:

this is on the beta pi-hole:

$ sudo pihole -up
[✓] Building dependency package pihole-meta.deb
[✓] Installing Pi-hole dependency package

[i] Checking for updates...
[i] Pi-hole Core:     up to date
[i] Web Interface:    update available
[i] FTL:              update available

[i] Pi-hole Web Admin files out of date, updating local repo.
[✓] Check for existing repository in /var/www/html/admin/
[i] Update repo in /var/www/html/admin/...
: Could not update local repository. Contact support.

$ uname -a
Linux rpi2 6.12.62+rpt-rpi-v8 #1 SMP PREEMPT Debian 1:6.12.62-1+rpt1~bookworm (2026-01-19) aarch64 GNU/Linux

$ sudo pihole -v
Core
Version is v6.3-54-g3d3be66 (Latest: null)
Branch is development
Hash is 3d3be666 (Latest: 3d3be666)
Web
Version is v6.4.1-27-ga62eded (Latest: null)
Branch is development
Hash is a62ededa (Latest: 220ae545)
FTL
Version is vDev-ba3c03b (Latest: null)
Branch is development
Hash is ba3c03b9 (Latest: ba3c03b9)

no big issue, just reporting, I’ll try again in a while, and, see if it’s gone

4

The files are there and there is no issues on our server.

This is probably a temporary network issue between your home and Pi-hole server (like the first time). Wait a few minutes and try again.

5

You are not on the master release branch.
Are you running the development branch by intention?

6

Just a note:

Why are you running development branch?
Is this on purpose or did you forget to return to master branch after testing something?

EDIT:

That's funny... we posted at the same time.

7

thanks for the replies!

thanks for the replies to both of you!

why? no real reason, other than, I have two RPIs here, so, I thought:

hmm, why not try (new and shiny) beta, maybe it’s ‘something’, I have a spare RPI, why not

also, I run other beta ‘things’ - hoping it might contribute a little in testing/assessment/whatever

but, the one my PC is pointed at, is ‘release_version, beta_version’