MX Linux Forum

fehlix wrote: Fri Nov 05, 2021 11:36 am Suggest this: you first remove NordVPN and install again, both steps by using MXPI->Pop.Apps->Network -> NordVPN. And logout/login or reboot.

System:    Host: <filter> Kernel: 4.19.0-6-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0 
           parameters: BOOT_IMAGE=/boot/vmlinuz-4.19.0-6-amd64 
           root=UUID=<filter> ro quiet splash 
           Desktop: Xfce 4.14.3 tk: Gtk 3.24.5 info: xfce4-panel wm: xfwm4 dm: LightDM 1.26.0 
           Distro: MX-19.4_x64 patito feo October 21  2019 base: Debian GNU/Linux 10 (buster) 
Machine:   Type: Laptop System: LENOVO product: 7469WEF v: ThinkPad X200s serial: <filter> 
           Chassis: type: 10 serial: <filter> 
           Mobo: LENOVO model: 7469WEF serial: <filter> BIOS: LENOVO v: 6DET72WW (3.22 ) 
           date: 10/25/2012 
Battery:   ID-1: BAT0 charge: 11.0 Wh condition: 11.8/28.8 Wh (41%) volts: 15.5/14.4 
           model: SANYO 42T4646 type: Li-ion serial: <filter> status: Unknown 
CPU:       Topology: Dual Core model: Intel Core2 Duo L9400 bits: 64 type: MCP arch: Penryn 
           family: 6 model-id: 17 (23) stepping: A (10) microcode: A0C L2 cache: 6144 KiB 
           flags: lm nx pae sse sse2 sse3 sse4_1 ssse3 vmx bogomips: 7447 
           Speed: 1818 MHz min/max: 800/1867 MHz boost: enabled Core speeds (MHz): 1: 1910 
           2: 1887 
           Vulnerabilities: Type: itlb_multihit status: KVM: Vulnerable 
           Type: l1tf mitigation: PTE Inversion 
           Type: mds status: Vulnerable: Clear CPU buffers attempted, no microcode; SMT disabled 
           Type: meltdown mitigation: PTI 
           Type: spec_store_bypass status: Vulnerable 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 mitigation: Full generic retpoline, STIBP: disabled, RSB filling 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: Intel Mobile 4 Series Integrated Graphics vendor: Lenovo driver: i915 
           v: kernel bus ID: 00:02.0 chip ID: 8086:2a42 
           Display: x11 server: X.Org 1.20.4 driver: intel resolution: 1280x800~60Hz 
           OpenGL: renderer: Mesa DRI Mobile Intel GM45 Express v: 2.1 Mesa 18.3.6 
           direct render: Yes 
Audio:     Device-1: Intel 82801I HD Audio vendor: Lenovo driver: snd_hda_intel v: kernel 
           bus ID: 00:1b.0 chip ID: 8086:293e 
           Sound Server: ALSA v: k4.19.0-6-amd64 
Network:   Device-1: Intel 82567LM Gigabit Network vendor: Lenovo driver: e1000e v: 3.2.6-k 
           port: 1840 bus ID: 00:19.0 chip ID: 8086:10f5 
           IF: eth0 state: down mac: <filter> 
           Device-2: Intel Ultimate N WiFi Link 5300 driver: iwlwifi v: kernel port: 1c60 
           bus ID: 03:00.0 chip ID: 8086:4236 
           IF: wlan0 state: up mac: <filter> 
           IF-ID-1: tun0 state: unknown speed: 10 Mbps duplex: full mac: N/A 
Drives:    Local Storage: total: 262.38 GiB used: 196.05 GiB (74.7%) 
           ID-1: /dev/sda vendor: Toshiba model: MK2561GSYN size: 232.89 GiB block size: 
           physical: 512 B logical: 512 B speed: 3.0 Gb/s rotation: 7200 rpm serial: <filter> 
           rev: 0C scheme: MBR 
           ID-2: /dev/sdb type: USB vendor: Ricoh model: R5U880FlashMedia size: 29.50 GiB 
           block size: physical: 512 B logical: 512 B serial: <filter> rev: 0000 scheme: MBR 
Partition: ID-1: / raw size: 11.72 GiB size: 11.47 GiB (97.90%) used: 7.94 GiB (69.2%) fs: ext4 
           dev: /dev/sda5 
           ID-2: /home raw size: 12.67 GiB size: 12.41 GiB (97.94%) used: 7.69 GiB (62.0%) 
           fs: ext4 dev: /dev/sda7 
           ID-3: swap-1 size: 1024.0 MiB used: 0 KiB (0.0%) fs: swap swappiness: 15 (default 60) 
           cache pressure: 100 (default) dev: /dev/sda6 
