Closed campana-giuseppe closed 2 years ago
I don't think this is a problem with the configs - Windscribe works just fine for me, even with those exact servers. I would double-check your openvpn details - you haven't mixed them up by accident? And you're definitely using your openvpn credentials, not your normal Windscribe login, right? You can find them here if you're a pro subscriber.
One thing though: you've misspelt 'transmission' several times. Unsure if this is intentional or not, but you may be encountering issues with directories if not.
I suggest you make sure you are running latest or dev, according to logs above it's an AUTH_FAILED so provider is refusing your credentials, not a bug on the container end
I don't think this is a problem with the configs - Windscribe works just fine for me, even with those exact servers. I would double-check your openvpn details - you haven't mixed them up by accident? And you're definitely using your openvpn credentials, not your normal Windscribe login, right? You can find them here if you're a pro subscriber.
One thing though: you've misspelt 'transmission' several times. Unsure if this is intentional or not, but you may be encountering issues with directories if not.
I have the same problem, I don't have a Pro account, how do I get my OPENVPN CREDS at Windsribe without a Pro user???
have this provider 61gb per month free to use
Starting container with revision: 07f5a2b9aea5028c9bb75438c1552708e91dde71
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: WINDSCRIBE
Running with VPN_CONFIG_SOURCE auto
No bundled config script found for WINDSCRIBE. Defaulting to external config
Will get configs from https://github.com/haugene/vpn-configs-contrib.git
Repository is already cloned, checking for update
Already up to date.
Already on 'main'
Your branch is up to date with 'origin/main'.
Found configs for WINDSCRIBE in /config/vpn-configs-contrib/openvpn/windscribe, will replace current content in /etc/openvpn/windscribe
No VPN configuration provided. Using default.
Modifying /etc/openvpn/windscribe/default.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 192.168.0.0/24 via 172.18.0.1 dev eth0
2024-06-30 10:51:45 Note: Treating option '--ncp-ciphers' as '--data-ciphers' (renamed in OpenVPN 2.5).
2024-06-30 10:51:45 OpenVPN 2.5.9 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Sep 29 2023
2024-06-30 10:51:45 library versions: OpenSSL 3.0.2 15 Mar 2022, LZO 2.10
2024-06-30 10:51:45 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
2024-06-30 10:51:45 Outgoing Control Channel Authentication: Using 512 bit message hash 'SHA512' for HMAC authentication
2024-06-30 10:51:45 Incoming Control Channel Authentication: Using 512 bit message hash 'SHA512' for HMAC authentication
2024-06-30 10:51:45 TCP/UDP: Preserving recently used remote address: [AF_INET]103.108.92.83:1194
2024-06-30 10:51:45 Socket Buffers: R=[212992->212992] S=[212992->212992]
2024-06-30 10:51:45 UDP link local: (not bound)
2024-06-30 10:51:45 UDP link remote: [AF_INET]103.108.92.83:1194
2024-06-30 10:51:45 TLS: Initial packet from [AF_INET]103.108.92.83:1194, sid=76f96464 0a1dec28
2024-06-30 10:51:45 WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this
2024-06-30 10:51:46 VERIFY OK: depth=2, C=CA, ST=ON, L=Toronto, O=Windscribe Limited, OU=Systems, CN=Windscribe Node CA X1
2024-06-30 10:51:46 VERIFY OK: depth=1, C=CA, ST=ON, L=Toronto, O=Windscribe Limited, OU=Systems, CN=Windscribe Node CA X2
2024-06-30 10:51:46 VERIFY KU OK
2024-06-30 10:51:46 Validating certificate extended key usage
2024-06-30 10:51:46 ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication
2024-06-30 10:51:46 VERIFY EKU OK
2024-06-30 10:51:46 VERIFY X509NAME OK: C=CA, ST=ON, L=Toronto, O=Windscribe Limited, OU=Systems, CN=adl-354.windscribe.com
2024-06-30 10:51:46 VERIFY OK: depth=0, C=CA, ST=ON, L=Toronto, O=Windscribe Limited, OU=Systems, CN=adl-354.windscribe.com
2024-06-30 10:51:46 Control Channel: TLSv1.3, cipher TLSv1.3 TLS_AES_256_GCM_SHA384, peer certificate: 4096 bit RSA, signature: RSA-SHA256
2024-06-30 10:51:46 [adl-354.windscribe.com] Peer Connection Initiated with [AF_INET]103.108.92.83:1194
2024-06-30 10:51:47 SENT CONTROL [adl-354.windscribe.com]: 'PUSH_REQUEST' (status=1)
2024-06-30 10:51:48 AUTH: Received control message: AUTH_FAILED
2024-06-30 10:51:48 SIGTERM[soft,auth-failure] received, process exiting
Is there a pinned issue for this?
Is there an existing or similar issue for this?
Is there any comment in the documentation for this?
Is this related to the container/transmission?
Are you using the latest release?
Have you tried using the dev branch latest?
Config used
Current Behavior
I have tried using transmission with both Privado and Windscribe, everything seems to be fine until authentication. I get the same error in both cases:
Expected Behavior
To connect to the VPN
How have you tried to solve the problem?
Log output
Environment
Anything else?
No response