I can't seem to connect to nordvpn.
The last successful command was login. Then, anything else yields this:
Whoops! Something went wrong. Please try again. If the problem persists, contact our customer support.
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: | 172 |
Popularity: | 0.74 |
First Submitted: | 2018-08-29 12:13 (UTC) |
Last Updated: | 2025-05-09 18:47 (UTC) |
« First ‹ Previous 1 .. 44 45 46 47 48 49 50 51 52 53 54 .. 57 Next › Last »
I can't seem to connect to nordvpn.
The last successful command was login. Then, anything else yields this:
Whoops! Something went wrong. Please try again. If the problem persists, contact our customer support.
@Ubermensch - I ran into the same issue (on GalliumOS in my case), and ultimately just uninstalled and reinstalled via apt. Some of the non-reinstallation options have worked in the past but this time around seemed to require the reinstall
I report frequently "Whoops! Cannot reach User Daemon." error message when i use nordvpn command. Removing ~/.config/nordvpn/ don't fix it
I get the issue "systemclt" is the alias of "sudo systemctl" in Antergos linux. https://bit.ly/2PZV25R
Anyone else having issue whitelisting ports for access on the local lan?
nordvpn whitelist add port 1234
transport is closing
or Whoops! Cannot reach User Daemon.
Both nordvpnsd
and nordvpnud
are showing as running
.
EDIT: fixed by removing ~/.config/nordvpn/
and reconfiguring.
Hey everyone! For some reason outgoing traffic halts when I connect to a server:
nordvpn c ireland dublin
:
Connecting to Ireland #21 (ie21.nordvpn.com)
You are connected to Ireland #21 (ie21.nordvpn.com)!ping google.com
returns nothing, my connection goes down.I checked the service logs (through journalctl), looks ok. Only a couple of lines that say "kernel reports TIME_ERROR: 0x2041: Clock Unsynchronized" but after a quick search on google it seems to be unrelated.
Any ideas?
System:
Manjaro 18.0.4
Kernel 4.14.93-rt53-MANJARO
NordVPN Version 3.0.0-4
I can't uninstall nord-vpn package
# pacman -Rcns nordvpn-bin
checking dependencies...
:: inxi optionally requires net-tools: inxi -i ip lan-deprecated
Packages (2) net-tools-1.60.20180212git-1 nordvpn-bin-3.0.0_4-1
Total Removed Size: 38.48 MiB
:: Do you want to remove these packages? [Y/n]
:: Processing package changes...
error: cannot remove file '/var/lib/nordvpn/data/insights.dat': Operation not permitted
(2/2) removing net-tools [######################################] 100%
:: Running post-transaction hooks...
(1/2) Reloading system manager configuration...
(2/2) Arming ConditionNeedsUpdate...
Upd. chattr -i /var/lib/nordvpn/data/insights.dat; chattr -i /var/lib/nordvpn/data/servers.dat
did the trick
Apparently the killswitch does not work at all in my case. It does not cut the internet connection when disconnected. I'm using Antergos linux. Any idea?
How can we choose between countries normal/P2P/Double/TOR? When I try to connect to Netherlands it picks the onion server by itself. Also, the man page says something about groups. What is that? I cannot find any reference to groups, apart from the 3 examples in the man page.
Warning: the systemd unit files included in this package give NordVPN full access to your entire system. Adding sandboxing options in the [Service]
section of each systemd service file can reduce the security risks.
For example the following options can be added in nordvpnsd.service
:
NoNewPrivileges=true
ProtectSystem=strict
ReadWritePaths=/var/lib/nordvpn /var/log/nordvpn
TemporaryFileSystem=/run
ProtectHome=true
PrivateTmp=true
ProtectKernelModules=true
ProtectControlGroups=true
InaccessiblePaths=/mnt
SystemCallFilter=@system-service
SystemCallErrorNumber=EPERM
See man systemd.exec
for details.
Pinned Comments
Mxzcabel commented on 2023-03-23 20:37 (UTC) (edited on 2025-05-12 22:12 (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.20.2-4
Dependency included as mandatory earlier as community request.
If you're late for the party and only had updated up to 3.20.2-2.1:
If you're coming from Manjaro or e.g another Arch-based distro with no stable libxml2-legacy package just yet:
Note from 3.20.2-3
There is now a new package from official repositories named libxml2-legacy and with it two fresh considerations:
Despite the fact libxml2-legacy was included as optional, it is actually a mandatory dependency. This will change on next NordVPN's release if the legacy support remains.
This release only removes the previous symbolic link and purges the file within NordVPN library directory, otherwise it would result in an error before installation/upgrade.
Note from 3.20.2-2.1
A patch have been implemented due the absence of libxml2.so.2 after package upgrade to 2.14.2. This fix is not useful if:
You plan to keep your system update to a specific date until NordVPN officially uses the new library.
You are from a different distribution, which is a Arch-based one with other repositories, and libxml2 is not yet upgraded.
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