Sensors:   System Temperatures: cpu: 53.0 C mobo: 48.0 C 
           Fan Speeds (RPM): fan-1: 2216 
Repos:     No active apt repos in: /etc/apt/sources.list 
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://deb.debian.org/debian/ buster-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://deb.debian.org/debian/ buster main contrib non-free
           2: deb http://deb.debian.org/debian-security/ buster/updates main contrib non-free
           No active apt repos in: /etc/apt/sources.list.d/google-chrome.list 
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://nl.mxrepo.com/mx/repo/ buster main non-free
           Active apt repos in: /etc/apt/sources.list.d/nordvpn.list 
           1: deb https://repo.nordvpn.com/deb/nordvpn/debian/ stable main
           No active apt repos in: /etc/apt/sources.list.d/skype-stable.list 
           No active apt repos in: /etc/apt/sources.list.d/teams.list 
           No active apt repos in: /etc/apt/sources.list.d/various.list 
Info:      Processes: 208 Uptime: 4m Memory: 3.75 GiB used: 1.10 GiB (29.3%) Init: SysVinit 
           v: 2.93 runlevel: 5 default: 5 Compilers: gcc: 8.3.0 alt: 8 Shell: quick-system-in 
           running in: quick-system-in inxi: 3.0.36 

Cristobal wrote: Fri Nov 05, 2021 12:44 pm Same problem here.

fehlix wrote: Fri Nov 05, 2021 11:36 am Suggest this: you first remove NordVPN and install again, both steps by using MXPI->Pop.Apps->Network -> NordVPN. And logout/login or reboot.

I did try your method but the Nordvpn app only ran with systemd.

patongko wrote: Fri Nov 05, 2021 1:35 pm I try again with your method but the Nordvpn app only ran with systemd
in sysvinit Whoops! /run/nordvpn/nordvpnd.sock not found

patongko wrote: Fri Nov 05, 2021 1:35 pm I try again with your method but the Nordvpn app only ran with systemd
in sysvinit Whoops! /run/nordvpn/nordvpnd.sock not found

sudo service nordvpn restart

patongko wrote: Fri Nov 05, 2021 1:55 pm

Code: Select all

sudo service nordvpn restart
[sudo] password di mx: 
Restarting /usr/sbin/nordvpnd: nordvpnstart-stop-daemon: warning: failed to kill 2265: No such process

asqwerth wrote: Fri Nov 05, 2021 7:51 pm By the way, I get the same "sock" error message in Fedora (systemd) after an update of nordvpn via their rpm repos.

I do have to reinstall the package whenever that happens and re-enable the service with the appropriate systemctl command, then reboot.

So it may not be merely a sysv thing but a nordvpn thing.

Cristobal wrote: Sat Nov 06, 2021 3:23 am Indeed, after restarting twice, it eventually connected.

Code: Select all

$ sudo service nordvpn restart
[....] Restarting /usr/sbin/nordvpnd: nordvpnstart-stop-daemon: warning: failed to kill 2300: No such process
. ok 

nordvpn c

asqwerth wrote: Sat Nov 06, 2021 3:42 am

Cristobal wrote: Sat Nov 06, 2021 3:23 am Indeed, after restarting twice, it eventually connected.

Code: Select all

$ sudo service nordvpn restart
[....] Restarting /usr/sbin/nordvpnd: nordvpnstart-stop-daemon: warning: failed to kill 2300: No such process
. ok 

That message had no effect on the restart command, in the sense that after I ran the restart command ONCE, the first

Code: Select all

nordvpn c

after that got nordvpn up and running.

The only issue now I have is getting the service to be enabled all the time on bootup so I don't have to keep starting the service.

sudo sed  -i '/ start)/a\    sleep 3' /etc/init.d/nordvpn

