Issue installing PiVPN #4503
Comments
|
Hi, many thanks for your message. We had a similar case in past where the issue was slow DNS resolution. At least your error message looks similar to #4061 Can you do a simple test |
|
here are the results |
|
That worked well. The log above already shows that the correct IP was found in the first attempt, and in the retry it was found in cache immediately, so the connection itself timed out, not DNS. Let's check if it is somehow curl explicitly: I just tested a survey upload, and our SSH/SFTP server responds quickly here, so that is not the issue. Btw, you said you tried to install PiVPN but the error our posted is about the bug report upload. Do you still have the log or remember which connection initially failed, like downloading the PiVPN installer or so? |
|
here are the results I don't have the log and I don't remember which connection failed. I can try again if that would help |
|
Ah I forgot to add the
Yes, please do that, as it might have been a temporary network issue. |
|
I'm not sure how to get the logs but this what I got when I retried it.
I can also try that curl request again with the time command. I just don't know how |
|
Just prefix it with |
|
|
Stange, so indeed it was when downloading the PiVPN installer, respectively when connecting to its server. We can retry the exact same time curl -IL https://install.pivpn.iobut I have a feeling that it succeeds (in below 5 seconds) like the dietpi.com connection does, so that it is somehow in the context of the script. The timeout of the URL check can be increased: G_CONFIG_INJECT 'CONFIG_G_CHECK_URL_TIMEOUT=' 'CONFIG_G_CHECK_URL_TIMEOUT=30' /boot/dietpi.txtThis may work around the issue, but leaves the open question why the connection takes so long or fails during the |
|
It looks like it took over 3 mins |
|
Strange, here it takes 0.5 seconds, so not a general server issue. Does it work normally to open this URL in your browser (showing the shell script code)? The URL actually is redirected to the raw file from the master GitHub branch. Does this work better? We could pull the installer from there directly and skip the prior |
|
I'm able to go to install.pivpn.io in my browser just fine. |
|
Do you use something like PiHole or AdGuard? |
|
... or NextDNS. If so, please try to add |
|
ahh, yes. I use PiHole. I'll try and disable it and try again. but this is still taking a while |
|
Could you check which blocklist is responsible for While I'm not sure about sed -i 's|install.pivpn.io|raw.githubusercontent.com/pivpn/pivpn/master/auto_install/install.sh|' /boot/dietpi/dietpi-software |
|
I tried searching the web GUI and the command line and both resulted in |
|
Maybe it took time to resolve the host name first, which is cached now. Maybe you can have a look to the query log for the url |
|
Strange. Probably not a blocklist is the issue but Pi-hole or Unbound behind it, if you have both installed? On the other hand, for time getent hosts install.pivpn.ioDoes Pi-hole and in case Unbound report any error? journalctl -u pihole-FTL -u unbound | tail -20
tail -20 /var/log/pihole.log
tail -20 /var/log/pihole-FTL.log |
|
|
Okay that looks all fine. Let's also have a look into the kernel logs, just to rule it out: dmesg | tail -20Btw, if Pi-hole is running on the same server, I'd generally not have that server using Pi-hole as well, so it cannot break its own DNS resolver when Pi-hole or Unbound fails, is stopped or upgraded and such. As you usually do not use a browser on that system (if it is a pure server), there is not really a reason to block ads, also since Linux does not do various in-transparent connections home 🙂. E.g.: sed -i 's/dns-nameservers 127.0.0.1/dns-nameservers 9.9.9.9/' /etc/network/interfacesto switch to Quad9 DNS and by this rule out Pi-hole and Unbound for this issue. And to not forget the workaround to allow PiVPN install: sed -i 's|install.pivpn.io|raw.githubusercontent.com/pivpn/pivpn/master/auto_install/install.sh|' /boot/dietpi/dietpi-software |
|
I do have pihole running on a different raspberry pi but the pi i'm currently trying to install pivpn on is also running a web server. Do you think that could be what is causing the issue. Should I use a dedicated pi just for the pivpn? I put all those inputs into the raspberry pi running pihole |
|
usually there should be no issue running both on one system. Can you try to install PiVPN again pls as you changed the install link now. |
|
|
|
your device have quite some issues to connect to the web
Are you using WiFi or Ethernet? |
|
ethernet. |
|
maybe restart your router? |
|
I was able to get it installed!!! Thank you so much for your help. You friends are doing awesome work and I appreciate everything you do |
|
Maybe you like to share the final solution 😉 |
This seemed to resolve the issue |
|
ok, I'm going to close the issue as it seems to be solved. Feel free to reopen if needed. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello,
I'm a complete noob when it comes to linux and things. I'm just trying to install PiVPN and I keep getting this error. I'm not sure how to fix and the googling I did do didn't give me any helpful results
Details:
curl --connect-timeout 8 --retry 1 --retry-delay 4 -sSvT ed796366-423d-428c-96dc-36b8ca8fd71c.7z XXXXSteps to reproduce:
Expected behaviour:
Actual behaviour:
Extra details:
Additional logs:
The text was updated successfully, but these errors were encountered: