UPDATE FAILED: Pi-hole version is v4.2 -- Unable to complete update, please contact Pi-hole Support

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

Thank you kindly in advance for any, and all information, suggestions, contributions, pro-tips and just general niceness from anyone who is able to contribute to my frustrations. Unsure if the issue stems from the fact that I'm running the testing branch of headless Raspbian Lite, or if it is something else entirely. That's why I'm here, so the experts can tell me what/where I've gone awry. Thanks again, happy Super Sunday to all you Americans who are interested in watching the Super fatball Bowl. :woozy_face:

If I have neglected to include any relevant information, please just say the word and I'll do my best to produce it immediately. Thanks again, so so very much. My network cannot survive without (redundant) Pi-holes. Will be looking forward to the expert opinions steering me in the proper direction to get this issue resolved.

  • Raspberry Pi 3 B+
  • OS: Raspbian Lite GNU/Linux buster/sid
  • Linux pihole2 4.14.79-v7+ #1159 SMP Sun Nov 4 17:50:20 GMT 2018 armv7l GNU/Linux

Expected Behaviour:

Pihole web admin console should load as normal.

Actual Behaviour:

# This site can’t be reached
**192.168.11.8** refused to connect.

Pi-hole web admin console fails to load at all. Update did not complete successfully, which resulted in this error: "Unable to complete update, please contact Pi-hole Support"

Appears to be an issue with index.lighttpd.html, but I'm just taking a wild stab in the dark.

Debug Token: weusz73mg4

Additional information:

(which may or may not be relevant)

pihole_debug-sanitized.log --> https://pastebin.com/fK9vFabC
pihole_debug.log --> https://pastebin.com/d71GcuUF

Second (or third) attempt at running pihole -up command:

`user@pihole2:~ $ pihole -up`
  [i] Checking for updates...
  [i] Pi-hole Core:     update available
  [i] Web Interface:    up to date
  [i] FTL:              up to date

  [i] Pi-hole core files out of date, updating local repo.
  [βœ“] Check for existing repository in /etc/.pihole
  [βœ“] Update repo in /etc/.pihole

  [i] If you had made any changes in '/etc/.pihole/', they have been stashed using 'git stash'

  [βœ“] Root user check

        .;;,.
        .ccccc:,.
         :cccclll:.      ..,,
          :ccccclll.   ;ooodc
           'ccll:;ll .oooodc
             .;cll.;;looo:.
                 .. ','.
                .',,,,,,'.
              .',,,,,,,,,,.
            .',,,,,,,,,,,,....
          ....''',,,,,,,'.......
        .........  ....  .........
        ..........      ..........
        ..........      ..........
        .........  ....  .........
          ........,,,,,,,'......
            ....',,,,,,,,,,,,.
               .',,,,,,,,,'.
                .',,,,,,'.
                  ..'''.

  [i] Existing PHP installation detected : PHP version 7.3.1-1
  [i] Performing unattended setup, no whiptail dialogs will be displayed
  [βœ“] Disk space check
  [βœ“] Update local cache of available packages

  [βœ“] Checking apt-get for upgraded packages... up to date!

  [i] Installer Dependency checks...
  [βœ“] Checking for apt-utils
  [βœ“] Checking for dialog
  [βœ“] Checking for debconf
  [βœ“] Checking for dhcpcd5
  [βœ“] Checking for git
  [βœ“] Checking for iproute2
  [βœ“] Checking for whiptail

  [i] Performing reconfiguration, skipping download of local repos
  [βœ“] Resetting repository within /etc/.pihole...
  [βœ“] Resetting repository within /var/www/html/admin...
  [i] Main Dependency checks...
  [βœ“] Checking for cron
  [βœ“] Checking for curl
  [βœ“] Checking for dnsutils
  [βœ“] Checking for iputils-ping
  [βœ“] Checking for lsof
  [βœ“] Checking for netcat
  [βœ“] Checking for psmisc
  [βœ“] Checking for sudo
  [βœ“] Checking for unzip
  [βœ“] Checking for wget
  [βœ“] Checking for idn2
  [βœ“] Checking for sqlite3
  [βœ“] Checking for libcap2-bin
  [βœ“] Checking for dns-root-data
  [βœ“] Checking for resolvconf
  [βœ“] Checking for libcap2
  [βœ“] Checking for lighttpd
  [βœ“] Checking for php7.3-common
  [βœ“] Checking for php7.3-cgi
  [βœ“] Checking for php7.3-sqlite3

  [βœ“] Enabling lighttpd service to start on reboot...

  [i] FTL Checks...

  [βœ“] Detected ARM-hf architecture (armv7+)
  [i] Checking for existing FTL binary...
  [i] Latest FTL Binary already installed (v4.2). Confirming Checksum...
  [i] Checksum correct. No need to download!
  [βœ“] Checking for user 'pihole'
  [βœ“] Installing scripts from /etc/.pihole

  [i] Installing configs from /etc/.pihole...
  [i] Existing dnsmasq.conf found... it is not a Pi-hole file, leaving alone!
  [βœ“] Copying 01-pihole.conf to /etc/dnsmasq.d/01-pihole.conf

  [i] Installing blocking page...
  [βœ“] Creating directory for blocking page, and copying files
  [βœ—] Backing up index.lighttpd.html
      No default index.lighttpd.html file found... not backing up

  [βœ“] Installing sudoer file

  [βœ“] Installing latest Cron script

  [βœ“] Installing latest logrotate script
  [i] Backing up /etc/dnsmasq.conf to /etc/dnsmasq.conf.old
  [βœ“] man pages installed and database updated
  [i] Testing if systemd-resolved is enabled
  [i] Systemd-resolved is not enabled
  [i] Restarting lighttpd service...
  Unable to complete update, please contact Pi-hole Support

