NordVPN

[scaw]

I got this all set up 3 days ago, including changing the subnet. It was all working until last night it suddenly stopped with nothing able to fix it. Turning the docker on leads to a long wait where it tries to talk to NordVPN and ends with the message "Unable to connect." in the logs before closing the docker instance.

 

I've tried changing the country, switching from NordLynx to OpenVPN, and totally reinstalling the docker, but nothing is working. I have no clue why it set up just fine originally and then suddenly crashed hard.

 

It seems like a lot of people are having trouble connecting. Did anyone manage to figure out a solution to this?

[MrCTS]

I seem to be having a similar issue to @scaw.  

 

[2021-09-06T15:20:17-04:00] Firewall is up, everything has to go through the vpn
[2021-09-06T15:20:17-04:00] Enabling connection to secure interfaces
[2021-09-06T15:20:17-04:00] Enabling connection to nordvpn group
[2021-09-06T15:20:17-04:00] Enabling connection to docker network
[2021-09-06T15:20:17-04:00] Enabling connection to network 192.168.1.0/24
[2021-09-06T15:20:17-04:00] Restarting the service
[2021-09-06T15:20:17-04:00] Waiting for the service to start
[2021-09-06T15:20:17-04:00] Logging in
[2021-09-06T15:20:19-04:00] Setting up NordVPN Version 3.10.0

CyberSec is set to 'enabled' successfully.
The command you entered is not valid. Enter 'nordvpn set dns --help' to see the options.
Technology is successfully set to 'NordLynx'.
Subnet 172.17.0.0/16 is whitelisted successfully.
Subnet 192.168.1.0/24 is whitelisted successfully.
[2021-09-06T15:20:19-04:00] Connecting...
If nothing happens, please visit https://join.nordvpn.com/order/?utm_medium=app&utm_source=linux
If nothing happens, please visit https://join.nordvpn.com/order/?utm_medium=app&utm_source=linux
If nothing happens, please visit https://join.nordvpn.com/order/?utm_medium=app&utm_source=linux
If nothing happens, please visit https://join.nordvpn.com/order/?utm_medium=app&utm_source=linux
If nothing happens, please visit https://join.nordvpn.com/order/?utm_medium=app&utm_source=linux
If nothing happens, please visit https://join.nordvpn.com/order/?utm_medium=app&utm_source=linux
If nothing happens, please visit https://join.nordvpn.com/order/?utm_medium=app&utm_source=linux
If nothing happens, please visit https://join.nordvpn.com/order/?utm_medium=app&utm_source=linux
If nothing happens, please visit https://join.nordvpn.com/order/?utm_medium=app&utm_source=linux
If nothing happens, please visit https://join.nordvpn.com/order/?utm_medium=app&utm_source=linux

 

 

Every once in a while in the console when issuing status and connect commands (the actual nordvpn status/nordvpn connect commands) I get the account active but an error message stating that my account subscription has expired.  I'm leaning towards more of a Nord issue than a docker issue myself but thats just my gut feeling.

[scaw]

FWIW my logs look identical to @MrCTS. I haven't seen the "account subscription expired" message though. I also tried resetting my password as suggested in the thread at https://github.com/bubuntux/nordvpn/issues/227 but no dice.

 

After the logs posted above happen, a bunch of stuff gets spit out at once and the docker instance closes; the most relevant seeming part of that dump seems to be

 

2021/09/06 16:33:18 Get "https://os4work.com/v1/users/services": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
2021/09/06 16:33:18 [Error] listing services: rotating domain: ptr timer is locked

 

Edited September 6, 2021 by scaw
Formatting

[scaw]

Sorry to double post; I was able to get things working using the container at https://hub.docker.com/r/azinchen/nordvpn. I just set up a new container in docker and added the required keys, and it's chugging along nicely (using openvpn). Hopefully the bubuntux container gets fixed soon and I can go back to the much faster NordLynx!

[22Casper]

Hi, 

I have the exact same issue as well, anyone knows if this is fixed? Also I tried setting up a new container in docker to use with openVPN but I get the same exact error. Everything was fine till couple days ago.

thanks!

[cpu]

Works fine in bridge mode instead of br0. It might be workaround for some folks 🙂

[MrCTS]

7 hours ago, cpu said:

Works fine in bridge mode instead of br0. It might be workaround for some folks 🙂

Mine has always been in bridge mode since day 1.  

