NordVPN


Recommended Posts

24 minutes ago, Karoolus said:

Container refuses to connect for me, I saw the open issue on Github

https://github.com/bubuntux/nordvpn/issues/227

 

No idea what to do now, I have several other containers running through this NordVPN container so those are all not working now either. ( I wouldn't have those running without VPN anyway, my ISP is too curious haha )

 

I am having the same issue. No problem connecting via another device. Advise will be appreciated.

Link to comment

Anyone else having problems with getting stuck in "Connecting..."? It appears that a VPN connection is still established successfully, as when I route all traffic from a Firefox Docker through the NordVPN container and visit https://nordvpn.com/de/what-is-my-ip/ it tells me that I am protected and the IP address and the geolocation differs from my actual ip address/location.

Though if I manually specify a preferred server (CONNECT), then no docker container is connected to the Internet (as I enabled KILLSWITCH).

 

 

 

Bildschirmfoto 2021-07-28 um 17.23.09.png

Edited by mapa92
typo
Link to comment
  • 2 weeks later...

 

 

On 7/13/2021 at 12:30 AM, Renaldo said:

@shiftylilbastrd so here are my current settings, my default was 8080 but i have sinced changed it to 8113. i believe everything is connected as it should be i just can't access the webui, i'm copying the link directly from qbit settings into my browser and getting "address took too long to respond". i appreciate all of your help and time reading through this so far. 

 1509480333_currentdockers.thumb.png.d18d28c4920524852ecf460d96cc4d3d.png676734313_currentqbit.thumb.png.769c1128b43690010c9b4c56e6df6d42.png1342250065_nordcurrent.thumb.png.916177de82ef439a69c0687d90d1b711.png

 

Still having trouble with this?  It looks to me like you changed the container port for qbitttorent.  I am using hotio's docker template, but should be similar for you.

 

qbitttorent's container typically uses port 8080.  This port is already occupied on my setup, so I modified it to 8089, but you need to leave the container port as 8080.  See attached screenshot.

1275890386_Screenshot2021-08-16121745.thumb.png.a9f585a52bc03f9ba37b88aa28de74d3.png

 

Then in the nordvpn container you have to map the host port 8089 to container port 8080.  See attached.

801820093_Screenshot2021-08-16121953.thumb.png.ff6a8b79fd7c9d94f0fdf4c8227b79cc.png

 

You should then be able to access the webui by using unraid's ip and port 8089.  You can verify traffic is being routed through the nordvpn container by bashing into qbittorent and using curl ifconfig.io.

Link to comment

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?

Link to comment
8 hours ago, 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?

 

If it does not give you the option to map both the container and host port, try turning on Template Authoring Mode.  Go to settings --> docker -->enable docker = no-->apply.  Then turn on Template Authoring Mode and start docker back up.

 

1966947327_Screenshot2021-08-17141548.thumb.png.5373964606e97f8c6d125fcc26cf7f7e.png

Link to comment
16 hours ago, Baby_Shark said:

 

If it does not give you the option to map both the container and host port, try turning on Template Authoring Mode.  Go to settings --> docker -->enable docker = no-->apply.  Then turn on Template Authoring Mode and start docker back up.

 

1966947327_Screenshot2021-08-17141548.thumb.png.5373964606e97f8c6d125fcc26cf7f7e.png

Sorry, I am not undestanding, what do you mean with start docker back up?

 

If it means "enable docker", I tryed but everything continues the same. only :8888 showed as mapped.

 

image.png.dffd23d04dae3ed9790b720a7861093e.png

Edited by dellorianes
Link to comment
On 8/19/2021 at 1:16 AM, SimpleDino said:

@Zotarios

 

Just like some of the people here I can not access the webui of the docker that has been routed through the NordVPN container.

  1. NordVPN - NordLyx: Works fine, Confirmed it via console and getting correct ip for specific country requested in template (even though logs show at the end ...connecting...)
  2. Lidarr with port :8685 - network type has been set to None and extra parameter to --net=container:nordvpn
  3. NordVPN - Lidarr port 8686 has been added (also tried setting requested to yes but to no veil)
  4. trying to access webui with [UnRAID IP]:8686 but still no success

Followed these step per SP1's instruction but can't any to work! Need help solving this?

 

A follow up question, is it possible to download in speedtest-cli in the container? if yes, then what linux command should be used here? because sudo doesnt work and this is not an archlinux so no pacman.

Does Lidarr container show the port :8686 mapped in unraid docker webpage?

 

image.png.05f7f5dfa63adebe2ad88f4348fb0409.png

Link to comment
On 8/20/2021 at 12:07 PM, SimpleDino said:

Yes, it does.

 

bild.thumb.png.29900f2c4daf90c6999615fb5244706e.png

 

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!

 

 

Screenshot 2021-08-24 195846.png

  • Thanks 1
Link to comment
14 minutes ago, SimpleDino said:

Okay, then that means I have to add a route (192.168.1.0/24) in network settings - Route settings, correct? if the connecting is up!

I just changed it in the nordvpn docker config like shown in my screenshot. Click on 'Show more settings' and if the IP range listed on the 'LAN net' section doesn't match your server, change it to the correct one. If it already matches, then you have a different problem and my fix won't help.

Link to comment
On 8/18/2021 at 2:03 PM, dellorianes said:

Sorry, I am not undestanding, what do you mean with start docker back up?

 

If it means "enable docker", I tryed but everything continues the same. only :8888 showed as mapped.

 

image.png.dffd23d04dae3ed9790b720a7861093e.png

Any idea about this?

 

I have also tryed creating both nordvpn and oscam containers using docker-compose (both in the same .yml file) but it results in the same issue.

Only mapping in the .yml file the ports 8889 and 9000; nordvpn is creating correctly (with this both ports) but oscam container is created only with port 8888 (even when I haven't created it as an ENVIRONMENT variable)

 

It seems like the container is primary builded and the image only accept port 8888 in this network mode.

Edited by dellorianes
Link to comment

Im also having problems getting the container to do anything, I am assuming I am missing something obvious.

Authentication fails.  Based on the container template description,  I used my email as username and the corresponding password.  This failed.  I then tried the "manual configuration" credentials from the NordVPN web site, which also (perhaps not surprisingly) failed.  I then reset the login credentials and used those, which also failed.  Can you provide guidance on debugging this?

Link to comment
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!

 

OK. Thanks for sharing. Helped me to solve the problem. Was looking a long time for a solution now. The setting should not be on Advanced settings => should be on top of Basic settings. However .. sabnzbd is now working like hell with nordvpn and nordlynx protocoll.

Link to comment

got same issue

 

[2021-08-27T14:37:47-04:00] Firewall is up, everything has to go through the vpn
[2021-08-27T14:37:47-04:00] Enabling connection to secure interfaces
[2021-08-27T14:37:47-04:00] Enabling connection to nordvpn group
[2021-08-27T14:37:47-04:00] Enabling connection to docker network
[2021-08-27T14:37:47-04:00] Enabling connection to network 192.168.0.0/24
[2021-08-27T14:37:47-04:00] Restarting the service
[2021-08-27T14:37:47-04:00] Waiting for the service to start
[2021-08-27T14:37:47-04:00] Logging in
[2021-08-27T14:38:48-04:00] Invalid Username or password.

 

Link to comment
9 hours ago, matty2k said:

 

OK. Thanks for sharing. Helped me to solve the problem. Was looking a long time for a solution now. The setting should not be on Advanced settings => should be on top of Basic settings. However .. sabnzbd is now working like hell with nordvpn and nordlynx protocoll.

yea I agree, if the NETWORK variable was more visible it would probably avoid a lot of confusion. Glad to hear you got it working!

Link to comment

Using Zotarios' Repository that pulls from bubntux on dockerhub

 

The container works great if I use "bridge" for my network type. However, if I use "custom: br0" the number of connections shown in my router spikes to 43 and I get the attached error in my logs. In reviewing the problem I found that this issue was raised here ( https://github.com/bubuntux/nordvpn/issues/91 ). The issue is closed but the last comment points to issue 139.

 

I'm hoping that others have found a solution to getting this image to work on custom as I'd like to assign it an IP and route traffic through it.

image.png

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.