Cannot reinstall: All GitHub clones are timing out

Help
1

Expected Behaviour:

On a Raspberry Pi 3 running Raspbian Bookworm. Been using Pi-Hole for awhile. Recently, I tried to update Gravity after adding a new list. I would expect, as before, that this would go through quickly and smoothly.

Actual Behaviour:

It hung on a GitHub request. I noticed Pi-Hole needed an update. That also hung on a GitHub request to the FTL repository, eventually timing out. Per the recommendation in another post, I tried to recreate the AdminLTE renamed Web repository at /var/www/html/admin, which also timed out at the Receiving objects step. I eventually just uninstalled Pi-Hole and tried a re-installation, but once again it timed out trying to clone into /etc/.pihole.

Debug Token:

N/A

2

I will note that GitHub pulls on other machines work. I even tried using wget to just download the source code zip from its URL on the Pi, and that failed. On my main PC, it was near instant success. I also forgot to mention that before attempting to update Pi-Hole, I updated system packages. This was extremely sluggish and timed out a lot, until I used the web interface of Pi-Hole to disable blocking. I initially just tried whitelisting the domain that the update was timing out on, but it said the database was locked or read only or something. Last but not least, I changed the Pi’s resolv file to point to 8.8.8.8, and that didn’t help at all (it was previously pointing at my router).

3

Okay, so, I switched over to 5GHz Wi-Fi from Ethernet, and now it’s working great. I tried two different ethernet cables, although it is possible that both of them or the socket I plugged them into were bad. Even Debian packages were slow, but only GitHub pulls ALWAYS timed out. The Pi always sits on right next to the router, so maybe this is enough? Would like to know what happened though. I will note that the Wi-Fi on the Pi of course has a slightly different MAC address. I’ve reviewed the router settings a few times to make sure I didn’t blacklist the Pi by accident or something, but maybe my ISP did. Regardless, I think it is certain that this is not Pi-Hole’s fault, although y’all might have some general network comments to make.