However over on the github page, we've managed to figure out that its not on bubuntux end.  Nord has actually taken the blame for it and owning that it is on their end of things.

[Joggel]

On 8/17/2021 at 12:34 PM, dellorianes said:

Hi,

I am having a problem at the moment of setting up Oscam container, running through nordvpn app.

 

When I try to define the container ports in Oscam docker, I can not map 9000 (dvbapi port, needed by tvheadend to connect with it).

 

Running Oscam alone (custom network), port 9000 is mapped correctly, but when running through nordvpn it does not appear mapped in unraid docker´s webpage. Only 8888 (webui) appears as mapped 🙂8888/TCP <->:8888). 

 

I have also JDownloaded setup to connect through nordvpn with 3 different ports openned with no issues.

 

Any idea?

Hi, 

 

i am having the exact same problem. Did you find any fix or workaround ?

[pika]

my docker won't connect anymore:

[2021-09-15T19:38:54+02:00] Waiting for the service to start
[2021-09-15T19:38:54+02:00] Logging in
[2021-09-15T19:38:56+02:00] Setting up NordVPN Version 3.10.0
CyberSec is already set to 'disabled'.
DNS is already set to '1.0.0.1, 1.1.1.1, 8.8.8.8'.
Technology is already set to 'NordLynx'.
Subnet 172.17.0.0/16 is whitelisted successfully.
Subnet 192.168.0.0/24 is whitelisted successfully.
[2021-09-15T19:38:57+02:00] Connecting...

stays like this and nothing more happens 

[chantekka]

On 8/25/2021 at 3:05 AM, evertinker said:

 

I had the same problem and finally realized I wasn't reading the nordvpn container's NETWORK variable closely enough (under 'more settings'). The default LAN it specifies is 192.168.0.0/24 and my LAN is 192.168.1.0/24

As soon as I changed it I could access lidarr through the web ui. I hope this easy change works for you too!

 

 

 

Ah was running out of ideas. Once I read it i knew it was my issue too since i am running in xxx.xxx.178.xxx.

 

Thank you so much for sharing u fixed my problem!

[Blue300]

On 9/11/2021 at 7:16 PM, MrCTS said:

Mine has always been in bridge mode since day 1.  

However over on the github page, we've managed to figure out that its not on bubuntux end.  Nord has actually taken the blame for it and owning that it is on their end of things.

Is there any news on this?

Been trying to fix a connection for a day now

[Hawkins12]

So I keep getting warning messages because my Docker Image file is getting full.  The culprit appears to be NordVPN:

 

 

How do I keep NordVPN from writing to my docker img?

[Blue300]

Still trying to fix this, is it a problem with my setup or is there still a problem at nords end?

I've tried everything I can think of and that I could find from what information i could find but nothing has helped.

Edited October 9, 2021 by Blue300

[jimdaway]

So, I'm sure I must be missing something but I'm at a loss as to what to try next.

 

I started with a test unRaid server setup and installed the Zotarios nordvpn docker container. I had it working perfectly on my test platform. I then tore the test server down and rebuilt was will become my new unRAID server. The first snag I hit was getting the nordvpn container running.

 

I did a complete re-build and re-start of the unRAID install and setup.

I re-formatted the boot-up flash-drive as well as all disks in the array including the cache disk.

The next step was to install the nordvpn container and other than entering my nordvpn username and password, I left all the other configuration settings as found except I unchecked the "Start contain after installation". The container installed without any errors or warnings.

I then opened the logs for the container and started the container. It went through the startup then reported Invalid username or password yet the container still showed as running. When I refreshed my unRAID browser window, the container showed as stopped. No other entries were entered into the log. This is the log of the startup:

[2021-10-12T14:26:43-07:00] Firewall is up, everything has to go through the vpn
[2021-10-12T14:26:43-07:00] Enabling connection to secure interfaces
[2021-10-12T14:26:43-07:00] Enabling connection to nordvpn group
[2021-10-12T14:26:43-07:00] Enabling connection to docker network
[2021-10-12T14:26:43-07:00] Enabling connection to network 192.168.0.0/24
[2021-10-12T14:26:43-07:00] Restarting the service
[2021-10-12T14:26:43-07:00] Waiting for the service to start
[2021-10-12T14:26:43-07:00] Logging in
[2021-10-12T14:26:44-07:00] Invalid Username or password.

One final piece of the puzzle is that there are no entries being displayed under the PORT MAPPINGS column yet maybe that isn't significant. When I select "Edit" then drop-down the Show docker allocations, it displays as follows:
nordvpn         bridge         0.0.0.0        "???"  (without the quotes)

 

