Parse error starting OpenVPN

stamina11 commented 1 year ago

Is there a pinned issue for this?

[X] I have read the pinned issues and could not find my issue

Is there an existing or similar issue/discussion for this?

[X] I have searched the existing issues
[X] I have searched the existing discussions

Is there any comment in the documentation for this?

[X] I have read the documentation, especially the FAQ and Troubleshooting parts

Is this related to a provider?

[X] I have checked the provider repo for issues
[X] My issue is NOT related to a provider

Are you using the latest release?

[X] I am using the latest release

Have you tried using the dev branch latest?

[ ] I have tried using dev branch

Docker run config used

version: '3' services: openvpn: image: haugene/transmission-openvpn container_name: openvpn privileged: true cap_add:

NET_ADMIN restart: always ports:
- "9091:9091" volumes:
- /etc/localtime:/etc/localtime:ro
- /home/plex/media:/data environment:
  NordVPN
- CREATE_TUN_DEVICE=true
- PEER_DNS=false
- TZ=MST
- HEALTH_CHECK_HOST=https://google.com
- OPENVPN_PROVIDER=NORDVPN
- NORDVPN_COUNTRY=CA
- NORDVPN_CATEGORY=P2P
- NORDVPN_PROTOCOL=UDP
- OPENVPN_USERNAME="****"
- OPENVPN_PASSWORD="****"
- OPENVPN_OPTS=--inactive 3600 --ping 10 --ping-exit 60
- DISABLE_PORT_UPDATER=true
- LOCAL_NETWORK=10.0.0.0/24
- TRANSMISSION_RATIO_LIMIT_ENABLED=true
- TRANSMISSION_RATIO_LIMIT=0.5
- TRANSMISSION_ALT_SPEED_UP=200
- TRANSMISSION_SPEED_LIMIT_DOWN_ENABLED=false

Current Behavior

I have downloaded the latest docker image but the issue still persists. No changes were done from my side recently. Openvpn is unable to connect and erroring out with Parse error.

Expected Behavior

Openvpn starts normally and connects to specified provider.

How have you tried to solve the problem?

1) stop the container and remove the image 2) pull down new image and start the container with no username/password in docker-compose file (still the same error) 3) Not specify the provider in docker-compose (error because no provider is specified)

Log output

Creating TUN device /dev/net/tun
Using OpenVPN provider: NORDVPN
Running with VPN_CONFIG_SOURCE auto
Provider NORDVPN has a bundled setup script. Defaulting to internal config
Executing setup script for NORDVPN
/etc/openvpn/nordvpn/..
INFO: OVPN: Checking curl installation
INFO: OVPN: DNS resolution ok
INFO: OVPN: ok, configurations download site reachable
INFO: OVPN: Removing existing configs in /etc/openvpn/nordvpn
parse error: Invalid numeric literal at line 1, column 7

HW/SW Environment

- OS: Ubuntu 20.04.6 LTS
- Docker: docker community edition - version 24.0.2

Anything else?

No response

ryanjohnsontv commented 1 year ago

Confirming that I am also experiencing this issue. NordVPN recently deprecated, and as of yesterday removed, the legacy login flow used by this repo. I updated my username and password to the new service credentials as instructed but it's possible the response from NordVPN has changed which causes this error.

ryanjohnsontv commented 1 year ago

In my case I believe this was caused by me not changing the login credentials in time, causing the container to retry authorizing every few seconds for hours while I slept. Debug reveals a "429 Too Many Requests" response, so assuming that's due to being rate limited I'm going to stop the container for a bit and try again later.

References: NordVPN Removes Legacy Login Error: 429 Too Many Requests

ilike2burnthing commented 1 year ago

Yep, same issue. Stopped the container for ~10mins (and disabled a SOCKS5 proxy I had running elsewhere), and it's back up again with the service credentials.

adudeinspain commented 1 year ago

Same issue with me as well, within the last few hours. The problem is on the NordVPN side for sure. My problem still remains, even after updating my credentials to the new login issued by NordVPN. I also added “-- token” to the OPENVPN options, still no dice.

stamina11 commented 1 year ago

Thanks for quick responses guys. I didn't even realize it was NordVPN related. Setting those credentials in the docker file and restarting did solve it for me. Much appreciated.

mushuthecat commented 1 year ago

Hi,

can someone confirm me that is the solution :

login to your nord vpn dashboard
activate "service credential"
edit your docker-compose file for the token OPENVPN_USERNAME and OPENVPN_PASSWORD by using your new credential
wait 10 minutes if your container was restarting in loop before ?

I in the waiting time cose i get the parse error: Invalid numeric literal at line 1, column 7

Regards

enchained commented 1 year ago

can someone confirm me that is the solution :

