NordVPN keeps asking for password

VPN
1

I had Nord VPN setup via openvpn files imported into the vpn settings in network settings. This has been working for nearly 8 months.

For about 2 weeks I get asked to enter a password when I try and connect. I have entered my nord vpn password but the prompt keeps reappearing.

I can login to nord vpn’s site in a browser or connect via terminal.

Which password does it want? Why is asking for it, I have been using it for months without this issue.

​

https://preview.redd.it/6lcxsomjkeab1.png?width=480&format=png&auto=webp&s=0b9222bd3f0a9bb05a48950af62ecb9d6d7c01a8

I see the following error in my log:

“ERROR: could not read Auth username/password/ok/string from management interface”

2

I use NordVPN with Nordlynx and made an icon for it to connect and disconnect. Generated a token on their website. Filled the token in the script at the location and placed the script in /usr/local/bin. Made an .desktop file and placed it in /usr/share/applications. Placed the icon in the icon bar. The script uses Zenity to display a window to connect or disconnect. You can also run the script from the command line to see what the messages returned by NordVPN are if it is not connecting.

Script:

#!/bin/bash
vpnOnline=3
vpnStatus=$(nordvpn status)
if [[ $(echo ${vpnStatus} | grep -c Disconnected) -eq 1 ]]
then
  vpnStatus="Status: Disconnected\n\n<b>Connect</b> to VPN?"
  okLabel="Connect"
  vpnOnline=0
else
  vpnStatus="Status: Connected\n\n<b>Disconnect</b> from VPN?"
  okLabel="Disconnect"
  vpnOnline=1
fi

zenity --question --ellipsize --title="NordVPN" --default-cancel --ok-label="${okLabel}" --text="${vpnStatus}" --icon-name=nordvpn
case ${vpnOnline} in
  0) nordvpn login --token <Replace by Token>
     nordvpn connect
     ;;
  1) nordvpn disconnect
     ;;
esac

nordvpn-connect.desktop

[Desktop Entry]
Version=1.0
Type=Application
Name=NordVPN
Comment=Nordvpn, Connect/Disconnect message window.
Icon=nordvpn
MimeType=x-scheme-handler/nordvpn
Exec=/usr/local/bin/nordvpn.sh
Terminal=false
3

Thank you! I was running into the same issue, and using the service credentials from the manual setup it works again.