Unable to access github.com for update

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

If you are Experiencing issues with a Pi-hole install that has non-standard elements (e.g you are using nginx, apache2 or another reverse proxy, or there is some other aspect of your install that is customised) - please use the Community Help category.

Expected Behaviour:

Update runs and gets implemented on Raspberry Pi Zero 2 W running Pi-hole. This has been going on for a month or two now, but the output varies. Sometimes all 3 update checks fail or sometimes 2 fail.

Actual Behaviour:

sudo pihole -up
  [✓] Update local cache of available packages
  [✓] Building dependency package pihole-meta.deb
  [✓] Installing Pi-hole dependency package

  [i] Checking for updates...
  [i] Pi-hole Core:     update available
fatal: unable to access 'https://github.com/pi-hole/web.git/': Could not resolve host: github.com

  Error: Unable to update local repository. Contact Pi-hole Support.
pihole -v
Core version is v6.1.2 (Latest: N/A)
Web version is v6.2.1 (Latest: v6.2.1)
FTL version is v6.2.3 (Latest: v6.2.3)

Debug Token:

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

Change your /etc/resolv.conf to use a remote DNS server (like 1.1.1.1 or 8.8.8.8)

-rw-r--r-- 1 root root 55 Jul 14 12:29 /etc/resolv.conf
   nameserver 192.168.68.69

You really don't want the server running Pi-hole to use itself for DNS because it can cause situations like this.

1 Like

Thank you so much! For those who are having the same problem as me, here's what I did:

  1. nmcli connection show
  2. nmcli connection modify "Wired connection 1" ipv4.dns "9.9.9.9" ipv4.ignore-auto-dns yes
  3. nmcli connection down "Wired connection 1" and nmcli connection up "Wired connection 1" (or alternatively sudo systemctl restart NetworkManager)
  4. Check with sudo nano /etc/resolv.conf
1 Like

Ok, so a couple of days after doing that, my new devices on my network now share the client name of pi.hole. I also can't add the new devices to groups. I tried to flush the logs and network table as this user did, but no luck. Any help would be appreciated!

new debug: https://tricorder.pi-hole.net/xINlwe4U/

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