This sequence worked for me earlier today, but I also had to restart the container once more cause downloads weren't starting in the client.

stamina11 commented 1 year ago

I just followed those steps, login here https://my.nordaccount.com/dashboard/nordvpn/ then under "Manual Setup" i clicked Set Up NordVPN Manually. I will send you a code to your email once verified then it shows you your new username/password. I plugged those values in to docker-compose.yaml file, did 'docker-compose down', then docker-compose up -d and it connected successfully.

adudeinspain commented 1 year ago

The steps in the post above to create the username and password are correct. As someone else mentioned they had to stop a different running container to clear the socket. I had to restart my computer to clear mine. After that it worked fine. On Jun 29, 2023, at 02:42, clintyip @.***> wrote: Tried the above steps and I'm still getting the exact same error. I've even tried to change the password on my NordVPN account to reset the password on the manual setup credentials and no dice Have waited about an hour in between attempts

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: @.***>

TaTaSuZette commented 1 year ago

Do you guys succeed to make it work ? I tried the different given solutions but it's still broken. Shall we wait for NordVPN to update something ?

mushuthecat commented 1 year ago

Hi,

Following my previous message, it works for me FYI it take for me more than 2 hours for be allowed again to login do not forget to stop your container and wait before.

Regards

Le jeu. 29 juin 2023, 16:29, TaTaSuZette @.***> a écrit :

Do you guys succeed to make it work ? I tried the different given solutions but it's still brokien. Shall we wait for NordVPN to update something ?

— Reply to this email directly, view it on GitHub https://github.com/haugene/docker-transmission-openvpn/issues/2638#issuecomment-1613284348, or unsubscribe https://github.com/notifications/unsubscribe-auth/AUAKOT6JW4PJKM2MTSFSTLTXNWGNZANCNFSM6AAAAAAZXG6AGM . You are receiving this because you commented.Message ID: @.***>

TaTaSuZette commented 1 year ago

Hi, Following my previous message, it works for me FYI it take for me more than 2 hours for be allowed again to login do not forget to stop your container and wait before. Regards

Hi, thanks for your answer :) It's good it's working. I still had the openvpn-credentials.txt as config file in my docker config folder. Remove it and relaunch everything made it works properly.

Thanks !

SpiralBrad commented 1 year ago

I continue to see this in my logs, with a repeatedly restarting container:

INFO: OVPN: Removing existing configs in /etc/openvpn/nordvpn
parse error: Invalid numeric literal at line 1, column 7

Even with recreating the container. Yes I've changed to the new auth stuff already; this implies @mushuthecat's solution isn't exactly it. ...unless I'm missing something...

BIG edit: yep I was missing something; mine was an incorrect password on top of the rest, even though I'd already gotten it from Manual Setup; it changed on me. Unsure how or why.

mushuthecat commented 1 year ago

I continue to see this in my logs, with a repeatedly restarting container:
INFO: OVPN: Removing existing configs in /etc/openvpn/nordvpn
parse error: Invalid numeric literal at line 1, column 7
Even with recreating the container. Yes I've changed to the new auth stuff already; this implies @mushuthecat's solution isn't exactly it. ...unless I'm missing something...

Hi,

- login to your nord vpn dashboard https://support.nordvpn.com/General-info/1653315162/Changes-to-the-login-process-on-third-party-apps-and-routers.htm
- activate "service credential"
- edit your docker-compose file for the token OPENVPN_USERNAME and OPENVPN_PASSWORD by using your new credential
- stop your docker container to avoid "ban" from Nord Vpn api
- make sur to delete your openvpn-credentials.txt file in your /config directory because of it contains your old credential.
- To solve my issue i wait for more than two hours

Everithing is okey after that

Regards

maikdiepenbroek commented 1 year ago

I continue to see this in my logs, with a repeatedly restarting container:
INFO: OVPN: Removing existing configs in /etc/openvpn/nordvpn
parse error: Invalid numeric literal at line 1, column 7
Even with recreating the container. Yes I've changed to the new auth stuff already; this implies @mushuthecat's solution isn't exactly it. ...unless I'm missing something...
Hi,
- login to your nord vpn dashboard https://support.nordvpn.com/General-info/1653315162/Changes-to-the-login-process-on-third-party-apps-and-routers.htm
- activate "service credential"
- edit your docker-compose file for the token OPENVPN_USERNAME and OPENVPN_PASSWORD by using your new credential
- stop your docker container to avoid "ban" from Nord Vpn api
- make sur to delete your openvpn-credentials.txt file in your /config directory because of it contains your old credential.
- To solve my issue i wait for more than two hours
Everithing is okey after that

Regards

Thanks for this!

Godd67 commented 1 year ago

