DietPi version |
G_DIETPI_VERSION_CORE=6
G_DIETPI_VERSION_SUB=34
G_DIETPI_VERSION_RC=3
G_GITBRANCH='master'
G_GITOWNER='MichaIng'
Distro version | 10.7
SDcard used |
Software title | Dietpi-NordVPN
dietpi-Nordvpn menu popping up
nothing, openvpn is installed and running but the nordvpn setup/gui command doesn't exist
Hi,
Many thanks for your message. NordVPN could be open via dietpi-launcher > DietPi-NordVPN or directly /boot/dietpi/misc/dietpi-nordvpn
@Joulinar thank you, maybe update the after install message, closing this.
You need to first configure it, before the alias is available. It is only loaded if the service file has been created. But it does not make much sense to have the condition in this case. When it has not been "installed" yet, the script will recognise it and even offer you to install it right away. Hence I changed it: https://github.com/MichaIng/DietPi/commit/12052633fb99256ee695438f5c988cef8a62bba6
Sorry to be a pain but i'm getting issues DL server lists and connecting. Tested it on the app and no issues user/pass ok, not fw blocked.
Maybe NordVPN download server is not reachable. Did you try downloading the archive on you desktop computer?
Also try to run the command manually from console to get some more output:
curl -LO https://downloads.nordcdn.com/configs/archives/servers/ovpn.zip
Works fine here ๐ค.
curl: (28) Resolving timed out after 2000 milliseconds
can't resolve anything since i installed nordvpn
removing it again
Well NordVPN should not be online if you don't download the server archive. As well you could disconnect it if needed
curl: (28) Resolving timed out after 2000 milliseconds
Strange, default Linux DNS resolving timeout is 5 seconds with two attempts. Has this changed on your system? cat /etc/resolv.conf
weird, have no outside connection on my Dietpi atm, can't ping 9.9.9.9 can't resolve anything only have lan access it seems
cat /etc/resolv.conf
nameserver 127.0.0.1
nameserver 192.168.0.1
Checking network connectivity โ
โ - Command: ping -c 1 -W 10 9.9.9.9 โ
โ - Exit code: 1 โ
โ - DietPi version: v6.34.3 (MichaIng/master) | HW_MODEL: 3 | HW_ARCH: 2 | DISTRO: 5 โ
โ - Image creator: DietPi Core Team โ
โ - Pre-image: Raspbian Lite โ
โ - Error log: โ
โ PING 9.9.9.9 (9.9.9.9) 56(84) bytes of data. โ
โ โ
โ --- 9.9.9.9 ping statistics --- โ
โ 1 packets transmitted, 0 received, 100% packet loss, time 0ms
Inside your network you can ping anything? Like your router?
nameserver 127.0.0.1
Huh, do you have a local DNS resolver installed, Pi-hole or Unbound? Ah or is that the way how OpenVPN forces the NordVPN DNS server, with OpenVPN as local resolver?
Is NordVPN connection active currently or not? If not, remove the first line in /etc/resolv.conf. I'll check how OpenVPN applies the local DNS resolver.
So looking at my FW logs found a monitoring Pi like device doing some arp poisoning, stopped that and my DietPi can talk to the interwebs again. Also NordVPN is back in business, Closing this and will try to stop tinkering with my Pi till next year. Thanks everyone, xmas donation on the way!
Closing this and will try to stop tinkering with my Pi till next year.
At least if there is a chance that it causes stress. I'll take the pandemic lock-down Christmas/holidays to tinker even more with my devices, but only since nothing really depends on it ๐.
I just checked and OpenVPN does not touch /etc/resolv.conf. Generally, if that Pi serves as DNS resolver, e.g. via Pi-hole or Unbound, I'd not make it using it's own services. If Pi-hole and/or Unbound need to be updated, it could easily get stuck when shutting down its own resolver. Better to keep it using an upstream DNS, in case of VPN connection one from NordVPN. Now I'm wondering if/how that isn't done when connection via OpenVPN to NordVPN ๐ค. I'll play a bit more with it, but that's clearly OOT.
this is my status with vpn running, using the router as dns and my other Pihole
root@DietPi:~ dietpi-nordvpn status
Connected - Sent = 8 MiB | Received = 519 MiB
root@DietPi:~ cat /etc/resolv.conf
nameserver 192.168.0.1
nameserver 192.168.0.2
Looks like it's working, correct?