Failed to connect to install.pi-hole.net port 443: No route to host

This is in regards to the latest PI4 and an update OS/system
I have installed pi-hole twice with cmd curl -sSL https://install.pi-hole.net | bash
Seems to fail since it never appears in /etc directory

I tried agarin to install and now I receive this message

Failed to connect to install.pi-hole.net port 443: No route to host

I can connect to Pi-hole over the internet

I have reinstalled curl
Updated
read and tried the fixes on the internet
Numerous reboots of the Hughes router and the P
I have searched similar post for unresolved host however I am still stumped
I setup RP with static in dhcpcd (all connections work in PUtty or VNC)

interface eth0
static ip_address=192.168.0.17/24
static routers=192.168.0.1
static domain_name_servers=192.168.0.1

interface wlan0
static ip_address=192.168.42.4/24
static routers=192.168.42.2
static domain_name_servers=192.168.42.2

router is a Hughes Gen 5
Pi is accessible via my local 5 g wireless and via cat 5 to computer or to Hughes Router
Currently Pi is hard cabled to Hughes router
Router ip is 192.168.0.1
Additional screens on router admin are in 192.168.42.2 + range
I have no filters exceptions or limits on Ip ranges in the Hughes router
DHCP cannot be shut off in router
Any advice is welcome
Gary

Change the name server on the Pi to an external DNS other than the router. Something like Cloudflare, for example.

to jfb:
Thanks, however no success, below are the changes I made (I also re-enabled ssh and rebooted)

interface eth0
static ip_address=192.168.0.17/24
static routers=192.168.0.1
static domain_name_servers=1.1.1.1

interface wlan0
static ip_address=192.168.42.4/24
static routers=192.168.42.2
static domain_name_servers=1.1.1.1

to jfb
Hello I made recommended changes from discourse Pi to dnsmasq

i noticed that the changes made in dnsmasq di not roll over to dhcpcd

I have restarted and confirmed dnsmasq is active

No success Different message below

"Could not resolve host: install.pi-hole.net"

Gary

pihole-FTL conflicts with dnsmasq since it includes dnsmasq. Did you manually install dnsmasq?

Yes I updated dmasq then configured
dmasq seems out of sync with dhcpcd and raspi-conf seems out of sync with dhcpcd

i just ran resolvconfig and see only my local host

Generated by resolvconf

nameserver 127.0.0.1

I could start over since it was working but really end of know how
Thanks, Gary

You should not be running dnsmasq at all. This software is embedded in pihole-FTL. Existing dnsmasq configurations work with pihole-FTL, but dnsmasq and pihole-FTL cannot run at the same time as separate processes.

JFB
Thanks for the help, sorry for the delay. I had lost browser internet connectivity in RP only. I commented yt no-resolv and fixed theinternet connection problem. Still unable to laod p-hole. I tried to remove, rename dnsmasq.d but unalb eto do . Also there is only a redme file in directory, so I disabled the service
sudo systemctl disable dnsmasq.service
no success
Failed to connect to install.pi-hole.net port 443: No route to host
Cand you offer any other recommendation, other wise I think this is the end of my attempts.
Thanks Gary

ip -4 route show

traceroute -n install.pi-hole.net

?

Try hash out/remove above two lines for the wlan0 interface and reboot to narrow down.
Make it like below:

interface eth0
  static ip_address=192.168.0.17/24
  static routers=192.168.0.1
  static domain_name_servers=192.168.0.1

interface wlan0
  static ip_address=192.168.42.4/24

to deHakkelaar
Thanks for the advice, I made the changes you recommeded but no success
Failed to connect to install.pi-hole.net port 443: No route to host

Gary

After you made my recommended changes and rebooted, whats output for below two ?

This is the result

pi@GBSpi:~ $ ip -4 route show
default via 192.168.0.1 dev eth0 src 192.168.0.17 metric 202
192.168.0.0/24 dev eth0 proto dhcp scope link src 192.168.0.17 metric 202
192.168.42.0/24 dev wlan0 proto dhcp scope link src 192.168.42.4 metric 303
pi@GBSpi:~ $
pi@GBSpi:~ $ traceroute -n install.pi-hole.net
traceroute to install.pi-hole.net (167.71.111.190), 30 hops max, 60 byte packets
 1  192.168.0.17  3094.679 ms !H  3094.559 ms !H  3094.491 ms !H
pi@GBSpi:~ $

Gary

Somthing odd going on that I dont have an explanation for.
The ip route command shows the correct default route via IP 192.168.0.1 to Internet.
But the first hop from traceroute seems not to be the 192.168.0.1 IP (which was expected) but the 192.168.0.17 IP instead (which seems to be the own host).
I have no clue why.

pi@ph5:~ $ ip -4 route show
default via 10.0.0.1 dev eth0 src 10.0.0.4 metric 202
10.0.0.0/24 dev eth0 proto dhcp scope link src 10.0.0.4 metric 202

pi@ph5:~ $ traceroute -n install.pi-hole.net
traceroute to install.pi-hole.net (167.71.111.190), 30 hops max, 60 byte packets
 1  10.0.0.1  0.812 ms  0.624 ms  0.621 ms
 2  192.168.1.1  1.173 ms  0.764 ms  0.750 ms
 3  62.58.240.1  9.603 ms  9.044 ms  8.611 ms
 4  212.53.25.201  26.420 ms  25.925 ms  9.236 ms
 5  130.244.21.85  12.622 ms  12.409 ms  12.457 ms
 6  130.244.200.19  13.824 ms  13.098 ms  13.374 ms
 7  62.115.136.194  104.574 ms  104.514 ms  104.603 ms
 8  * 62.115.113.239  102.226 ms  115.338 ms
 9  * * 62.115.112.244  98.472 ms
10  62.115.140.223  103.754 ms 62.115.139.151  104.854 ms 62.115.140.223  103.731 ms
11  * * *
12  * * *
13  * * *
14  167.71.111.190  91.423 ms  94.745 ms  94.529 ms

If no one else comes up with a solution, I would suggest to start fresh again.

Thanks you for your help. I do not really know how to start "fresh again". I inactivated dmasq, tried to reload OS on raspberry but it only allows me to write from card which already has the network and dmasq configuration already written to. I reviewed how to's on google, but I get the same result each time I try to reboot from the card. I could rewrite the card but I really don/t now how. Also I really don't know why this will not work. I previously was able to access pi-hole. I can successfully use all network functions and access all web sites, except for pi-hole. All of my work and communication is in regards to only the pi-hole connection and retrieval of the install package. SInce I am not successful, seems like a pi-hole issue, and I reall do not need their service, just nice to have, so I am done with the issue.
But again, thank you.
Gary

How did you install Pi-hole originally?

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