Still not working for me. :( So I put my container down, went to this page - and copy-paste these creds into docker-compose.yaml

OPENVPN_USERNAME=
OPENVPN_PASSWORD= then waited for couple hours, started and got the same error. Anything I missed here?

ilike2burnthing commented 1 year ago

Anything I missed here?

https://github.com/haugene/docker-transmission-openvpn/issues/2638#issuecomment-1613304346

Godd67 commented 1 year ago

Hmm, i dont have this file .

ilike2burnthing commented 1 year ago

Tried recreating the container from scratch?

Godd67 commented 1 year ago

OK, mapped new folder to /data and it magically worked. Not sure what was the problem, probably they lift a ban

andsoitgoes commented 1 year ago

I'm struggling here.

I've removed all credentials txt files, I've changed the config directory and I'm still getting the error.

My config file is:

sudo docker run --name=transmission \
--cap-add=NET_ADMIN -d \
--dns 8.8.8.8 \
--dns 8.8.4.4 \
--restart=always \
-v /mnt/media/downloads/:/data \
-v /home/pi/transmission/:/config \
-v /mnt/video/:/video \
-v /mnt/media/tv/:/tv \
-v /etc/localtime:/etc/localtime:ro \
-e CREATE_TUN_DEVICE=true \
-e OPENVPN_PROVIDER=NORDVPN \
-e NORDVPN_COUNTRY=CA \
-e NORDVPN_CATEGORY=legacy_p2p \
-e NORDVPN_PROTOCOL=tcp \
-e WEBPROXY_ENABLED=false \
-e TRANSMISSION_DOWNLOAD_DIR=/data \
-e TRANSMISSION_INCOMPLETE_DIR=/data/incomplete \
-e LOCAL_NETWORK=10.0.0.0/24 \
-e TRANSMISSION_RPC_AUTHENTICATION_REQUIRED=true \
-e TRANSMISSION_RPC_ENABLED=true \
-e TRANSMISSION_RPC_USERNAME=\
-e TRANSMISSION_RPC_PASSWORD=\
-e TRANSMISSION_PEER_PORT_RANDOM_ON_START=false \
--sysctl net.ipv6.conf.all.disable_ipv6=0 \
--log-driver json-file \
--log-opt max-size=10m \
-p 9091:9091 \
haugene/transmission-openvpn:latest

My log file still looks like this:

2023-06-30T07:23:44.043587092Z We will fallback to this directory as long as the folder exists. Please consider moving it to /config/transmission-home 2023-06-30T07:23:44.146995134Z Creating TUN device /dev/net/tun 2023-06-30T07:23:44.163390234Z Using OpenVPN provider: NORDVPN 2023-06-30T07:23:44.163597377Z Running with VPN_CONFIG_SOURCE auto 2023-06-30T07:23:44.163771632Z Provider NORDVPN has a bundled setup script. Defaulting to internal config 2023-06-30T07:23:44.163802612Z Executing setup script for NORDVPN 2023-06-30T07:23:44.169769645Z /etc/openvpn/nordvpn/.. 2023-06-30T07:23:47.474412979Z INFO: OVPN: Checking curl installation 2023-06-30T07:23:47.548122929Z INFO: OVPN: DNS resolution ok 2023-06-30T07:23:48.625876816Z INFO: OVPN: ok, configurations download site reachable 2023-06-30T07:23:48.626217048Z INFO: OVPN: Removing existing configs in /etc/openvpn/nordvpn 2023-06-30T07:23:48.784746720Z parse error: Invalid numeric literal at line 1, column 7 2023-06-30T07:23:49.888427093Z Starting container with revision: 1103172c3288b7de681e2fb7f1378314f17f66cf 2023-06-30T07:23:49.888521942Z TRANSMISSION_HOME is currently set to: /config/transmission-home 2023-06-30T07:23:49.889932443Z WARNING: Deprecated. Found old default transmission-home folder at /data/transmission-home, setting this as TRANSMISSION_HOME. This might break in future versions. 2023-06-30T07:23:49.895828663Z We will fallback to this directory as long as the folder exists. Please consider moving it to /config/transmission-home 2023-06-30T07:23:49.992706076Z Creating TUN device /dev/net/tun 2023-06-30T07:23:50.008726278Z Using OpenVPN provider: NORDVPN 2023-06-30T07:23:50.009038307Z Running with VPN_CONFIG_SOURCE auto 2023-06-30T07:23:50.009135990Z Provider NORDVPN has a bundled setup script. Defaulting to internal config 2023-06-30T07:23:50.009239061Z Executing setup script for NORDVPN 2023-06-30T07:23:50.015264722Z /etc/openvpn/nordvpn/..

I'm lost - I know there's got to be something stupidly simple that I'm missing, would love any help. Got the username and password from the service page as well.

Thanks :(

TaTaSuZette commented 1 year ago

Hi, Can't see the OPENVPN_USERNAME and OPENVPN_PASSWORD lines in your docker file ? Did you remove it for the post or is it missing from your config ?

Regards,

x-real-ip commented 1 year ago

I am spending hours now to get this working, but still without success. I am running the container on Kubernetes. I followed these steps:

- login to your nord vpn dashboard https://support.nordvpn.com/General-info/1653315162/Changes-to-the-login-process-on-third-party-apps-and-routers.htm
- activate "service credential"
- edit your docker-compose file for the token OPENVPN_USERNAME and OPENVPN_PASSWORD by using your new credential
- stop your docker container to avoid "ban" from Nord Vpn api
- make sur to delete your openvpn-credentials.txt file in your /config directory because of it contains your old credential.
- To solve my issue i wait for more than two hours

I even waited more then 12 hours before trying again by starting the container and get this error message AUTH: Received control message: AUTH_FAILED

Full log output:

Starting container with revision: 1103172c3288b7de681e2fb7f1378314f17f66cf
TRANSMISSION_HOME is currently set to: /config/transmission-home
Creating TUN device /dev/net/tun
Using OpenVPN provider: NORDVPN
Running with VPN_CONFIG_SOURCE auto
Provider NORDVPN has a bundled setup script. Defaulting to internal config
Executing setup script for NORDVPN
/etc/openvpn/nordvpn/..
INFO: OVPN: Checking curl installation
INFO: OVPN: DNS resolution ok
INFO: OVPN: ok, configurations download site reachable
INFO: OVPN: Removing existing configs in /etc/openvpn/nordvpn
Checking NORDPVN API responses
INFO: OVPN:Selecting the best server...
INFO: OVPN: Searching for country : NL (153)
INFO: OVPN: Searching for group: legacy_p2p
INFO: OVPN:Searching for technology: openvpn_tcp
INFO: OVPN: Best server : nl897.nordvpn.com, load: 8
Best server : nl897.nordvpn.com
INFO: OVPN: Downloading config: nl897.nordvpn.com.ovpn
INFO: OVPN: Downloading from: https://downloads.nordcdn.com/configs/files/ovpn_tcp/servers/nl897.nordvpn.com.tcp.ovpn
OVPN: NORDVPN: selected: nl897.nordvpn.com, VPN_PROVIDER_HOME: /etc/openvpn/nordvpn
Starting OpenVPN using config nl897.nordvpn.com.ovpn
Modifying /etc/openvpn/nordvpn/nl897.nordvpn.com.ovpn for best behaviour in this container
Modification: Point auth-user-pass option to the username/password file
Modification: Change ca certificate path
Modification: Change ping options
Modification: Update/set resolv-retry to 15 seconds
Modification: Change tls-crypt keyfile path
Modification: Set output verbosity to 3
Modification: Remap SIGUSR1 signal to SIGTERM, avoid OpenVPN restart loop
Modification: Updating status for config failure detection
Setting OpenVPN credentials...
adding route to local network 10.0.100.240/32 via 10.42.2.1 dev eth0
adding route to local network 10.0.10.0/24 via 10.42.2.1 dev eth0
2023-06-30 12:43:00 OpenVPN 2.5.5 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Jul 14 2022
2023-06-30 12:43:00 library versions: OpenSSL 3.0.2 15 Mar 2022, LZO 2.10
2023-06-30 12:43:00 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
2023-06-30 12:43:00 NOTE: --fast-io is disabled since we are not using UDP
2023-06-30 12:43:00 Outgoing Control Channel Authentication: Using 512 bit message hash 'SHA512' for HMAC authentication
2023-06-30 12:43:00 Incoming Control Channel Authentication: Using 512 bit message hash 'SHA512' for HMAC authentication
2023-06-30 12:43:00 TCP/UDP: Preserving recently used remote address: [AF_INET]213.232.87.125:443
2023-06-30 12:43:00 Socket Buffers: R=[131072->131072] S=[16384->16384]
2023-06-30 12:43:00 Attempting to establish TCP connection with [AF_INET]213.232.87.125:443 [nonblock]
2023-06-30 12:43:00 TCP connection established with [AF_INET]213.232.87.125:443
2023-06-30 12:43:00 TCP_CLIENT link local: (not bound)
2023-06-30 12:43:00 TCP_CLIENT link remote: [AF_INET]213.232.87.125:443
2023-06-30 12:43:00 TLS: Initial packet from [AF_INET]213.232.87.125:443, sid=98ca145c e53d81d0
2023-06-30 12:43:00 VERIFY OK: depth=2, C=PA, O=NordVPN, CN=NordVPN Root CA
2023-06-30 12:43:00 VERIFY OK: depth=1, O=NordVPN, CN=NordVPN CA8
2023-06-30 12:43:00 VERIFY KU OK
2023-06-30 12:43:00 Validating certificate extended key usage
2023-06-30 12:43:00 ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication
2023-06-30 12:43:00 VERIFY EKU OK
2023-06-30 12:43:00 VERIFY X509NAME OK: CN=nl897.nordvpn.com
2023-06-30 12:43:00 VERIFY OK: depth=0, CN=nl897.nordvpn.com
2023-06-30 12:43:00 Control Channel: TLSv1.3, cipher TLSv1.3 TLS_AES_256_GCM_SHA384, peer certificate: 4096 bit RSA, signature: RSA-SHA512
2023-06-30 12:43:00 [nl897.nordvpn.com] Peer Connection Initiated with [AF_INET]213.232.87.125:443
2023-06-30 12:43:01 SENT CONTROL [nl897.nordvpn.com]: 'PUSH_REQUEST' (status=1)
2023-06-30 12:43:07 SENT CONTROL [nl897.nordvpn.com]: 'PUSH_REQUEST' (status=1)
2023-06-30 12:43:07 AUTH: Received control message: AUTH_FAILED
2023-06-30 12:43:07 SIGTERM[soft,auth-failure] received, process exiting

My config


---
kind: ConfigMap
apiVersion: v1
metadata:
  name: transmission-config
  namespace: media
  labels:
    app: transmission
data:
  LOCAL_NETWORK: 10.0.100.240/32, 10.0.10.0/24
  NORDVPN_CATEGORY: p2p
  NORDVPN_COUNTRY: NL
  NORDVPN_PROTOCOL: udp
  OPENVPN_OPTS: --inactive 3600 --ping 10 --ping-exit 60
  OPENVPN_PROVIDER: NORDVPN
  TRANSMISSION_DOWNLOAD_DIR: /data/completed
  TRANSMISSION_INCOMPLETE_DIR: /data/incomplete
  TRANSMISSION_WATCH_DIR: /data/watch
  TRANSMISSION_DOWNLOAD_QUEUE_SIZE: "4"
  TZ: Europe/Amsterdam
  WEBPROXY_ENABLED: "false"
  CREATE_TUN_DEVICE: "true"
  OPENVPN_PASSWORD: <REDACTED>
  OPENVPN_USERNAME: <REDACTED>

mushuthecat commented 1 year ago

hi,

extract from my docker-compose.yaml if it can help with my working config

 environment:
      - TZ=Europe/Paris
      - OPENVPN_PROVIDER=NORDVPN
      - OPENVPN_USERNAME=newuser
      - OPENVPN_PASSWORD=newpassword
      - LOCAL_NETWORK=your local network
      - NORDVPN_COUNTRY=CH
      - NORDVPN_CATEGORY=legacy_p2p
      - NORDVPN_PROTOCOL=udp
      - GLOBAL_APPLY_PERMISSIONS=true
      - TRANSMISSION_RPC_PORT=9091
      - TRANSMISSION_DOWNLOAD_DIR=/data/completed
      - TRANSMISSION_INCOMPLETE_DIR=/data/incomplete
      - TRANSMISSION_WATCH_DIR=/data/watch
      - CREATE_TUN_DEVICE=true
      - HEALTH_CHECK_HOST=google.com
      - ENABLE_UFW=false
      - UFW_ALLOW_GW_NET=false
      - UFW_DISABLE_IPTABLES_REJECT=false
      - WEBPROXY_ENABLED=false
      - WEBPROXY_PORT=8888
      - LOG_TO_STDOUT=false
      - PEER_DNS=true
      - PEER_DNS_PIN_ROUTES=true
      - SELFHEAL=false
    dns:
      - 1.1.1.1
      - 1.0.0.1

Your logs are explicit auth failed

did you follow the process by creating a new credential from the nord vpn dashboard ?

You can also try to delete all your container and folder and start a new one from scratch to avoid any error...

FYI: my new user and password do not contains special caracters is it also your case ?

x-real-ip commented 1 year ago

hi,

extract from my docker-compose.yaml if it can help with my working config

 environment:
      - TZ=Europe/Paris
      - OPENVPN_PROVIDER=NORDVPN
      - OPENVPN_USERNAME=newuser
      - OPENVPN_PASSWORD=newpassword
      - LOCAL_NETWORK=your local network
      - NORDVPN_COUNTRY=CH
      - NORDVPN_CATEGORY=legacy_p2p
      - NORDVPN_PROTOCOL=udp
      - GLOBAL_APPLY_PERMISSIONS=true
      - TRANSMISSION_RPC_PORT=9091
      - TRANSMISSION_DOWNLOAD_DIR=/data/completed
      - TRANSMISSION_INCOMPLETE_DIR=/data/incomplete
      - TRANSMISSION_WATCH_DIR=/data/watch
      - CREATE_TUN_DEVICE=true
      - HEALTH_CHECK_HOST=google.com
      - ENABLE_UFW=false
      - UFW_ALLOW_GW_NET=false
      - UFW_DISABLE_IPTABLES_REJECT=false
      - WEBPROXY_ENABLED=false
      - WEBPROXY_PORT=8888
      - LOG_TO_STDOUT=false
      - PEER_DNS=true
      - PEER_DNS_PIN_ROUTES=true
      - SELFHEAL=false
    dns:
      - 1.1.1.1
      - 1.0.0.1

Your logs are explicit auth failed

did you follow the process by creating a new credential from the nord vpn dashboard ?

You can also try to delete all your container and folder and start a new one from scratch to avoid any error...

Thanks, but i tried all that, copied the service credentials and start a fresh container with an empty volume mounted without any persistent old files/storage. My credentials doesn't contains any special characters too.

TaTaSuZette commented 1 year ago

hi, extract from my docker-compose.yaml if it can help with my working config
 environment:
      - TZ=Europe/Paris
      - OPENVPN_PROVIDER=NORDVPN
      - OPENVPN_USERNAME=newuser
      - OPENVPN_PASSWORD=newpassword
      - LOCAL_NETWORK=your local network
      - NORDVPN_COUNTRY=CH
      - NORDVPN_CATEGORY=legacy_p2p
      - NORDVPN_PROTOCOL=udp
      - GLOBAL_APPLY_PERMISSIONS=true
      - TRANSMISSION_RPC_PORT=9091
      - TRANSMISSION_DOWNLOAD_DIR=/data/completed
      - TRANSMISSION_INCOMPLETE_DIR=/data/incomplete
      - TRANSMISSION_WATCH_DIR=/data/watch
      - CREATE_TUN_DEVICE=true
      - HEALTH_CHECK_HOST=google.com
      - ENABLE_UFW=false
      - UFW_ALLOW_GW_NET=false
      - UFW_DISABLE_IPTABLES_REJECT=false
      - WEBPROXY_ENABLED=false
      - WEBPROXY_PORT=8888
      - LOG_TO_STDOUT=false
      - PEER_DNS=true
      - PEER_DNS_PIN_ROUTES=true
      - SELFHEAL=false
    dns:
      - 1.1.1.1
      - 1.0.0.1
Your logs are explicit auth failed did you follow the process by creating a new credential from the nord vpn dashboard ? You can also try to delete all your container and folder and start a new one from scratch to avoid any error...
Thanks, but i tried all that, copied the service credentials and start a fresh container with an empty volume mounted without any persistent old files/storage. My credentials doesn't contains any special characters too.

Did you try reseting your password and get new credentials from nordvpn ?

andsoitgoes commented 1 year ago

Hi,

Can't see the OPENVPN_USERNAME and OPENVPN_PASSWORD lines in your docker file ? Did you remove it for the post or is it missing from your config ?

Regards,

I removed it for the post

x-real-ip commented 1 year ago

Thanks, i reset my username and password and it is working now 😅

andsoitgoes commented 1 year ago

Thanks, i reset my username and password and it is working now 😅

SAME!

also it would have been good if I went back to, oh I dunno, PUTTING MY CREDENTIALS in.

I put my Nord password into the bloody RPC login page... I'm so dumb.

demesm commented 1 year ago

I keep seeing you guys say get new creds, but from what I see once you get them there is no way to change it

andsoitgoes commented 1 year ago

I keep seeing you guys say get new creds, but from what I see once you get them there is no way to change it

Mine only started working once I changed my default Nord password.

Try that. Don't need to get new credentials although you will once you change your password, it's what happened to me.

nikscave commented 1 year ago

steps that worked for me with the docker-compose.yml setup:

replace creds with new service creds as per nord and above.
run "docker restart"
check new creds are pulling through by checking the latest openvpn-credentials.txt created in /var/lib/docker..... (find / -name openvpn-credentials.txt)
run "docker ps" to grab container ID
stop container with "docker stop [container ID]"
wait 2 hours
run "docker start [container ID]"

andsoitgoes commented 1 year ago

Hi - This has started happening again. I've checked ALL my settings and everything should be working fine - but god, I don't know what the heck is going on with this, it makes no sense!

I changed my password to reset the credentials and tried with the new credentials, still no dice.

What am I doing wrong? Log files at bottom.

sudo docker run --name=transmission \
--cap-add=NET_ADMIN -d \
--dns 8.8.8.8 \
--dns 8.8.4.4 \
--restart=always \
-v /mnt/media/downloads/:/data \
-v /home/pi/transmission/:/config \
-v /mnt/video/:/video \
-v /mnt/media/tv/:/tv \
-v /etc/localtime:/etc/localtime:ro \
-e CREATE_TUN_DEVICE=true \
-e OPENVPN_USERNAME=XXXXX \
-e OPENVPN_PASSWORD=XXXXXX \
-e OPENVPN_PROVIDER=NORDVPN \
-e NORDVPN_COUNTRY=CA \
-e NORDVPN_CATEGORY=legacy_p2p \
-e NORDVPN_PROTOCOL=tcp \
-e WEBPROXY_ENABLED=false \
-e TRANSMISSION_DOWNLOAD_DIR=/data \
-e TRANSMISSION_INCOMPLETE_DIR=/data/incomplete \
-e LOCAL_NETWORK=10.0.0.0/24 \
-e TRANSMISSION_RPC_AUTHENTICATION_REQUIRED=true \
-e TRANSMISSION_RPC_ENABLED=true \
-e TRANSMISSION_RPC_USERNAME=XXXX \
-e TRANSMISSION_RPC_PASSWORD=XXXXX \
-e TRANSMISSION_PEER_PORT_RANDOM_ON_START=false \
--sysctl net.ipv6.conf.all.disable_ipv6=0 \
--log-driver json-file \
--log-opt max-size=10m \
-p 9091:9091 \
haugene/transmission-openvpn:latest

INFO: OVPN: Checking curl installation
INFO: OVPN: DNS resolution ok
INFO: OVPN: ok, configurations download site reachable
INFO: OVPN: Removing existing configs in /etc/openvpn/nordvpn
parse error: Invalid numeric literal at line 1, column 7
Starting container with revision: 48299204d160d2d699ce6dd5ccdfcba0ecf13c83
TRANSMISSION_HOME is currently set to: /config/transmission-home
WARNING: Deprecated. Found old default transmission-home folder at /data/transmission-home, setting this as TRANSMISSION_HOME. This might break in future versions.
We will fallback to this directory as long as the folder exists. Please consider moving it to /config/transmission-home
Creating TUN device /dev/net/tun
Using OpenVPN provider: NORDVPN
Running with VPN_CONFIG_SOURCE auto
Provider NORDVPN has a bundled setup script. Defaulting to internal config
Executing setup script for NORDVPN
/etc/openvpn/nordvpn/..
INFO: OVPN: Checking curl installation
INFO: OVPN: DNS resolution ok
INFO: OVPN: ok, configurations download site reachable
INFO: OVPN: Removing existing configs in /etc/openvpn/nordvpn
parse error: Invalid numeric literal at line 1, column 7

I've even checked the OpenVPN credentials text file, and that's showing the correct credentials... I'm at a complete loss.

edgd1er commented 1 year ago

Hi - This has started happening again. I've checked ALL my settings and everything should be working fine - but god, I don't know what the heck is going on with this, it makes no sense!

I changed my password to reset the credentials and tried with the new credentials, still no dice.

What am I doing wrong? Log files at bottom.

sudo docker run --name=transmission \
--cap-add=NET_ADMIN -d \
--dns 8.8.8.8 \
--dns 8.8.4.4 \
--restart=always \
-v /mnt/media/downloads/:/data \
-v /home/pi/transmission/:/config \
-v /mnt/video/:/video \
-v /mnt/media/tv/:/tv \
-v /etc/localtime:/etc/localtime:ro \
-e CREATE_TUN_DEVICE=true \
-e OPENVPN_USERNAME=XXXXX \
-e OPENVPN_PASSWORD=XXXXXX \
-e OPENVPN_PROVIDER=NORDVPN \
-e NORDVPN_COUNTRY=CA \
-e NORDVPN_CATEGORY=legacy_p2p \
-e NORDVPN_PROTOCOL=tcp \
-e WEBPROXY_ENABLED=false \
-e TRANSMISSION_DOWNLOAD_DIR=/data \
-e TRANSMISSION_INCOMPLETE_DIR=/data/incomplete \
-e LOCAL_NETWORK=10.0.0.0/24 \
-e TRANSMISSION_RPC_AUTHENTICATION_REQUIRED=true \
-e TRANSMISSION_RPC_ENABLED=true \
-e TRANSMISSION_RPC_USERNAME=XXXX \
-e TRANSMISSION_RPC_PASSWORD=XXXXX \
-e TRANSMISSION_PEER_PORT_RANDOM_ON_START=false \
--sysctl net.ipv6.conf.all.disable_ipv6=0 \
--log-driver json-file \
--log-opt max-size=10m \
-p 9091:9091 \
haugene/transmission-openvpn:latest

INFO: OVPN: Checking curl installation
INFO: OVPN: DNS resolution ok
INFO: OVPN: ok, configurations download site reachable
INFO: OVPN: Removing existing configs in /etc/openvpn/nordvpn
parse error: Invalid numeric literal at line 1, column 7
Starting container with revision: 48299204d160d2d699ce6dd5ccdfcba0ecf13c83
TRANSMISSION_HOME is currently set to: /config/transmission-home
WARNING: Deprecated. Found old default transmission-home folder at /data/transmission-home, setting this as TRANSMISSION_HOME. This might break in future versions.
We will fallback to this directory as long as the folder exists. Please consider moving it to /config/transmission-home
Creating TUN device /dev/net/tun
Using OpenVPN provider: NORDVPN
Running with VPN_CONFIG_SOURCE auto
Provider NORDVPN has a bundled setup script. Defaulting to internal config
Executing setup script for NORDVPN
/etc/openvpn/nordvpn/..
INFO: OVPN: Checking curl installation
INFO: OVPN: DNS resolution ok
INFO: OVPN: ok, configurations download site reachable
INFO: OVPN: Removing existing configs in /etc/openvpn/nordvpn
parse error: Invalid numeric literal at line 1, column 7

I've even checked the OpenVPN credentials text file, and that's showing the correct credentials... I'm at a complete loss.

Nordvpn is blocking you because of too many request to nordvpn api due to too many container reboot due to invalid creds. activate debug to have more information on logs. http://haugene.github.io/docker-transmission-openvpn/config-options/#debugging https://github.com/haugene/docker-transmission-openvpn/issues/2642 http://haugene.github.io/docker-transmission-openvpn/provider-specific/#nordvpn

andsoitgoes commented 1 year ago

Thanks. I manually shut down the container last night after trying to roll back.

I don't get it though, when I updated the credentials were correct, and this was still happening.

I'll activate debug tonight and give it another shot. Hopefully the time it's been out of commission will be enough to reset things.

andsoitgoes commented 1 year ago

transmission_logs.txt

Tossed in the logs, I've emailed Nord to see if they can do anything to allow me to bypass it but I am willing to try ANYTHING!

Minor edit - Saw on the NordVPN they recommend changing the password, which I did. Updated credentials and same error. Again, I'd held off since last night before I tried to reconnect.

edgd1er commented 1 year ago

transmission_logs.txt

Tossed in the logs, I've emailed Nord to see if they can do anything to allow me to bypass it but I am willing to try ANYTHING!

Minor edit - Saw on the NordVPN they recommend changing the password, which I did. Updated credentials and same error. Again, I'd held off since last night before I tried to reconnect.

You are still blocked by the api... The log joined to the issue might not be the first after the container restart. Something is triggering the api protection.

few thing to try:

Nordvpn has changed its rules, and login/password are not accepted anymore, you need to get the service login/password. https://nordvpn.nanorep.co/storage/nr1/kb/3E6DB546/3E6DB64A/6FE5E9EA/6/3.png
Even easier and safer, create a token and log with it: https://support.nordvpn.com/Connectivity/Linux/2010688322/How-to-log-in-to-NordVPN-on-Linux-devices-without-a-GUI.htm
as a temporary workaround, leave the api alone by downloading the config with this tool https://nordvpn.com/fr/servers/tools/ and try to setup a custom config: https://haugene.github.io/docker-transmission-openvpn/supported-providers/#using_a_local_single_ovpn_file_from_a_provider
When things settle down a littre, try to set NORDVPN_<COUNTRY,CATEGORY>, I didn't see any set in the log, even if it's not the root cause.
Do you have another container or device that use nordvpn's vpn ?

andsoitgoes commented 1 year ago

I am SUCH AN IDIOT.

Insert the morgan freeman meme "It was at this point, he knew he f***ed up"

I wasn't paying attention yesterday and accidentally loaded transmission on my old Pi that's just sitting and not doing anything of importance.

I didn't think anything of it until I looked after that final comment and saw it was hanging in "restarting"....

argh.

I did get the Service Credentials - but I can actually just download the custom config, I'm hoping that solves it if this doesn't work when I try again tomorrow.

I do have Nord set in the startup docker script I provided above, is there another way I should do it? Also, how long should I wait before retrying?

ilike2burnthing commented 1 year ago

The rate limiting increases with each successive failed auth, so those of us at the very start of the issue were able to give it 10mins and we were fine, some others that caught it after half a day had to wait a couple of hours. If you're looking at a day plus, maybe give it 4-5hrs, or overnight if it's that time where you are.

andsoitgoes commented 1 year ago

To quote the prophet Medea, hallelujer

It is WORKING, thank you all. I need to move that old Raspbery Pi in my Putty application, it's just in the worst place and I can't believe I screwed it up so badly! Thank you all for your help!!

haugene / docker-transmission-openvpn