I am unable to update my pihole because the installation cannot access github.com
Very similar to the situation described here Unable to update Pi-hole unfortunately the original poster did not give details into how they fixed it.
I am able to access github.com from client devices on the network so I am extremely stumped why the pihole itself cannot access it.
Expected Behaviour:
pihole up should complete without issue
Actual Behaviour:
pihole up fails because it cannot contact github.com
Debug Token:
https://tricorder.pi-hole.net/pig496ghb8
Additional information to help debugging:
The debug log says that 10.0.0.1 (my router) cannot be found, but it responds to manual pings
PING 10.0.0.1 (10.0.0.1) 56(84) bytes of data.
64 bytes from 10.0.0.1: icmp_seq=1 ttl=64 time=0.616 ms
64 bytes from 10.0.0.1: icmp_seq=2 ttl=64 time=0.500 ms
64 bytes from 10.0.0.1: icmp_seq=3 ttl=64 time=0.463 ms
PING google.com(ord38s01-in-x0e.1e100.net (2607:f8b0:4009:811::200e)) 56 data bytes
64 bytes from ord38s01-in-x0e.1e100.net (2607:f8b0:4009:811::200e): icmp_seq=1 ttl=114 time=18.2 ms
64 bytes from ord38s01-in-x0e.1e100.net (2607:f8b0:4009:811::200e): icmp_seq=2 ttl=114 time=20.6 ms
64 bytes from ord38s01-in-x0e.1e100.net (2607:f8b0:4009:811::200e): icmp_seq=3 ttl=114 time=16.3 ms
PING github.com (140.82.114.3) 56(84) bytes of data.
From 10.0.0.16 (10.0.0.16) icmp_seq=1 Destination Host Unreachable
From 10.0.0.16 (10.0.0.16) icmp_seq=2 Destination Host Unreachable
From 10.0.0.16 (10.0.0.16) icmp_seq=3 Destination Host Unreachable
traceroute to github.com (140.82.112.4), 30 hops max, 60 byte packets
1 10.0.0.16 (10.0.0.16) 3059.644 ms !H 3059.110 ms !H 3059.015 ms !H
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 9.9.9.9
nameserver 149.112.112.112
nameserver 2620:fe::fe
#nameserver 2600:6c4a:7b7f:f378:ce1c:b206:45d5:12ad
search lan
# A sample configuration for dhcpcd.
# See dhcpcd.conf(5) for details.
# Allow users of this group to interact with dhcpcd via the control socket.
#controlgroup wheel
# Inform the DHCP server of our hostname for DDNS.
hostname
# Use the hardware address of the interface for the Client ID.
#clientid
# or
# Use the same DUID + IAID as set in DHCPv6 for DHCPv4 ClientID as per RFC4361.
# Some non-RFC compliant DHCP servers do not reply with this set.
# In this case, comment out duid and enable clientid above.
duid
# Persist interface configuration when dhcpcd exits.
persistent
# Rapid commit support.
# Safe to enable by default because it requires the equivalent option set
# on the server to actually work.
option rapid_commit
# A list of options to request from the DHCP server.
option domain_name_servers, domain_name, domain_search, host_name
option classless_static_routes
# Respect the network MTU. This is applied to DHCP routes.
option interface_mtu
# Most distributions have NTP support.
#option ntp_servers
# A ServerID is required by RFC2131.
require dhcp_server_identifier
# Generate SLAAC address using the Hardware Address of the interface
#slaac hwaddr
# OR generate Stable Private IPv6 Addresses based from the DUID
slaac private
interface eth0
static ip_address=10.0.0.16/24
static routers=10.0.0.1
static domain_name_servers=9.9.9.9 149.112.112.112