search

bubuntux / nordvpn

NordVpn Docker Client
GNU Affero General Public License v3.0
749 stars 198 forks source link

Fix for 3.16.1 #392

Closed mhhplumber closed 1 year ago

mhhplumber commented 1 year ago

fixes #389

upgraded OS to jammy upgraded nord version to 3.16.1 fixed s6 permissions for check added sleep to stop race condition for nordvpnd.sock

jarlbrak commented 1 year ago

@bubuntux can you check this out? Hoping this can fix the issues I'm having with the token auth...

bubuntux commented 1 year ago

merged, thanks

mhhplumber commented 1 year ago

I think what most users were experiencing was nordvpnd.sock not existing yet. If it doesn't fix for everyone, can try increasing the sleep or just waiting for the socket

jarlbrak commented 1 year ago

I think what most users were experiencing was nordvpnd.sock not existing yet. If it doesn't fix for everyone, can try increasing the sleep or just waiting for the socket

Now I'm getting a new error that is stumping me...

FATAL: iptables is not functional. Ensure your container config adds --cap-add=NET_ADMIN,NET_RAW
--- Due to errors, routing has been disabled ---

I have both NET_ADMIN,NET_RAW in my docker compose...

mhhplumber commented 1 year ago

I think what most users were experiencing was nordvpnd.sock not existing yet. If it doesn't fix for everyone, can try increasing the sleep or just waiting for the socket

Now I'm getting a new error that is stumping me...

FATAL: iptables is not functional. Ensure your container config adds --cap-add=NET_ADMIN,NET_RAW
--- Due to errors, routing has been disabled ---

I have both NET_ADMIN,NET_RAW in my docker compose...

Can you post the lines from your docker compose? this line I don't think works --cap-add=NET_ADMIN,NET_RAW because it takes the capabilities as one argument -- It works when you add them separately ie "--cap-add=NET_ADMIN --cap-add=NET_RAW" Docker compose version may make a difference here too

jarlbrak commented 1 year ago

Eh, I'm done messing with it. Both this and NordLynx don't work for me at all since the past two weeks. Just switched to SurfShark and Glutun and it worked on the first run...

DigitalGameMachine commented 1 year ago

I think what most users were experiencing was nordvpnd.sock not existing yet. If it doesn't fix for everyone, can try increasing the sleep or just waiting for the socket

Now I'm getting a new error that is stumping me...

FATAL: iptables is not functional. Ensure your container config adds --cap-add=NET_ADMIN,NET_RAW
--- Due to errors, routing has been disabled ---

I have both NET_ADMIN,NET_RAW in my docker compose...

Can you post the lines from your docker compose? this line I don't think works --cap-add=NET_ADMIN,NET_RAW because it takes the capabilities as one argument -- It works when you add them separately ie "--cap-add=NET_ADMIN --cap-add=NET_RAW" Docker compose version may make a difference here too

Since I'm having the same issue I will reply since @jarlbrak is switching to Glutun. Using portainer Stack deployment.

version: "3" services: vpn: container_name: nordvpn image: ghcr.io/bubuntux/nordvpn restart: unless-stopped
cap_add:

mhhplumber commented 1 year ago

@DarkGM I need a couple other details to try to recreate the behavior. Could you let me know what your base OS is and the CPU architecture?

fraPace commented 1 year ago

Hello @mhhplumber ,

I am having the same problem above.

My docker-compose is the following one:

version: "3" services: vpn: image: ghcr.io/bubuntux/nordvpn container_name: vpn cap_add:

I usually use Portainer EE to manage it and it worked fine. I also saw that some reported that with Portainer they could have have the cap_add set properly so I have manually deployed it using docker-compose up -d without success.

My docker env is the following: CPU: 4 RAM: 16.6 GB - Standalone 20.10.17-qnap7.

mhhplumber commented 1 year ago

Hello @mhhplumber ,

I am having the same problem above.

My docker-compose is the following one:

version: "3"

services:

vpn:

image: ghcr.io/bubuntux/nordvpn

container_name: vpn

cap_add:

  - NET_ADMIN

  - NET_RAW

environment:

  - TOKEN=${VPN_TOKEN}

  - CONNECT='--group p2p'

  - TECHNOLOGY=NordLynx

  - NETWORK=192.168.1.0/24

  - PUID=1000

  - PGID=100

  - TZ=Europe/Paris

  - DNS=127.0.0.11;1.1.1.1;8.8.8.8; # need to manually specify them to support docker DNS

ulimits:                    # Recommended for High bandwidth scenarios

  memlock:

    soft: -1

    hard: -1

restart: always

I usually use Portainer EE to manage it and it worked fine.

I also saw that some reported that with Portainer they could have have the cap_add set properly so I have manually deployed it using docker-compose up -d without success.

My docker env is the following: CPU: 4 RAM: 16.6 GB - Standalone 20.10.17-qnap7.

Thanks for the info! Work has me very busy atm but I will spend some time on this the next few days.

handsome1987 commented 1 year ago

Hey is there any news on this issue? I also have the invalid token error on docker on my synology nas.