I'm really at a loss here and would very much appreciate any insights or advice.

Edited October 12, 2021 by jimdaway

[RiDDiX]

Also for me since last night completly broken. Used an other one... Sad cuz NordLynx and KillSwitch worked great till yesterday night.

[jimdaway]

Hi @RiDDiX, I eventually went to my Nord account and changed my password there as I KNOW I was entering it correctly in the container config.

 

After I changed my password on the Nord site, I used the new one for the unRAID container and it started working just fine.

 

It was a very odd situation as I know the password for NordVPN was correct as I tested it on other devices.

[RiDDiX]

1 hour ago, jimdaway said:

Hi @RiDDiX, I eventually went to my Nord account and changed my password there as I KNOW I was entering it correctly in the container config.

 

After I changed my password on the Nord site, I used the new one for the unRAID container and it started working just fine.

 

It was a very odd situation as I know the password for NordVPN was correct as I tested it on other devices.

 

Ok. I will try this also but afaik if this happens every week it seems nearly useless. Because why should I change my Password every week?

 

[jimdaway]

I totally agree that a potentially regular occurrence of this would be too problematic to tolerate.

 

I made this change two weeks ago (Oct 12) and it's been working properly since. I'm not beyond thinking I may have had something misconfigured but the process of fixing it didn't point in that direction. I use a torrent IP tracker to confirm that my torrenting traffic is going through the VPN and it's been solid so far however YMMV.

 

If I see any drop in connection, I'll report it back here so we can stay informed.

[RiDDiX]

52 minutes ago, jimdaway said:

I totally agree that a potentially regular occurrence of this would be too problematic to tolerate.

 

I made this change two weeks ago (Oct 12) and it's been working properly since. I'm not beyond thinking I may have had something misconfigured but the process of fixing it didn't point in that direction. I use a torrent IP tracker to confirm that my torrenting traffic is going through the VPN and it's been solid so far however YMMV.

 

If I see any drop in connection, I'll report it back here so we can stay informed.

 

So I tried with chaning my password within nordvpn control panel.. Dont work

So Ill go back to an other nordvpn docker....

[jimdaway]

Gah. Sorry, Mate.

 

Please let me know which Nord docker container you end up using and what the outcome is. Shared info is always valuable!

 

Best of luck.🙂

[RiDDiX]

5 minutes ago, jimdaway said:

Gah. Sorry, Mate.

 

Please let me know which Nord docker container you end up using and what the outcome is. Shared info is always valuable!

 

Best of luck.🙂

 

I try now a few and check which one is my favorite.

Here my Logs / Username and Password wont show. But it is stuck at connecting -.-

 

Quote

[2021-10-26T16:31:30+02:00] Setting up NordVPN Version 3.10.0
CyberSec is set to 'enabled' successfully.
Disabling CyberSec.
DNS is set to '1.0.0.1, 1.1.1.1' successfully.
Kill Switch is already set to 'disabled'.
Technology is successfully set to 'NordLynx'.
Subnet XXX is whitelisted successfully.
Subnet XXX is whitelisted successfully.
Ipv6 is set to 'enabled' successfully.
Subnet XXXX is whitelisted successfully.
[2021-10-26T16:31:30+02:00] Connecting...

 

[jimdaway]

I initially had that situation waiting for a connection as well.

 

However, check your WAN IP address as mine was indeed through the VPN even though it said it was still connecting.

 

[RiDDiX]

38 minutes ago, jimdaway said:

I initially had that situation waiting for a connection as well.

 

However, check your WAN IP address as mine was indeed through the VPN even though it said it was still connecting.

 

 

Found a fix:

Edit the docker template and add/replace for repository:

 

bubuntux/nordvpn:master

 

 

Start the container, when stuck at "connecting"

 

Go into Unraid -> Docker -> Click on nordvpn Icon -> Console -> type 

 

curl ifconfig.io

 

Check IP against your WAN-IP.

 

Should work 🙂

 

Edited October 26, 2021 by RiDDiX
Typos

[matty2k]

Same here. NordVPN is working but the log still chowing connecting.

[RiDDiX]

55 minutes ago, matty2k said:

Same here. NordVPN is working but the log still chowing connecting.

 

It seems that the "LATEST" isnt the LATEST This is why I added the :master

 

Because it uses NordVPN Client 3.11 instead 3.10