Can't change Gateway with PiHole-r

[Ark]

Expected Behaviour:
Be able to change default Gateway with PiHole-r

Actual Behaviour:

PiHole-r script crashes as it can't download a GitHub file via a non-existent Gateway.

Debug Token:

Not provided - could not upload via curl or web interface !

Hi all - I hope someone can help me - a novice - with this issue & thanks in anticipation.

My Pihole (now V5) is on a PiZero & been working perfectly for 12+ months on my network Gateway 192.168.2.1.

I temporarily moved the Pi to another router recently (that Gateway was 192.168.88.1) but since moving the Pi back to its original network
the PiHole has retained the 192.168.88.1 Gateway address for some reason & so now has no network access (unable to Ping anyone from within Pi SSH).
All the other Clients on this 192.168.2.1 network can see this Gateway & can access the WWW accordingly.

A Pihole-d shows this as ..

[i] Default IPv4 gateway: 192.168.88.1

• Pinging 192.168.88.1...
  [✗] Gateway did not respond.

When I used pihole-r I can change the Gateway address to 192.168.2.1 initially during the process, but the pihole-r script subsequently crashes
as it attempts to load the "github FTL file" via the non-existent Pihole Gateway IP.

The restoration process aborts without updating the Gateway IP as requested - the error message ...

[✓] Checking for user 'pihole'
[i] FTL Checks...
[✓] Detected ARM-hf architecture (armv6 or lower) Using ARM binary
[i] Checking for existing FTL binary...
[i] Downloading and Installing FTL...curl: (6) Could not resolve host: github.com
[✗] Downloading and Installing FTL
Error: URL https://github.com/pi-hole/ftl/releases/latest/download/pihole-FTL-arm-linux-gnueabi not found
[✗] FTL Engine not installed

I tried Router reboot etc & this idea from a previous Discourse post (FTL Engine not installed) but did not work for me....

"RamSet
Moderator
Apr '18

[✗] Downloading and Installing FTL

Error: Unable to get latest release location from GitHub

edit /etc/resolv.conf and change from 127.0.0.1 to let’s say google’s 8.8.8.8 - run a pihole -r and repair."

I seem to be going around in circles on this - I have the feeling there will be a simple answer.

All assistance will be greatly appreciated - kind regards Ark.

[deHakkelaar]

Edit below file:

sudo nano /etc/dhcpcd.conf

At the bottom you'll find a section similar as below:

pi@ph5:~ $ tail /etc/dhcpcd.conf
[..]
interface eth0
  static ip_address=10.0.0.4/24
  static routers=10.0.0.1
  static domain_name_servers=10.0.0.1

Enter your network preferences here, save/exit and run below to apply:

sudo systemctl restart dhcpcd

Check with:

ip -4 address show

ip -4 route show

cat /etc/resolv.conf

EDIT: ow and run reconfigure afterwards to tell Pi-hole of the changes:

pihole -r

[Ark]

Brilliant - kind sir - the solution worked a treat. Much appreciate your help & all the devs work.
Stay Safe