MX Linux Forum

I added the delay to the init script following all the instructions in post #19, then rebooted. I also still get the whoops sock error when using "nordvpn c"

I can still restart service to make it work, which is my new normal way to get it to work.

Just sharing what works and what doesn't work for me, Jim.

Just wondering if there is a restart code option, so it does what you now do manually.

asqwerth wrote: Sun Nov 07, 2021 1:47 am @fehlix

I added the delay to the init script following all your instructions, then rebooted. I still get the whoops sock error.

I can still restart service to make it work but it doesn't work OOTB upon reboot.

jim8085 wrote: Sun Nov 07, 2021 8:54 am I added the delay to the init script following all the instructions in post #19, then rebooted. I also still get the whoops sock error when using "nordvpn c"

I can still restart service to make it work, which is my new normal way to get it to work.

Just sharing what works and what doesn't work for me, Jim.

@jim8085 , @asqwerth thanks for checking the delay hack, which seems only to work for me.
Hmm.. not sure whether we should try to fix NordVPN start-script and it's worth the effort as they probably might soonish provide their own fixed version, anyway. I'd say, let's wait and see whether next NorVPN update provides a fix or not.

fehlix wrote: Sun Nov 07, 2021 9:24 am Hmm.. not sure whether we should try to fix NordVPN start-script and it's worth the effort as they probably might soonish provide their own fixed version, anyway. I'd say, let's wait and see whether next NorVPN update provides a fix or not.

Following my yesterday's request, I got this answer this afternoon:

Hello,

Thank you for your response.

And we appreciate you for sharing your feedback.

We wanted to let you know, that our services do not work with sysvinit.

Our NordVPN software works on Linux with systemd only.

If you wish, you can enable systemd by following these steps on the official MX Linux website:
https://mxlinux.org/wiki/system/systemd/

Let us know if the issue still persists.

I install again, using MXPI->Pop.Apps->Network -> NordVPN and I see they remove nordvpn-sysvinit-compat_19.04.02 from
@dolphinoracle maybe we must wait update from this package

I tried the solution of @fehlix delay init script not work for me too, finally I back to nordvpn 3.11

The thing is there are similar comments on the latest nordvpn package version 3.12 (and 3.11) in Arch's AUR.

Read the latest comments here: https://aur.archlinux.org/packages/nordvpn-bin/

whoops sock message and all.

And Arch is systemd.

It would appear that there are some problems with the later versions of Nord, and it's not confined to sysV distros.

My Arch-based distro is currently on 3.11 and it doesn't connect at all, even though there is no error message.

If you can be interested in my other distributions based on arch I have solved by installing wireguard and wireguard tools and even the last release works perfectly there is to say however that adopt the systemd, on mx differently (sysvinit) I never had any problem only with a small expedient script on
~/.local/share/applications/nordvpn.sh I used to start from session and start in mx setting until the last release 3.12

In case manually restarting nordvpn would help, as mentioned already,
here a password less auto(re-)start of nordvpn daemon:

* first enable password less (re-)start of NordVPN daemon:
run this in terminal:
* next add an autostart entry for Xfce with delay, e.g. of 5 sec:
Within Session&Startup add new Entry:
Name: NordVPN
Comment: Restart NordVPN
Command: Note: you can add further commands semicolon separated like the one you have shown, e.g.
e.g. to add "nordvpn c" Works here for both inits: SysVinit and systemd.
+++EDIT+++; adjusted autostart command

Cristobal wrote: Sun Nov 07, 2021 10:51 am

fehlix wrote: Sun Nov 07, 2021 9:24 am Hmm.. not sure whether we should try to fix NordVPN start-script and it's worth the effort as they probably might soonish provide their own fixed version, anyway. I'd say, let's wait and see whether next NorVPN update provides a fix or not.

Following my yesterday's request, I got this answer this afternoon:

Hello,

Thank you for your response.

And we appreciate you for sharing your feedback.

We wanted to let you know, that our services do not work with sysvinit.

Our NordVPN software works on Linux with systemd only.

If you wish, you can enable systemd by following these steps on the official MX Linux website:
https://mxlinux.org/wiki/system/systemd/

Let us know if the issue still persists.

May I ask if you just emailed them at their support email? I will file a similar bug report to reinforce yours because version 3.12 doesn't work in Arch either, which uses systemd. It doesn't manifest exactly the same way as there is no error message and it appears to have connected successfully. However, no internet connection gets through at all once you connect. A stop and restart service does not help. I believe though that it must stem from the same bug in 3.12 because the source of the PKGBUILD for the Arch package is the 3.12 .deb file.

And at least in MX running under sysV, it does connect once you restart the service. So the claim that their application doesn't work with sysV just isn't true.

patongko wrote: Sun Nov 07, 2021 5:20 pm I install again, using MXPI->Pop.Apps->Network -> NordVPN and I see they remove nordvpn-sysvinit-compat_19.04.02 from
@dolphinoracle maybe we must wait update from this package

I tried the solution of @fehlix delay init script not work for me too, finally I back to nordvpn 3.11

I've been checking my MX18 and 19 installs. Nordvpn 3.11 never had the sysvinit-compat package installed, but it works OOTB anyway. It's nothing to do with that package.

Pinned version 3.11 in those installs for the moment.