venik212 wrote: Sat Nov 06, 2021 2:33 pm I had a similar problem with 3.12, and following the suggestion of the Nordvpn support, I removed all traces of the non-functioning version 3.12, and installed version 3.10, which works, but is invisible to the MX Linux package installer or Synaptic... ;-(

sudo service nordvpn stop

sudo sed  -i '/ start)/a\    sleep 2' /etc/init.d/nordvpn

sudo service nordvpn start

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.

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.

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.

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.

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

fehlix wrote: Tue Nov 09, 2021 7:15 am 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:

Code: Select all

echo "%users ALL=(root) NOPASSWD: /etc/init.d/nordvpn" | sudo sh -c 'umask 0337; tee /etc/sudoers.d/nordvpn'

* 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:

Code: Select all

sh -c "pidof -q nordvpnd && exit; test  -f /etc/init.d/nordvpn && sleep 5 && sudo /etc/init.d/nordvpn restart"

Note: you can add further commands semicolon separated like the one you have shown, e.g.
e.g. to add "nordvpn c"

Code: Select all

sh -c "pidof -q nordvpnd && exit; test  -f /etc/init.d/nordvpn && sleep 5 && sudo /etc/init.d/nordvpn restart; nordvpn c"

Works here for both inits: SysVinit and systemd.
+++EDIT+++; adjusted autostart command

asqwerth wrote: Tue Nov 09, 2021 11:25 am

fehlix wrote: Tue Nov 09, 2021 7:15 am 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:

Code: Select all

echo "%users ALL=(root) NOPASSWD: /etc/init.d/nordvpn" | sudo sh -c 'umask 0337; tee /etc/sudoers.d/nordvpn'

* 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:

Code: Select all

sh -c "pidof -q nordvpnd && exit; test  -f /etc/init.d/nordvpn && sleep 5 && sudo /etc/init.d/nordvpn restart"

Note: you can add further commands semicolon separated like the one you have shown, e.g.
e.g. to add "nordvpn c"

Code: Select all

sh -c "pidof -q nordvpnd && exit; test  -f /etc/init.d/nordvpn && sleep 5 && sudo /etc/init.d/nordvpn restart; nordvpn c"

Works here for both inits: SysVinit and systemd.
+++EDIT+++; adjusted autostart command

@fehlix can the first command be reversed if Nordvpn issues an update that works again? I'll be more comfortable testing this knowing how to reverse it.

For now, I made a launcher that runs a script with the simple sysV command to start the service. Terminal pops up, I enter password, then I run command to connect.

I don't connect with vpn all the time (e.g my wireless printer/scanner doesn't work with vpn on).

[Added] also, is the nordvpn deb file for MX21 the same as that for MX19? I have the 3.11 file in MX21 but had cleared the caches of my MX19 installs already.

pidof -q nordvpnd && exit;

apt policy nordvpn | head

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

nordvpn:
  Installed: 3.12.0-1
  Candidate: 3.12.0-1
  Version table:
 *** 3.12.0-1 500
        500 https://repo.nordvpn.com/deb/nordvpn/debian stable/main amd64 Packages
        100 /var/lib/dpkg/status
     3.11.0-1 500
        500 https://repo.nordvpn.com/deb/nordvpn/debian stable/main amd64 Packages
     3.10.0-1 500

asqwerth wrote: Tue Nov 09, 2021 11:25 am @fehlix can the first command be reversed if Nordvpn issues an update that works again? I'll be more comfortable testing this knowing how to reverse it.

sudo rm /etc/sudoers.d/nordvpn

asqwerth wrote: Tue Nov 09, 2021 11:57 am Sorry, @fehlix , I meant the command that seems to add nordvpn to sudoers file (I'm not exactly sure what it does but when I see "sudoers" I sit up). That looks like something I only want on a temporary basis. I can always remove the autostart entry.

%users ALL=(root) NOPASSWD: /etc/init.d/nordvpn

sh -c "pidof -q nordvpnd && exit; test  -f /etc/init.d/nordvpn && sleep 5 && pkexec /etc/init.d/nordvpn restart"

asqwerth wrote: Tue Nov 09, 2021 9:37 am
May I ask if you just emailed them at their support email?

asqwerth wrote: Tue Nov 09, 2021 9:37 am 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.

Cristobal wrote: Tue Nov 09, 2021 1:24 pm
I sent them an email on last Saturday, explaining that their app would work with sysvinit if restarted and that their developers should look into it.
....
I know, Nordvpn customer service's answer are always a bit off to me... The response usually arrives the day after and seems automated (as if they got it from a customer relationship management software).

venik212 wrote: Fri Nov 12, 2021 5:35 am Is there a compelling reason to "upgrade"? Version 3.10 seems to work just fine, although now it is unknown to MX Package manager, because I uploaded it using NordVPN's instructions-- wget... etc.

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.

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.

Exec=bash -c 'pidof -q nordvpnd && exit; test  -f /etc/init.d/nordvpn && sleep 5 && sudo /etc/init.d/nordvpn restart'

nordvpn login --nordaccount

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.

patongko wrote: Thu Nov 18, 2021 5:26 pm 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!

nordvpn c
Whoops! /run/nordvpn/nordvpnd.sock not found

[Desktop Entry]
Encoding=UTF-8
Type=Application
Name=NordVPN
Comment=Restart NordVPN
Exec=sh -c "pidof -q nordvpnd && exit; test  -f /etc/init.d/nordvpn && sleep 5 && sudo /etc/init.d/nordvpn restart"
RunHook=0
StartupNotify=false
Terminal=false
Hidden=false

asqwerth wrote: Fri Nov 19, 2021 6:50 am @fehlix

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

Code: Select all

nordvpn login --nordaccount

asqwerth wrote: Fri Nov 19, 2021 6:50 am question2:

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

you added a 3 sec delay to /etc/init.d/nordvpn:

Code: Select all

sudo sed  -i '/ start)/a\    sleep 3' /etc/init.d/nordvpn

Now with

Code: Select all

sh -c "pidof -q nordvpnd && exit; test  -f /etc/init.d/nordvpn && sleep 5 && sudo /etc/init.d/nordvpn restart"

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)

