the_LXZ
February 4, 2023, 12:23pm
1
The issue I am facing:
user@pihole:~ $ sudo curl -v -sSL https://install.pi-hole.net | bash
Trying 164.90.255.4:443...
Immediate connect fail for 164.90.255.4: Network is unreachable
Closing connection 0
curl: (7) Couldn't connect to server
Alternate approach doesn't work either:
user@pihole:~ $ wget -O basic-install.sh https://install.pi-hole.net
--2023-02-04 13:22:42-- https://install.pi-hole.net/
Resolving install.pi-hole.net (install.pi-hole.net)... 164.90.255.4
Connecting to install.pi-hole.net (install.pi-hole.net)|164.90.255.4|:443... failed: Network is unreachable.
Details about my system:
Raspberry Pi 3B, latest Raspberry Pi OS Lite 64-Bit
What I have changed since installing Pi-hole:
I can't install it
jfb
February 4, 2023, 1:48pm
2
You have a network connectivity problem on your device.
wd9895
February 4, 2023, 4:05pm
3
Yes, check LAN or Wifi connections.
Well, I actually access the pi via SSH, so it's not like the LAN doesn't work. Also, Curl works when you just test it with example.com:
user@pihole:~ $ sudo curl -v -sSL https://example.com
Trying 2606:2800:220:1:248:1893:25c8:1946:443...
Connected to example.com (2606:2800:220:1:248:1893:25c8:1946) port 443 (#0 )
ALPN, offering h2
ALPN, offering http/1.1
successfully set certificate verify locations:
CAfile: /etc/ssl/certs/ca-certificates.crt
CApath: /etc/ssl/certs
TLSv1.3 (OUT), TLS handshake, Client hello (1):
TLSv1.3 (IN), TLS handshake, Server hello (2):
TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
TLSv1.3 (OUT), TLS handshake, Client hello (1):
TLSv1.3 (IN), TLS handshake, Server hello (2):
TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
TLSv1.3 (IN), TLS handshake, Certificate (11):
TLSv1.3 (IN), TLS handshake, CERT verify (15):
TLSv1.3 (IN), TLS handshake, Finished (20):
TLSv1.3 (OUT), TLS handshake, Finished (20):
SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
ALPN, server accepted to use h2
Server certificate:
subject: C=US; ST=California; L=Los Angeles; O=Internet▒Corporation▒for▒Assig ned▒Names▒and▒Numbers; CN=www.example.org
start date: Jan 13 00:00:00 2023 GMT
expire date: Feb 13 23:59:59 2024 GMT
subjectAltName: host "example.com" matched cert's "example.com"
issuer: C=US; O=DigiCert Inc; CN=DigiCert TLS RSA SHA256 2020 CA1
SSL certificate verify ok.
Using HTTP2, server supports multi-use
Connection state changed (HTTP/2 confirmed)
Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
Using Stream ID: 1 (easy handle 0x559dc51ce0)
GET / HTTP/2
Host: example.com
user-agent: curl/7.74.0
accept: /
TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
old SSL session ID is stale, removing
Connection state changed (MAX_CONCURRENT_STREAMS == 100)!
< HTTP/2 200
< age: 258521
< cache-control: max-age=604800
< content-type: text/html; charset=UTF-8
< date: Sat, 04 Feb 2023 16:18:45 GMT
< etag: "3147526947+ident"
< expires: Sat, 11 Feb 2023 16:18:45 GMT
< last-modified: Thu, 17 Oct 2019 07:18:26 GMT
< server: ECS (nyb/1D11)
< vary: Accept-Encoding
< x-cache: HIT
< content-length: 1256
<
<!doctype html>
Example Domain
<meta charset="utf-8" />
<meta http-equiv="Content-type" content="text/html; charset=utf-8" />
<meta name="viewport" content="width=device-width, initial-scale=1" />
<style type="text/css">
body {
background-color: #f0f0f2;
margin: 0;
padding: 0;
font-family: -apple-system, system-ui, BlinkMacSystemFont, "Segoe UI", " Open Sans", "Helvetica Neue", Helvetica, Arial, sans-serif;
}
div {
width: 600px;
margin: 5em auto;
padding: 2em;
background-color: #fdfdff;
border-radius: 0.5em;
box-shadow: 2px 3px 7px 2px rgba(0,0,0,0.02);
}
a:link, a:visited {
color: #38488f;
text-decoration: none;
}
@media (max-width: 700px) {
div {
margin: 0 auto;
width: auto;
}
}
</style>
Example Domain
This domain is for use in illustrative examples in documents. You may use this
domain in literature without prior coordination or asking for permission.
More information...
* Connection #0 to host example.com left intact
While when I try to reach install.pi-hole.net:
user@pihole:~ $ sudo curl -v -sSL https://install.pi-hole.net
Trying 164.90.255.4:443...
Immediate connect fail for 164.90.255.4: Network is unreachable
Closing connection 0
curl: (7) Couldn't connect to server
Oh, I accidentally got one step further:
When I manually browsed h ttps://install.pi-hole.net, I realized you are being forwarded to the script on Github, specifically the URL h ttps://raw.githubusercontent.com/pi-hole/pi-hole/master/automated%20install/basic-install.sh
So I substituted the URL in the Curl / Bash command so it is:
sudo curl -v -sSL h ttps://raw.githubusercontent.com/pi-hole/pi-hole/master/automated%20install/basic-install.sh | bash
And that did the trick and loaded the installer. Does the latest Pi OS have some sort of URL forwarding protection (since install.pi-hole.net forwards to github)?
[NOTE: I made h ttps out of https because the forum software thought I was posting links]
But it didn't go far - I then got an error that the Network is unreachable:
Okay, so obviously the Pi can't reach Github, which is weird!
It doesn't look like a Pi-hole problem – if you fix the network connectivity problem on your machine then you will be able to proceed.
What is your ISP maybe they block access to github?
the_LXZ
February 5, 2023, 11:38am
9
Interestingly, I can access github via my desktop PC so it has to be a Pi thing. Will continue to troubleshoot there.
What is your Pi's upstream DNS server? What's in your /etc/hosts
file?
system
Closed
February 26, 2023, 1:17pm
11
This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.