Username or password is not correct. Please try again.

[4others]

Hi!
I've been using image: ghcr.io/bubuntux/nordvpn:v3.10.0-1-1 for quite a while now, but just today started observing weird behavior there.

It still rarely works, but initially (till 11:00:00 CEST roughly) produced an error:

It's not you, it's us. We're having trouble reaching our servers. If the issue persists, please contact our customer support.

However it changed and produces this one now:

Username or password is not correct. Please try again

Both password and username are OK, last successful connection was established around 160m ago, before 3PM CEST.

Any suggestions how could I keep it running on this image or do I need to use the newest version instead?

Note: the app I use runs in Kubernetes, so current https://github.com/bubuntux/nordlynx cannot solve the issue.

[trablin45]

Im having the same issue, I had multiple containers using "latest" of this image, everything was working fine until saturday. Today I wasn't able to ssh to the container, it was in a endless reboot. I deleted everything,even images, net interfaces and recompose. The checked on portainer logs and found this
[services.d] starting services [services.d] done. A new version of NordVPN is available! Please update the application. Logging in via ‘--legacy’, ‘--username’, and ‘--password’ flags is deprecated. Use ‘nordvpn login' or ‘nordvpn login --nordaccount’ to log in via browser. Alternatively, you can use ‘nordvpn login --token’ to log in with a generated token. We couldn't log you in. Make sure your credentials are correct. If you have MFA enabled, log in using the 'nordvpn login' command. Invalid Username or password. [cmd] /bin/sh exited 1 [cont-finish.d] executing container finish scripts... [cont-finish.d] done. [s6-finish] waiting for services. [s6-finish] sending all processes the TERM signal. [s6-finish] sending all processes the KILL signal and exiting.
Legacy login is not longer supported? So this container is officially dead now?

[4others]

Oh, so it's the same with the latest one too? What is the sha of the image you're using?

[fuzzaldrin]

Had the same issue, it looks like Nord have changed the login/auth process. I tried generating a token in the Nord dashboard and using that with the TOKEN env var but that doesn't work either. Based on the Dockerfile it looks like it doesn't actually pass the TOKEN to the NordVPN client but this could be potentially fixed. I'll see if I can get it working.

[jamiejones1997]

I am able to connect with the newest image, i.e. 28b8e88d337a, with the TOKEN specified. It is not possible to specify one for the version I use normally, as the client is too old I presume...

Is that using the NordLynx technology?

[4others]

It says so, but unfortunately I made a mistake saying it can connect, it does not do it, even though the prompt says so.

[fuzzaldrin]

This works for me but did require a little faff and does require Wireguard to be installed on the host: https://github.com/bubuntux/nordlynx

[4others]

Sounds great! Unfortunately I cannot afford that - need to have a module too, not only tools (https://www.wireguard.com/install/) :/

[jamiejones1997]

I've ended up just paying for surfshark instead and using this https://github.com/ilteoood/docker-surfshark

Worked without any issues, took a few mins to migrate my other containers over to use it but still less hassle than getting the nordlynx working with wiregaurd

[jarlbrak]

Spent a few days trying to get the new https://github.com/bubuntux/nordlynx working with my environment. I got the container itself to connect but none of the other docker containers can access it. Tried to go back to what worked before and now I stumble upon this issue... Very annoying. Any fixes?

[fuzzaldrin]

Did you map the ports of the other containers to the VPN container in the same way as you would have for the old container?

vpn:
  container_name: vpn
  image: ghcr.io/bubuntux/nordlynx:2023-04-01
  cap_add:
    - NET_ADMIN #required
  environment:
    - PRIVATE_KEY=[super-secret-key-here] #required
    - PERSISTENT_KEEP_ALIVE=30
    - NET_LOCAL=192.168.0.0/24
    - QUERY=filters\[country_id\]=227 #UK Servers 
    #- RECONNECT=15
    - TZ=Europe/London
  ports:
    - 9696:9696               # prowlarr
    - 9117:9117               # jackett
    - 6789:6789               # nzbget
    - 6881:6881               # rtorrent
    - 3001:3001               # flood
    - 9091:9091               # transmission
  sysctls:
    - net.ipv6.conf.all.disable_ipv6=1

[jarlbrak]

Yep, got all of that the same. I'm on a Synology box so maybe there is some bug there...

[fuzzaldrin]

Are you using the API key generated in the NordVPN console in the PRIVATE_KEY field?

[jarlbrak]

Yep, it's connected to the endpoint, I just never receive any packets back.

Edit: sorry confusing this with the NordLynx container which doesn't work for me either.

It appears there is a PR here that could fix the issue.

[PhamineXL]

Adding to this thread. Anyone find a fix to this issue as of yet?

`[2023-04-28T21:11:44-04:00] Firewall is up, everything has to go through the vpn
[2023-04-28T21:11:44-04:00] Enabling connection to secure interfaces
[2023-04-28T21:11:44-04:00] Enabling connection to nordvpn group
iptables: No chain/target/match by that name.
[2023-04-28T21:11:44-04:00] group match failed, fallback to open necessary ports
[2023-04-28T21:11:44-04:00] ip6 group match failed, fallback to open necessary ports
[2023-04-28T21:11:44-04:00] Enabling connection to docker network
[2023-04-28T21:11:44-04:00] Enabling connection to network 192.168.1.163/24
Error: Invalid prefix for given prefix length.
[2023-04-28T21:11:44-04:00] Restarting the service
[2023-04-28T21:11:44-04:00] Waiting for the service to start
[2023-04-28T21:11:44-04:00] Logging in

|

Username or password is not correct. Please try again.
[2023-04-28T21:11:45-04:00] Invalid Username or password.`

[jamiejones1997]

Yeah, just move over to this https://github.com/qdm12/gluetun

https://github.com/qdm12/gluetun/wiki/NordVPN

It has a nordvon option, I went to it after using surfshark for a few days ands it's brilliant. The reconnect also works perfectly

[karlitros]

Mate thanks SO much for suggesting this. Took hardly any time to set up with port mapping, and works like a dream!