There is mistake at line number 26
bsdtar -O -xf *.deb data.tar.xz | bsdtar -C "${pkgdir}" -xJf -
there should be data.tar.gz
Git Clone URL: | https://aur.archlinux.org/nordvpn-bin.git (read-only, click to copy) |
---|---|
Package Base: | nordvpn-bin |
Description: | NordVPN CLI tool for Linux |
Upstream URL: | https://nordvpn.com/download/linux/ |
Keywords: | networking nordvpn openvpn security vpn |
Licenses: | GPL3 |
Conflicts: | openvpn-nordvpn |
Provides: | nordvpn |
Submitter: | metiis |
Maintainer: | Mxzcabel |
Last Packager: | Mxzcabel |
Votes: | 168 |
Popularity: | 0.98 |
First Submitted: | 2018-08-29 12:13 (UTC) |
Last Updated: | 2024-11-21 01:21 (UTC) |
« First ‹ Previous 1 .. 18 19 20 21 22 23 24 25 26 27 28 .. 54 Next › Last »
There is mistake at line number 26
bsdtar -O -xf *.deb data.tar.xz | bsdtar -C "${pkgdir}" -xJf -
there should be data.tar.gz
@sylvite I tried it, but when restore it runs but never finish, I have to stop it with CTRL+Z, and it does nothing.
@esdaniel It can't connect (no error, it endless run but does nothing), but nordvpnd is running.
I also tried stoping nordvpnd and restart it without succes. I always have to reboot.
Sometimes it runs after suspend, sometimes not...
A lot of times when I have no connection it's because nord left the iptables in a broken state. What I've done is sudo iptables-save
to a file (once only) right after a clean reboot before interacting with nord, when I have connectivity. Then when nord gets in this state, do a sudo iptables-restore
from that file before using nord. Has saved me from rebooting many times.
@ledom05 as nordvpn won't maintain 'stale' connections when you sleep your computer, when you resume your computer just try: nordvpn c
to reconnect to nordvpn service. Hope that works for you. If you wish to have internet access and not connect with nordvpn, after resume then run nordvpn d
Nordvpn stop working and breaks wifi connection after suspend.
Each time I suspend iwth nordvpn connected, after wake up I have no internet connection. Stoping or restarting nordvpnd does not solve the problem. I have to restart my computer.
@gary9872 Same here on the Nordlynx support. That would be a great upgrade to this package! Otherwise working perfectly with OpenVPN.
Killswitch is not working for me.
Thanks for the package.
OpenVPN seems to work fine. Nordlynx is a mixed bag. Nordvpn won't help much because it's on Arch system. If anyone knows how to make Nordlynx reliable, let me know..
@hydra Thanks!
I accidentally deleted, my previous comment, so reposting... DIY patch, change the appropriate PKGBUILD lines to:
pkgver=3.8.10
sha256sums_x86_64=('e27ba637dffc766b99161805f525b87716c8d36186d09abea61f6094af87a9fe')
sha256sums_i686=('94a796e1fe719f89519a30ffe65b558ae9aa580c3e8ae2761ba763ac25c27e2b')
sha256sums_armv7h=('f19fd4c5ec6cadde082669eccc23fe9238060f6263e89244a43c04aff7ca3d3c')
sha256sums_aarch64=('e357c7c7f3ca6411605fc4601361bd05fd6202b09057f3dc1ddeb65d5dc1a45f')
Pinned Comments
Mxzcabel commented on 2023-03-23 20:37 (UTC) (edited on 2024-11-21 01:57 (UTC) by Mxzcabel)
"Please, do not flag this package as out-of-date until there's the official release on Github page."
"Maybe the announcement is delayed, but wait for some other possible forward release, which is patching the previous one before the actual publishing."
Note from 3.19.1:
The repository's hierarchy has been updated and a slightly divergence comes with it. It was from:
/debian/pool/main
To now as:
/debian/pool/main/n/nordvpn
Any previous commits you may like to try in the future will need a manual mediation to replace old links in favor of the new ones.
Note from 3.19.0:
This version introduces new libraries being used by NordVPN. I have created symbolic links and committed a patch for it not interposing with already existing libraries (like sqlite3). Although this is not a big deal, If you, however, upgraded nordvpn-bin before the fix and noticed some library-related issue from sqlite lately, I suggest reinstalling the affected package.
Note from 3.17.4v:
The previous bug exposing DNS servers is fixed.
Note from 3.17.3v:
Caution! This version needs heed while using it and should be avoided. I strongly advice downgrading to 3.17.2 and wait for a new version or patching. Some big problems are:
There's DNS leak present. Your original ISP servers can be exposed, as reported already on #343 issue.
Unable to connect on nordvpn servers. Your journal might show the follow output:
networker setting dns: setting dns with resolvectl: setting dns with resolvectl: Failed to set DNS configuration: Could not activate remote peer: activation request failed: unknown unit.: exit status 1
Also huge thanks for the community warnings in prior comments before I could've noticed all.
Note from 3.16.2v:
As the published note from the version above has mentioned on Github's page:
Please, consider using a token to logging in from now on.
Note from 3.16.0v:
The 'countries.dat' may differ between versions. Be aware to remove the file before upgrading the package.
martoko commented on 2020-12-20 09:10 (UTC) (edited on 2020-12-20 09:12 (UTC) by martoko)
If you're seeing the message "Daemon is unreachable, is systemd running?", then one of two things is probably happening.
The nordvpn daemon might not be started
Start it using:
sudo systemctl enable --now nordvpnd
You might not have been added to the nordvpn group
Add yourself:
sudo gpasswd -a USERNAME nordvpn
And then restart in order for the group to be created:
reboot