This is the device in question, giving me issues:

Buster/Sid does have different lighttpd package version than the released Stretch. Since we are unable to support a moving target we are unable to support Buster/Sid.

1 Like

So I have to reroll with the main (stretch) branch, is essentially the solution? I understand you cannot possibly support every possible combination -- but are there any other suggestions? What packages could i potentially attempt to downgrade in hopes of getting this issue resolved (if any)?

I'm far from an expert and should have known better than to fiddle with things on such a critical appliance for our network, but I cannot seem to help myself, I love to tinker. Thank you kindly for the prompt response.

Buster/sid on RPi 3 B+

user@pihole2:~ $ lighttpd -v

lighttpd/1.4.53 (ssl) - a light and fast webserver

Compared with the Ubuntu Server 18.04.1 LTS VM:

user@pihole:~$ lighttpd -v

lighttpd/1.4.45 (ssl) - a light and fast webserver
Build-Date: Feb 6 2018 12:41:51

When i now run the following commands, I get an all green on the status report(s):

user@pihole2:~ $ pihole -up

  [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!

There are configuration file syntax changes between the versions of lighttpd that cause some errors. If you wanted to dig around, you can invoke lighttpd in the shell and have it verify the configuration file for any errors or changes. And the changelogs would be a good place to look. But try (with 1.4.53) lighttpd -t -f <path_to_config> to test the configuration, or lighttpd -f <path_to_config> -D to run in shell and not daemonize.

1 Like

Thank you kindly for the guidance. Hopefully I can fumble my way through this and not have to rebuild entirely (one of the disadvantages of running baremetal as opposed to a virtual machine, but thus is life). It's hard to argue with the 4-5W device as an always-on, secondary name-server, pulling double/triple duty as Unbound + OpenVPN server, as well.

Have to run out for a bit, but will try to tackle this a bit later this afternoon, or first opportunity I get and report back ASAP. Thanks again, Mr. Schaper, sir. Your intellect and expertise is greatly appreciated, as always.

EDIT: In the mean time, I believe I have a backup (third) Pi-hole VM waiting to be updated and tossed in the mix until I can figure this out... that should at least buy me a little time, so I don't have to go back to running just a single Pi-hole name server. Ohhh, the travesty!

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