@dalu Have you tried with a clean build? No errors pop-up to me during tests.
Search Criteria
Package Details: nordvpn-bin 3.19.0-2
Package Actions
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: | 1.20 |
First Submitted: | 2018-08-29 12:13 (UTC) |
Last Updated: | 2024-10-03 15:24 (UTC) |
Dependencies (1)
- libxml2 (libxml2-gitAUR, libxml2-2.9AUR)
Required by (8)
- gnome-shell-extension-nordvpn-connect-git
- nordtray-bin (requires nordvpn)
- nordvpn-dinit
- nordvpn-openrc
- nordvpn-runit
- nordvpn-s6
- plasma6-runners-nordvpn (requires nordvpn)
- rofi-nordvpn-git
Sources (5)
- https://repo.nordvpn.com/deb/nordvpn/debian/pool/main/nordvpn_3.19.0_amd64.deb
- https://repo.nordvpn.com/deb/nordvpn/debian/pool/main/nordvpn_3.19.0_arm64.deb
- https://repo.nordvpn.com/deb/nordvpn/debian/pool/main/nordvpn_3.19.0_armel.deb
- https://repo.nordvpn.com/deb/nordvpn/debian/pool/main/nordvpn_3.19.0_armhf.deb
- https://repo.nordvpn.com/deb/nordvpn/debian/pool/main/nordvpn_3.19.0_i386.deb
Mxzcabel commented on 2024-10-04 20:35 (UTC)
dalu commented on 2024-10-04 15:20 (UTC)
(3/8) upgrading nordvpn-bin [#############################################] 100%
/tmp/alpm_rWRjVe/.INSTALL: line 22: [: =: unary operator expected
/tmp/alpm_rWRjVe/.INSTALL: line 22: [: =: unary operator expected
/tmp/alpm_rWRjVe/.INSTALL: line 22: [: =: unary operator expected
/tmp/alpm_rWRjVe/.INSTALL: line 22: [: =: unary operator expected
Kingaspore commented on 2024-09-21 14:16 (UTC)
Is this package bugged? Nordvpn.service seems to link to /dev/null after yay installation. I have dependencies, no idea why this would be happening on install.
apvanzanten commented on 2024-05-19 22:31 (UTC)
Heads up: It seems there are some issues with the firewall settings as per 3.18.1-1 ( a5489010120a), see https://github.com/NordSecurity/nordvpn-linux/issues/406
borw2024 commented on 2024-04-06 15:57 (UTC) (edited on 2024-04-08 14:32 (UTC) by borw2024)
Please disregard my question below, I fixed it another way. I'm now connecting to my dedicated NordVPN IP address through OpenVPN. I can do the same things I need as with the nordvpn client or cli, no issues speed-wise, it even seems to be 30-40% faster up and down. Maybe a today thing, can't verify that easily now. No DNS leaks afaict (https://www.dnsleaktest.com/results.html)and I can access the same functionality I used before.
=========================================================================
I rolled back to (pamac>aur) nordvpn 3.17.2-1 connected to nordlynx, no problems, fast and stable connection. Just tried to connect to udp (and tcp) to connect to my private ip address and bam, error connecting. Switching back to nordlynx, all is fine.
Steps taken from cli: nordvpn set technology openvpn nordvpn set protocol udp nordvpn connect nlxxxx (my server) nordvpn connect nl
result: Connecting to Netherlands nlxxxx The VPN connection has failed. Please check your internet connection and try connecting to the VPN again. If the issue persists, contact our customer support.
Then: nordvpn set technology nordlynx nordvpn connect nl
result: Connecting to Netherlands #881 (nl881.nordvpn.com) You are connected to Netherlands #881 (nl881.nordvpn.com)!
What am I missing? I'm far from a linux expert so I'm probably overlooking something. openvpn 2.6.9-1 and openvpn-update-resolv-conf-git are installed (pamac>aur).
Npa commented on 2024-04-06 00:43 (UTC) (edited on 2024-04-06 20:45 (UTC) by Npa)
hello everyone, I followed precisely the archlinux tutorial (https://wiki.archlinux.org/title/NordVPN#Setting_systemd-resolved_as_DNS_resolver) with wireguard-tools and systemd-resolvconf. Everything is ok except that if I start the VPN first Firefox is frozen (no startup) with nordlynx technology and openvpn.
On the other hand, if I open Firefox and then activate the VPN there is no longer a problem (closing FF, reopening...). This is beyond my skills.
If someone has an idea ? Thanks
EDIT 06/04/24 i stop and disable systemd-resolved.service, remove wireguard-tools and systemd-resolvconf and everything works fine again.
molasses2 commented on 2024-04-05 16:18 (UTC)
@mxzcabel, thank you for fixing this AND for the tip about systemctl restart systemd-resolved.service. I would not have thought of that.
linux-aarhus commented on 2024-04-05 11:22 (UTC) (edited on 2024-04-05 11:36 (UTC) by linux-aarhus)
If you setup your system using systemd-resolved then NordVPN will not leak dns.
https://wiki.archlinux.org/title/NordVPN#Setting_systemd-resolved_as_DNS_resolver
HotblackDesiato commented on 2024-04-05 06:34 (UTC)
Instructions for downgrade to version 3.17.2:
wget https://aur.archlinux.org/cgit/aur.git/snapshot/aur-e4dbfacf758c41a3514702d25779ececc18f1bf9.tar.gz
unp aur-e4dbfacf758c.tar.gz
mv aur-e4dbfacf758c nordvpn-bin-3.17.2
cd nordvpn-bin-3.17.2
makepkg
sudo pacman -U nordvpn-bin-3.17.2-1-x86_64.pkg.tar.zst
as root edit /etc/pacman.conf and add "nordvpn-bin" to IgnorePkg, to avoid update to 3.17.3.
Pinned Comments
Mxzcabel commented on 2023-03-23 20:37 (UTC) (edited on 2024-10-03 19:33 (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.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