MX Linux Forum

What is the latest on the Nordvpn bridge? Are we out of luck to use Nordvpn via pc interface for now? I mostly use Nordvpn through my router. I am helping someone else who can't cannect through Linux pc & doesn't have access to a customizable router.

galaxysurfer wrote: Mon Nov 15, 2021 1:04 am What is the latest on the Nordvpn bridge? Are we out of luck to use Nordvpn via pc interface for now? I mostly use Nordvpn through my router. I am helping someone else who can't cannect through Linux pc & doesn't have access to a customizable router.

(re-)starting of nordvpn service should work for latest version, as mentioned a couple of times within recent posts of this thread.

sorry if i didn't find the last post on matter when looking for solutions. Anyways I explained in another thread. Maybe it was due to you tweaking the nordvpn bridge or they fixed from their end? Either way keep up the great work!

fehlix wrote: Mon Nov 15, 2021 4:36 am (re-)starting of nordvpn service should work for latest version, as mentioned a couple of times within recent posts of this thread.

Your workaround to to make nordvpn service (re)start automatically upon reboot/fresh login does indeed work.

But I was using MX-KDE instead of XFCE, and the Plasma settings for autostart allows you to add only: a) application, b) login script or c) logout script.
so for the autostart entry, I made a .desktop file (ie, an "application") with the Exec entry as:
I didn't want to autoconnect, since I only connect when I want to.


Note: I actually first reverted your above changes and tried to do what @galaxysurfer and @CyberGhost did, ie login via the new
command, but when I used the provided browser link (in the terminal output) to re-login, the browser page simply indicated that I had been logged in, without the short **appearance of a fresh terminal with the nordvpn rotating "/" symbol indicating logging in was happening. When I then tried to connect in a terminal after that so-called login, it told me I wasn't logged in. I tried this in systemd and sysv, both told me I wasn't logged in after the browser page said I'd logged in successfully.

So I had to log in using the deprecated command, add your workarounds again, and reboot, and sure enough your workaround works to enable the service our of the box. I can then connect whenever I want to without any whoops sock error.


** I used the new login command in my Arch-based distros and when I entered my account name and password in the browser page and hit ENTER, a new terminal appeared during login (with the rotating "/") and disappeared when login was complete. After that, Nordvpn version 3.12 is now working upon connecting, instead of previously when internet was fully cut off upon connecting.

@fehlix , I'm wondering if under "normal" systemd, the browser is able to trigger the opening of a terminal which is not possible in sysvinit or MX's systemd.

asqwerth wrote: Tue Nov 16, 2021 8:08 am @fehlix , I'm wondering if under "normal" systemd, the browser is able to trigger the opening of a terminal which is not possible in sysvinit or MX's systemd.

AFAIK, it's possible to "talk" from Javascript to dbus, and dbus can trigger waiting/registed dbus services to perform actions and trigger systemd user-sevices, which includes starting of applications or running scrips etc. But surely I have no idea what they do within there new browser based login procedures.

Try now the new version 3.12.1 same bug nothing change!

patongko wrote: Thu Nov 18, 2021 5:26 pm Try now the new version 3.12.1 same bug nothing change!

It's working fine for me! I just upgraded to the newest version and I have SysVinit. Not real sure what's going on at your end.

the new version 3.12.1 works for me also

EDIT UPDATE: after reboot I still get...... Whoops! /run/nordvpn/nordvpnd.sock not found
This still is my normal way to get it to work. "sudo service nordvpn restart" then enter my password, then nordvpn c

patongko wrote: Thu Nov 18, 2021 5:26 pm Try now the new version 3.12.1 same bug nothing change!

Confirmed.
I still got this after upgrading to version 3.12.1 and reboot: Workaround as per post #29 with this autostart entry still needed when booting in SysVinit:

$HOME/.config/autostart/NordVPN.desktop

@fehlix

question 1:
are you able with this new version, to logout, and then login with the new command
question2:

In your much earlier post here: viewtopic.php?p=661237#p661237

you added a 3 sec delay to /etc/init.d/nordvpn: Now with there is a further 5 second delay.

So the total delay you are suggesting is 8 secs? (for what it's worth, I reduced the delay in /etc/init.d/nordvpn to 1 sec; I wasn't sure whether I supposed to delete the whole sleep line so I just reduced the number of secs)