Pihole -up / error messages

Help Community Help
1

Hi,

I turn again trustfully to the super community! :slight_smile:

Unfortunately I can not update my Pi-Hole for months.

I have already checked all the descriptive possibilities, I can say that they do not apply.

I get the following error:

[✓] Update local cache of available packages
[i] Existing PHP installation detected : PHP version 7.4.28
[✓] Checking for git
[✓] Checking for iproute2
[✓] Checking for whiptail
[✓] Checking for ca-certificates

[i] Checking for updates...
fatal: unable to access 'GitHub - pi-hole/pi-hole: A black hole for Internet advertisements': Could not resolve host: github.com
[i] Pi-hole Core: up to date
fatal: unable to access 'GitHub - pi-hole/web: Pi-hole Dashboard for stats and more': Could not resolve host: github.com
[i] Web Interface: up to date
[i] FTL: update available

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

[✓] Root user check

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

[✓] Update local cache of available packages
[i] Existing PHP installation detected : PHP version 7.4.28

[✓] Checking apt-get for upgraded packages... up to date!

[i] Checking for / installing Required dependencies for OS Check...
[✓] Checking for grep
[✓] Checking for dnsutils

[✗] Retrieval of supported OS list failed. dig failed with return code 10.
Unable to determine if the detected OS (Raspbian 11) is supported
Possible causes for this include:
- Firewall blocking certain DNS lookups from Pi-hole device
- ns1.pi-hole.net being blocked (required to obtain TXT record from versions.pi-hole.net containing supported operating systems)
- Other internet connectivity issues

  https://docs.pi-hole.net/main/prerequesites/#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)

  It is possible that the installation will still fail at this stage due to an unsupported configuration.
  If that is the case, you can feel free to ask the community on Discourse with the Community Help category:
  https://discourse.pi-hole.net/c/bugs-problems-issues/community-help/

Unable to complete update, please contact Pi-hole Support

Can anyone help me?

2

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:

pihole -d

or do it through the Web interface:

Tools > Generate Debug Log

3

Hi,

I was able to create the debug log.
However, it could not upload it.

[✓] ** FINISHED DEBUGGING! **

  • The debug log can be uploaded to tricorder.pi-hole.net for sharing with developers only.

[?] Would you like to upload the log? [y/N] y
* Using curl for transmission.
* curl failed, contact Pi-hole support for assistance.
* Error message: curl: (6) Could not resolve host: tricorder.pi-hole.net

[✗] There was an error uploading your debug log.

  • Please try again or contact the Pi-hole team for assistance.
  • A local copy of the debug log can be found at: /var/log/pihole_debug.log

probably I should upload the log here then?
/var/log/pihole_debug.log

Thanks

4

This will temporarily reset the nameserver on the Pi to bypass Pi-Hole DNS.

sudo nano /etc/resolv.conf

Edit the nameserver line to nameserver 9.9.9.9 or your preferred third party DNS service, save and exit

Run

pihole -d

and upload the debug log.

5

Okay, first of all I am a bit confused because there was only one IPv6 nameserver in there.
But yes, I now have a log which could be uploaded :slight_smile:

[✓] ** FINISHED DEBUGGING! **

  • The debug log can be uploaded to tricorder.pi-hole.net for sharing with developers only.

[?] Would you like to upload the log? [y/N] Y
* Using curl for transmission.

[✓] Your debug token is: https://tricorder.pi-hole.net/B2Qa2Isf/
[i] Logs are deleted 48 hours after upload.

  • Provide the token above to the Pi-hole team for assistance at https://discourse.pi-hole.net
  • A local copy of the debug log can be found at: /var/log/pihole_debug.log
6

Looks like you couldn't update because you were having DNS issues, but now you are able to connect.

Can you try to update again?

7

I think you don't need to look at the log anymore.
The update has now worked.
But what does that mean now?
Should I reverse the change now?
Or was that only the DNS server for the PiHole itself? But what are the upstream servers in the PiHole GUI?
My Pi Hole somehow continues to work anyway.

When I log in on my PiHole and go to
Settings
DNS
my IPv4 and IPv6 upstream DNS servers are still there.

8

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