Replies: 21 comments 10 replies
-
|
Instead of Ports work exactly the same. It's just how docker works and not specific to the old NordVPN container or this one. |
Beta Was this translation helpful? Give feedback.
-
|
Have you managed to get this to work? I'm trying to do the same but struggling to make it work as it should. A guide & compose example for a working version would be really appreciated. |
Beta Was this translation helpful? Give feedback.
-
|
Yes, it now operates in the same way as the old nordvpn container did. |
Beta Was this translation helpful? Give feedback.
-
|
Hi, Thanks for this. This is my config which doesn't seem to work. Am I missing something? Items in [] are hidden. |
Beta Was this translation helpful? Give feedback.
-
|
You don't need a volume for the configs. They get created dynamically on startup and don't need a permanent location. I don't understand why you only allow some private IPs. If you want traffic to run via the VPN connection then you should use the default |
Beta Was this translation helpful? Give feedback.
-
Okay perfect! That all works as it should now. I misinterpreted what allowed IPs was. Thought it was the equivalent of firewall whitelisting. For future reference to others the working docker compose for me is : |
Beta Was this translation helpful? Give feedback.
-
|
I'm moving over from bubuntux/nordvpn as well and got close following @cschinis 's example. However The docker host is on Ubuntu 18.04.6, 4.15.0-163-generic if that helps |
Beta Was this translation helpful? Give feedback.
-
|
Don't forget to add: Change the ID to your recommended server id from (Example extract for UK "{"id":227,"name":"United Kingdom","code":"GB","): Also try commenting out: |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the reply! Neither of those changes affect the behavior unfortunately. Neither the vpn container or the dependent containers can access the WAN Unrelatedly, I thought the QUERY var was optional and it'd auto select the best by default? |
Beta Was this translation helpful? Give feedback.
-
How are you deploying the stack? With the exception of the issue I had above which was resolved with allowing 0.0.0.0, every other time dependant containers were not connecting to the wan was because the vpn did not have a successful connection. I use docker in combination with Portainer and similar issues were fixed by stopping all containers, deleting the images and networks and redeployed the stack. Obviously make sure the private key is correct. (I got mine through the bubintux/NordVPN image.) |
Beta Was this translation helpful? Give feedback.
-
|
EDIT: fixed it myself by changing to a different container. Here's my torrent stack now for posterity: The portion of the old container I wanted, the vuetorrent front end, can be installed manually by simply unzipping the package from the vuetorrent github into /opt/torrent/qBittorrent/vuetorrent or /config/qBittorrent/vuetorrent within the container. Everything working perfectly. |
Beta Was this translation helpful? Give feedback.
-
|
I'm having issues with this too. Testing with the bare minimum: This allows me to i.e
|
Beta Was this translation helpful? Give feedback.
-
|
What IP range are you trying to cover with NET_LOCAL=10.0.0.0/24? If it's
10.0.0.1-10.254.254.254 then you should use 10.0.0.0/8?
…On Sun, 19 Dec 2021 at 20:57, NoLooseEnds ***@***.***> wrote:
I'm having issues with this too.
Testing with the bare minimum:
version: '3.7'
services:
vpn-test:
container_name: nordlynx
image: ghcr.io/bubuntux/nordlynx:edge
cap_add:
- NET_ADMIN #required
environment:
- PRIVATE_KEY=<key>
- NET_LOCAL=10.0.0.0/24 # So it can be accessed within the local network
- ALLOWED_IPS=0.0.0.0/0
sysctls:
- net.ipv6.conf.all.disable_ipv6=1
restart: unless-stopped
This allows me to i.e ping 10.0.0.1 on the local network, but I'm not
allowed to ping or resolve anything else.
[image: image]
<https://user-images.githubusercontent.com/4103531/146690493-8021fc65-8df9-45e0-b86d-d174e036334a.png>
—
Reply to this email directly, view it on GitHub
<#9 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACSF5AIY4L4QGM2JIZ3LGDTURZBMJANCNFSM5JDHFRFA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
This is just to test, I'm running the simplest docker-compose I can to debug. It's just to open up my local network to see if I can get through. In my actual setup, it's a bit more advanced with multiple ranges. Anyhow, if I understand this correctly, opening up for the local network is not the issue. The issue is that I can't get out on the internet. I can add public IP's to So I'm hoping somebody can spot something obviously wrong, and or help me debug it further. This is the iptables rules: |
Beta Was this translation helpful? Give feedback.
-
|
It looks like the issue is with your firewall rather than the VPN container. Can you route it so that your VPN machine bypasses the firewall? |
Beta Was this translation helpful? Give feedback.
-
|
I don't think that should be an issue. It's a VM running PhotonOS. I can do anything natively – and I've never had to add any iptables rules because any docker container previously. And the previous nordvpn-image worked flawlessly in that regard. This is the iptables of the PhotonOS vm |
Beta Was this translation helpful? Give feedback.
-
|
Hi Guys! Apologies for the noobie question but How I get the Rekired Nord_Private_key? Ised the following as instructed: docker run --rm --cap-add=NET_ADMIN -e USER=MYUSERHERE -e PASS=MYPASSHERE bubuntux/nordvpn nord_private_key But says NordVPN is using a new app and do many try to connecto with no providing any private key. I proceeded to contatc NordVPN and they say unfortunately they are con allowing Nordlynx thechnology for manual use anymore. So how you got it? If I don;t have the private key I can't even try any compose file at first. Am I wrong? Please help. |
Beta Was this translation helpful? Give feedback.
-
|
@walmer26 try following the manual steps to get the private key https://forum.openwrt.org/t/instruction-config-nordvpn-wireguard-nordlynx-on-openwrt/89976 |
Beta Was this translation helpful? Give feedback.
-
|
Hello, why should we migrate to /nordlynx image? I imagine is not using the nordvpn client, but I have a question: I need the ability to change servers dinamically, would this still work using the private key that the /nordvpn gave me? From my understanding, the private key will change based on the server, is that correct? Thanks |
Beta Was this translation helpful? Give feedback.
-
|
@mircoianese The private key is link to you account no to a server, you can use your private key to connect to any of the server, and yes you can dynamically change servers using the query parameter @ThxAndBye listed a few very useful ones. |
Beta Was this translation helpful? Give feedback.
-
Thanks both! I will migrate to the new image. I guess that the same PK can't be used to open multiple concurrent connection tho. Right? Can I generate multiple valid private keys in an easy way? |
Beta Was this translation helpful? Give feedback.
-
|
Hello again. I was doing the migration but I'm getting into the issue I expected: i need to have two different containers connected to different servers (using the same NordVPN account). The old image generated the same Private Key on both containers, but now if I try to connect two different containers using the new image with the same private key I have issues where I randomly loose internet connection (DNS resolution failures). Maybe this issue was also present with the other image tho, as I had to restart the containers once in a while. Do you know if there is a correct way to do this? |
Beta Was this translation helpful? Give feedback.
-
|
Why do you need two different servers, why don't you use the same container for both? |
Beta Was this translation helpful? Give feedback.
-
|
Each NordVPN account can connect from up to 6 different "devices". I have two different containers (in two different servers) that needs to connect to different countries to perform some downloading tasks. |
Beta Was this translation helpful? Give feedback.
-
|
I can't migrate from nordvpn |
Beta Was this translation helpful? Give feedback.
-
Try to remove apostrophes from:
|
Beta Was this translation helpful? Give feedback.
-
|
well, no luck still |
Beta Was this translation helpful? Give feedback.
-
The WSL2 kernel isn't compatible with Wireguard ootb. You need to replace the kernel for it to work like you expect on a compatible system. |
Beta Was this translation helpful? Give feedback.
-
|
I can't seem to recompile the kernel, so I tried a compiled one, https://github.com/nathanchance/WSL2-Linux-Kernel but it still didn't work for me |
Beta Was this translation helpful? Give feedback.
-
|
How do I select city to connect to using QUERY? I can only select country |
Beta Was this translation helpful? Give feedback.
-
Looking for some guidance on replacing bubuntux/nordvpn with this instead based on this commend bubuntux/nordvpn#282 (comment)
I've got it up and running, it's connected, and I can connect other containers through it, I just can't seem to access them once they're connected.
I'm looking for the equivalent environment variables for:
1: NETWORK=192.168.1.0/24 # So it can be accessed within the local network
2: CONNECT=Canada
3: KILLSWITCH=Enabled
Also looking for the proper way to set the ports for the containers connecting through this one. On the NordVPN one you'd set the ports for the containers through the NordVPN container (ie: 3000:3000), is this handled the same or can you use a comma seperated list for LISTEN_PORTS?
The documentation isn't really clear on any of these.
Beta Was this translation helpful? Give feedback.
All reactions