Was getting the "Whoops! We couldn't connect you' error, even after logout/login.
A reboot is necessary to load the new kernel and modules after the running kernel has been updated using pacman. After reboot, Nordvpn-bin works again.
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.88 |
First Submitted: | 2018-08-29 12:13 (UTC) |
Last Updated: | 2024-11-28 13:50 (UTC) |
« First ‹ Previous 1 .. 29 30 31 32 33 34 35 36 37 38 39 .. 54 Next › Last »
Was getting the "Whoops! We couldn't connect you' error, even after logout/login.
A reboot is necessary to load the new kernel and modules after the running kernel has been updated using pacman. After reboot, Nordvpn-bin works again.
I am still getting the "Whoops! We couldn't connect you..." error when using both OpenVPN and NordLynx. I have tried logging out and restarting the service. I have the optional wireguard packages installed. I also get "A new version of NordVPN is available! Please update the application." Whenever using any command.
@andryandrew thanks for the solution.
Confirmed logging out/logging in fixes the connection issue after updating to 3.7.0. Previously, if this was necessary the app would notify you to do so, which didn't happen this time.
I had connection problems when installing the latest version (3.7.0). Fixed them by logging out and in again
Having the same problem as aslan00 and others
Edit: not anymore
I have the same problem of nasdack, I have update the package and I'm unable to connect to any server. I have unistalled the package, reboot the system, changed connection settings switching from OpenVPN and Nordlinx, and UPD/TCP but nothing works, I always get the message :
Whoops! We couldn't connect you to "anyserver". Please try again. If the problem persists, contact our customer support.
@ABOhiccups Auto-Connect doesn't work with NetworkManager on NordLynx. The nordvpnd.service needs an additional dependency: 'Wants=network-online.target'.
NordLynx won't auto-connect after login to XFCE Desktop. I have to connect manually.
Nordlynx won't work. But, OpenVPN does work.
NordLynx and Openvpn technologies appear to be working now again after the update to nordvpn-bin was added to the AUR repo. I did have to restart and re-enable the nordvpnd service. Thanks!
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