patongko wrote: Fri Nov 19, 2021 10:56 am For @fehlix
Thank you, your solution work for me in nordvpn 3.12.1
I guess it is not the last one for the next versions

CyberGhost wrote: Sun Nov 21, 2021 1:28 pm @hkjz , the first command is a password less entry auto(re-)start of nordvpn daemon that needs to be run in terminal. Type it in, press enter, and then close terminal. The second command is what you put in the command box in Session&Startup. The third command is the same command as the second, but with the option to auto connect upon login. That's the one I use. To do this, first go to Menu, then Settings, and scroll down until you see Session&Startup. Click on that and when it opens up, click on Application Autostart. There is a little plus icon (+) at the bottom right of the window. Click on that. In the first entry box that says Name, type: NordVPN. In the second box that says Description, type: Restart NordVPN. In the third box that says Command, type in either the second command @fehlix gave in order to restart the service without auto connecting, or use the third command to restart plus auto connect the service. Which command you use is up to you. As @asqwerth already mentioned. Also, reboot your computer after doing all of that. Check to see if it worked.You can type in terminal: nordvpn status. I suggest reading the #28 post @fehlix made about this again. viewtopic.php?t=67290&start=20 Hope this clarifies things for you! Good luck!

Cristobal wrote: Sat Apr 02, 2022 3:14 am I'd like to add some info that might help some users.

Since the new update, when trying to connect to nordvpn via the app, it provides a link to the nordvpn site where you have to enter your credentials. However, once logged in, in my case nothing happens (it said that I was 'in' on the webpage, but when typing 'nordvpn c' in terminal, it said I wasn't logged in, go figure).

After contacting the customer service (which was super responsive for once), they told me to type this command 'nordvpn login --legacy' which allowed me to log in.

asqwerth wrote: Sat Apr 02, 2022 5:06 am

Cristobal wrote: Sat Apr 02, 2022 3:14 am I'd like to add some info that might help some users.

Since the new update, when trying to connect to nordvpn via the app, it provides a link to the nordvpn site where you have to enter your credentials. However, once logged in, in my case nothing happens (it said that I was 'in' on the webpage, but when typing 'nordvpn c' in terminal, it said I wasn't logged in, go figure).

After contacting the customer service (which was super responsive for once), they told me to type this command 'nordvpn login --legacy' which allowed me to log in.

I already posted that tip in the previous page: viewtopic.php?p=671626#p671626

I suspect this is a systemd-dependent thing, because when done in Arch-based distros, the browser login will trigger the opening of a new terminal and text will show that login is completed and you can now go back to connecting to nordvpn the usual way. The new terminal then disappears.

Sensu commented on 2022-04-05 21:41 (UTC)

Please add xterm as a dependency to this. I was not able to sign with my nordvpn credentials until I installed xterm in my system.

asqwerth wrote: Sat May 07, 2022 12:09 am Just something new learned which explains why nordvpn running in MX was not able to complete the new login method (" nordvpn login --nordaccount"), forcing us to use the "--legacy" login instead. It has NOTHING to do with systemd vs sysvinit, but with the lack of xterm preinstalled on MX.

See this post from the AUR page https://aur.archlinux.org/packages/nordvpn-bin

Sensu commented on 2022-04-05 21:41 (UTC)

Please add xterm as a dependency to this. I was not able to sign with my nordvpn credentials until I installed xterm in my system.

I tested this in MX19. xterm was not installed. After installing, I logged out of nordvpn (legacy) and logged in again with the new login method. As previously described, it provides a link which you must open in browser and login from there. This time, with xterm installed, the little terminal does pop open after you enter your account name and password (like I reported happened in Manjaro/Arch-based distros), and after some "working" symbols within, you are logged in, the terminal disappears, and you get a message on the browser page that you are logged in. From there, go back to terminal to connect.


@fehlix @Stevo , request that we add xterm as a dependency to the package or the .pm file in MXPI, or however you all do it.


Thanks.