Pihole update schlägt fehl

Hallo zusammen,

habe mal wieder mit pihole -up nach updates gesucht. Leider funktioniert es nicht. Beim letzten Mal ging das Update ohne Probleme durch. Bei einem zweiten pihole, den ich betreibe, klappt alles. Vielleicht kann mir jemand helfen.
Danke
Gruß

Holger

Beobachtetes und erwartetes Verhalten

$ pihole -up
[✓] Update local cache of available packages
[i] Existing PHP installation detected : PHP version 7.4.33
[✓] Checking for git
[✓] Checking for iproute2
[✓] Checking for dialog
[✓] 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:.
             .. ','.
            .',,,,,,'.
          .',,,,,,,,,,.
        .',,,,,,,,,,,,....
      ....''',,,,,,,'.......
    .........  ....  .........
    ..........      ..........
    ..........      ..........
    .........  ....  .........
      ........,,,,,,,'......
        ....',,,,,,,,,,,,.
           .',,,,,,,,,'.
            .',,,,,,'.
              ..'''.

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

[✓] Checking apt-get for upgraded packages... 72 updates available
[i] It is recommended to update your OS after installing the Pi-hole!

[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/prerequisites/#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

Debug Token:

Funktioniert nicht

[✓] ** 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/pihole_debug.log

Dein Pi-hole-Rechner hat ein grundsätzliches Problem mit Namensauflösungen.

Für welchen DNS-Server ist der Rechner konfiguriert:

cat /etc/resolv.conf

Hallo,
danke für die schnelle Antwort.

Hab inzwischen das Problem vermutlich durch Zufall gelöst. Habe in raspi-config in den erweiterten Einstellungen auf Networkmanager geklickt. Jetzt geht es wieder. Aber warum, weiß ich nicht. Nach der Inbetriebnahme im Herbst wurde nichts geändert.

Die Ausgabe mit dem von dir genannten Befehl lautet:

cat /etc/resolv.conf

Generated by resolvconf

search fritz.box
nameserver 192.168.127.83

Gruß
Holger

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