anyone has expirience with protonvpn free? #2275

spupuz · 2022-06-10T08:46:20Z

spupuz
Jun 10, 2022

anyone has experience with protonvpn free?
i configured as a custom and i downloaded from proton page the proper file .ovpn and mapped a volume as explained with my path

Mount the volume Compose sample: - //openvpn/:/etc/openvpn/custom/

Starting container with revision: 94754fe91d3a430bafa6b0dec75f56ded43ef1df
Creating TUN device /dev/net/tun
Using OpenVPN provider: CUSTOM
Running with VPN_CONFIG_SOURCE auto
No bundled config script found for CUSTOM. Defaulting to external config
Downloading configs from https://github.com/haugene/vpn-configs-contrib/archive/main.zip into /tmp/tmp.CvY54Di4Qt
Extracting configs to /tmp/tmp.la0nFoihvi
ERROR: Could not find any configs for provider CUSTOM in downloaded configs
Cleanup: deleting /tmp/tmp.CvY54Di4Qt and /tmp/tmp.la0nFoihvi
Starting OpenVPN using config us-free-04.protonvpn.net.udp.ovpn
Modifying /etc/openvpn/custom/us-free-04.protonvpn.net.udp.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
Setting OpenVPN credentials...
adding route to local network 192.168.1.0/16 via 192.168.32.1 dev eth0
Error: Invalid prefix for given prefix length.
Fri Jun 10 10:39:55 2022 Multiple --up scripts defined.  The previously configured script is overridden.
Fri Jun 10 10:39:55 2022 OpenVPN 2.4.7 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Mar 22 2022
Fri Jun 10 10:39:55 2022 library versions: OpenSSL 1.1.1f  31 Mar 2020, LZO 2.10
Fri Jun 10 10:39:55 2022 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
Fri Jun 10 10:39:55 2022 Outgoing Control Channel Authentication: Using 512 bit message hash 'SHA512' for HMAC authentication
Fri Jun 10 10:39:55 2022 Incoming Control Channel Authentication: Using 512 bit message hash 'SHA512' for HMAC authentication
Fri Jun 10 10:39:55 2022 TCP/UDP: Preserving recently used remote address: [AF_INET]45.89.173.194:5060
Fri Jun 10 10:39:55 2022 Socket Buffers: R=[212992->212992] S=[212992->212992]
Fri Jun 10 10:39:55 2022 UDP link local: (not bound)
Fri Jun 10 10:39:55 2022 UDP link remote: [AF_INET]45.89.173.194:5060
Fri Jun 10 10:39:55 2022 TLS: Initial packet from [AF_INET]45.89.173.194:5060, sid=d4b17161 47c3e618
Fri Jun 10 10:39:55 2022 WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this
Fri Jun 10 10:39:56 2022 VERIFY OK: depth=2, C=CH, O=ProtonVPN AG, CN=ProtonVPN Root CA
Fri Jun 10 10:39:56 2022 VERIFY OK: depth=1, C=CH, O=ProtonVPN AG, CN=ProtonVPN Intermediate CA 1
Fri Jun 10 10:39:56 2022 VERIFY KU OK
Fri Jun 10 10:39:56 2022 Validating certificate extended key usage
Fri Jun 10 10:39:56 2022 ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication
Fri Jun 10 10:39:56 2022 VERIFY EKU OK
Fri Jun 10 10:39:56 2022 VERIFY OK: depth=0, CN=node-us-47.protonvpn.net
Fri Jun 10 10:39:56 2022 WARNING: 'link-mtu' is used inconsistently, local='link-mtu 1633', remote='link-mtu 1634'
Fri Jun 10 10:39:56 2022 WARNING: 'comp-lzo' is present in remote config but missing in local config, remote='comp-lzo'
Fri Jun 10 10:39:56 2022 Control Channel: TLSv1.3, cipher TLSv1.3 TLS_AES_256_GCM_SHA384, 4096 bit RSA
Fri Jun 10 10:39:56 2022 [node-us-47.protonvpn.net] Peer Connection Initiated with [AF_INET]45.89.173.194:5060
Fri Jun 10 10:39:57 2022 SENT CONTROL [node-us-47.protonvpn.net]: 'PUSH_REQUEST' (status=1)
Fri Jun 10 10:40:02 2022 SENT CONTROL [node-us-47.protonvpn.net]: 'PUSH_REQUEST' (status=1)
Fri Jun 10 10:40:07 2022 SENT CONTROL [node-us-47.protonvpn.net]: 'PUSH_REQUEST' (status=1)
Fri Jun 10 10:40:12 2022 SENT CONTROL [node-us-47.protonvpn.net]: 'PUSH_REQUEST' (status=1)
Fri Jun 10 10:40:17 2022 SENT CONTROL [node-us-47.protonvpn.net]: 'PUSH_REQUEST' (status=1)
Fri Jun 10 10:40:22 2022 SENT CONTROL [node-us-47.protonvpn.net]: 'PUSH_REQUEST' (status=1)
Fri Jun 10 10:40:27 2022 SENT CONTROL [node-us-47.protonvpn.net]: 'PUSH_REQUEST' (status=1)
Fri Jun 10 10:40:33 2022 SENT CONTROL [node-us-47.protonvpn.net]: 'PUSH_REQUEST' (status=1)
Fri Jun 10 10:40:38 2022 SENT CONTROL [node-us-47.protonvpn.net]: 'PUSH_REQUEST' (status=1)
Fri Jun 10 10:40:43 2022 SENT CONTROL [node-us-47.protonvpn.net]: 'PUSH_REQUEST' (status=1)
Fri Jun 10 10:40:48 2022 SENT CONTROL [node-us-47.protonvpn.net]: 'PUSH_REQUEST' (status=1)
Fri Jun 10 10:40:53 2022 SENT CONTROL [node-us-47.protonvpn.net]: 'PUSH_REQUEST' (status=1)
Fri Jun 10 10:40:58 2022 No reply from server after sending 12 push requests
Fri Jun 10 10:40:58 2022 SIGTERM[soft,no-push-reply] received, process exiting`
```

spupuz · 2022-06-10T14:56:56Z

spupuz
Jun 10, 2022
Author

i was able to make vpn login correctly but the the server web does not start and it stuck there:

Running with VPN_CONFIG_SOURCE auto
No bundled config script found for CUSTOM. Defaulting to external config
Downloading configs from https://github.com/haugene/vpn-configs-contrib/archive/main.zip into /tmp/tmp.jtMhLi0eDo
Extracting configs to /tmp/tmp.iFzeQAyx7j
ERROR: Could not find any configs for provider CUSTOM in downloaded configs
Cleanup: deleting /tmp/tmp.jtMhLi0eDo and /tmp/tmp.iFzeQAyx7j
Starting OpenVPN using config us-free-04.protonvpn.net.udp.ovpn
Modifying /etc/openvpn/custom/us-free-04.protonvpn.net.udp.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
Setting OpenVPN credentials...
adding route to local network 192.168.1.0/16 via 192.168.32.1 dev eth0
Error: Invalid prefix for given prefix length.
Fri Jun 10 14:42:40 2022 Multiple --up scripts defined.  The previously configured script is overridden.
Fri Jun 10 14:42:40 2022 OpenVPN 2.4.7 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Mar 22 2022
Fri Jun 10 14:42:40 2022 library versions: OpenSSL 1.1.1f  31 Mar 2020, LZO 2.10
Fri Jun 10 14:42:40 2022 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
Fri Jun 10 14:42:40 2022 Outgoing Control Channel Authentication: Using 512 bit message hash 'SHA512' for HMAC authentication
Fri Jun 10 14:42:40 2022 Incoming Control Channel Authentication: Using 512 bit message hash 'SHA512' for HMAC authentication
Fri Jun 10 14:42:40 2022 TCP/UDP: Preserving recently used remote address: [AF_INET]45.89.173.194:5060
Fri Jun 10 14:42:40 2022 Socket Buffers: R=[212992->212992] S=[212992->212992]
Fri Jun 10 14:42:40 2022 UDP link local: (not bound)
Fri Jun 10 14:42:40 2022 UDP link remote: [AF_INET]45.89.173.194:5060
Fri Jun 10 14:42:41 2022 TLS: Initial packet from [AF_INET]45.89.173.194:5060, sid=a792d5f1 a524a9d2
Fri Jun 10 14:42:41 2022 WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this
Fri Jun 10 14:42:42 2022 VERIFY OK: depth=2, C=CH, O=ProtonVPN AG, CN=ProtonVPN Root CA
Fri Jun 10 14:42:42 2022 VERIFY OK: depth=1, C=CH, O=ProtonVPN AG, CN=ProtonVPN Intermediate CA 1
Fri Jun 10 14:42:42 2022 VERIFY KU OK
Fri Jun 10 14:42:42 2022 Validating certificate extended key usage
Fri Jun 10 14:42:42 2022 ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication
Fri Jun 10 14:42:42 2022 VERIFY EKU OK
Fri Jun 10 14:42:42 2022 VERIFY OK: depth=0, CN=node-us-47.protonvpn.net
Fri Jun 10 14:42:43 2022 WARNING: 'link-mtu' is used inconsistently, local='link-mtu 1633', remote='link-mtu 1634'
Fri Jun 10 14:42:43 2022 WARNING: 'comp-lzo' is present in remote config but missing in local config, remote='comp-lzo'
Fri Jun 10 14:42:43 2022 Control Channel: TLSv1.3, cipher TLSv1.3 TLS_AES_256_GCM_SHA384, 4096 bit RSA
Fri Jun 10 14:42:43 2022 [node-us-47.protonvpn.net] Peer Connection Initiated with [AF_INET]45.89.173.194:5060
Fri Jun 10 14:42:44 2022 SENT CONTROL [node-us-47.protonvpn.net]: 'PUSH_REQUEST' (status=1)
Fri Jun 10 14:42:49 2022 SENT CONTROL [node-us-47.protonvpn.net]: 'PUSH_REQUEST' (status=1)
Fri Jun 10 14:42:54 2022 SENT CONTROL [node-us-47.protonvpn.net]: 'PUSH_REQUEST' (status=1)
Fri Jun 10 14:42:59 2022 SENT CONTROL [node-us-47.protonvpn.net]: 'PUSH_REQUEST' (status=1)
Fri Jun 10 14:43:04 2022 SENT CONTROL [node-us-47.protonvpn.net]: 'PUSH_REQUEST' (status=1)
Fri Jun 10 14:43:09 2022 SENT CONTROL [node-us-47.protonvpn.net]: 'PUSH_REQUEST' (status=1)
Fri Jun 10 14:43:14 2022 SENT CONTROL [node-us-47.protonvpn.net]: 'PUSH_REQUEST' (status=1)
Fri Jun 10 14:43:14 2022 PUSH: Received control message: 'PUSH_REPLY,dhcp-option DNS 10.26.0.1,sndbuf 524288,rcvbuf 524288,redirect-gateway def1,explicit-exit-notify,comp-lzo no,route-gateway 10.26.0.1,topology subnet,ping 10,ping-restart 60,socket-flags TCP_NODELAY,ifconfig 10.26.0.14 255.255.0.0,peer-id 655373,cipher AES-256-GCM'
Fri Jun 10 14:43:14 2022 OPTIONS IMPORT: timers and/or timeouts modified
Fri Jun 10 14:43:14 2022 OPTIONS IMPORT: explicit notify parm(s) modified
Fri Jun 10 14:43:14 2022 OPTIONS IMPORT: compression parms modified
Fri Jun 10 14:43:14 2022 OPTIONS IMPORT: --sndbuf/--rcvbuf options modified
Fri Jun 10 14:43:14 2022 Socket Buffers: R=[212992->425984] S=[212992->425984]
Fri Jun 10 14:43:14 2022 OPTIONS IMPORT: --socket-flags option modified
Fri Jun 10 14:43:14 2022 NOTE: setsockopt TCP_NODELAY=1 failed
Fri Jun 10 14:43:14 2022 OPTIONS IMPORT: --ifconfig/up options modified
Fri Jun 10 14:43:14 2022 OPTIONS IMPORT: route options modified
Fri Jun 10 14:43:14 2022 OPTIONS IMPORT: route-related options modified
Fri Jun 10 14:43:14 2022 OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified
Fri Jun 10 14:43:14 2022 OPTIONS IMPORT: peer-id set
Fri Jun 10 14:43:14 2022 OPTIONS IMPORT: adjusting link_mtu to 1656
Fri Jun 10 14:43:14 2022 OPTIONS IMPORT: data channel crypto options modified
Fri Jun 10 14:43:14 2022 Data Channel: using negotiated cipher 'AES-256-GCM'
Fri Jun 10 14:43:14 2022 Outgoing Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Fri Jun 10 14:43:14 2022 Incoming Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Fri Jun 10 14:43:14 2022 ROUTE_GATEWAY 192.168.32.1/255.255.240.0 IFACE=eth0 HWADDR=02:42:c0:a8:20:02
Fri Jun 10 14:43:14 2022 TUN/TAP device tun0 opened
Fri Jun 10 14:43:14 2022 TUN/TAP TX queue length set to 100
Fri Jun 10 14:43:14 2022 /sbin/ip link set dev tun0 up mtu 1500
Fri Jun 10 14:43:14 2022 /sbin/ip addr add dev tun0 10.26.0.14/16 broadcast 10.26.255.255
Fri Jun 10 14:43:14 2022 /etc/openvpn/update-resolv-conf tun0 1500 1584 10.26.0.14 255.255.0.0 init
Fri Jun 10 14:43:14 2022 /sbin/ip route add 45.89.173.194/32 via 192.168.32.1
Fri Jun 10 14:43:14 2022 /sbin/ip route add 0.0.0.0/1 via 10.26.0.1
Fri Jun 10 14:43:14 2022 /sbin/ip route add 128.0.0.0/1 via 10.26.0.1
Fri Jun 10 14:43:14 2022 Initialization Sequence Completed
Fri Jun 10 15:41:14 2022 VERIFY OK: depth=2, C=CH, O=ProtonVPN AG, CN=ProtonVPN Root CA
Fri Jun 10 15:41:14 2022 VERIFY OK: depth=1, C=CH, O=ProtonVPN AG, CN=ProtonVPN Intermediate CA 1
Fri Jun 10 15:41:14 2022 VERIFY KU OK
Fri Jun 10 15:41:14 2022 Validating certificate extended key usage
Fri Jun 10 15:41:14 2022 ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication
Fri Jun 10 15:41:14 2022 VERIFY EKU OK
Fri Jun 10 15:41:14 2022 VERIFY OK: depth=0, CN=node-us-47.protonvpn.net
Fri Jun 10 15:41:14 2022 WARNING: 'link-mtu' is used inconsistently, local='link-mtu 1633', remote='link-mtu 1634'
Fri Jun 10 15:41:14 2022 WARNING: 'comp-lzo' is present in remote config but missing in local config, remote='comp-lzo'
Fri Jun 10 15:41:14 2022 Outgoing Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Fri Jun 10 15:41:14 2022 Incoming Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Fri Jun 10 15:41:14 2022 Control Channel: TLSv1.3, cipher TLSv1.3 TLS_AES_256_GCM_SHA384, 4096 bit RSA
Fri Jun 10 16:39:45 2022 VERIFY OK: depth=2, C=CH, O=ProtonVPN AG, CN=ProtonVPN Root CA
Fri Jun 10 16:39:45 2022 VERIFY OK: depth=1, C=CH, O=ProtonVPN AG, CN=ProtonVPN Intermediate CA 1
Fri Jun 10 16:39:45 2022 VERIFY KU OK
Fri Jun 10 16:39:45 2022 Validating certificate extended key usage
Fri Jun 10 16:39:45 2022 ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication
Fri Jun 10 16:39:45 2022 VERIFY EKU OK
Fri Jun 10 16:39:45 2022 VERIFY OK: depth=0, CN=node-us-47.protonvpn.net
Fri Jun 10 16:39:45 2022 WARNING: 'link-mtu' is used inconsistently, local='link-mtu 1633', remote='link-mtu 1634'
Fri Jun 10 16:39:45 2022 WARNING: 'comp-lzo' is present in remote config but missing in local config, remote='comp-lzo'
Fri Jun 10 16:39:45 2022 Outgoing Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Fri Jun 10 16:39:45 2022 Incoming Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Fri Jun 10 16:39:45 2022 Control Channel: TLSv1.3, cipher TLSv1.3 TLS_AES_256_GCM_SHA384, 4096 bit RSA

1 reply

pkishino Jun 15, 2022
Collaborator

have you set LOCAL_NETWORK to 192.168.1.0/16 ?
that is not a valid subnet mask.. try 192.168.1.0/24 ...or 192.168.0.0/16 if you insist on such a wide subnet

ydeng11 · 2022-09-26T23:27:43Z

ydeng11
Sep 26, 2022

Hi - do you have any updates on this?

6 replies

ydeng11 Sep 27, 2022

Thx. I am wondering how he get the auth worked. I am blocked by auth now.
I put two line - username and password - in openvpn-credential.txt.
I am not sure if it is protonfree or my setting.

version: '3.3'
services:
  transmission-openvpn:
    cap_add:
      - NET_ADMIN
    volumes:
      - /home/abc/DockerFiles:/data
      - /home/abc/DockerFiles/us-free-21.protonvpn.net.udp.ovpn:/etc/openvpn/custom/default.ovpn
      - /home/abc/DockerFiles/openvpn-credentials.txt:/etc/openvpn/custom/openvpn-credential.txt
    environment:
      - OPENVPN_PROVIDER=custom
      - OPENVPN_CONFIG=default
      - OPENVPN_USERNAME=xx
      - OPENVPN_PASSWORD=xx
      - OPENVPN_OPTS=--inactive 3600 --ping 10 --ping-exit 60
      - LOCAL_NETWORK=192.168.1.0/24
      - PGID=xx
      - PUID=xx
      - CREATE_TUN_DEVICE=true
    logging:
      driver: json-file
      options:
        max-size: 10m
    ports:
      - '9091:9091'
    image: haugene/transmission-openvpn

And I think the credentials are good so I am confused by the 'AUTH-FAIL'

❯ docker compose up
[+] Running 1/0
 ⠿ Container dockerfiles-transmission-openvpn-1  Created                                                           0.0s
Attaching to dockerfiles-transmission-openvpn-1
dockerfiles-transmission-openvpn-1  | Starting container with revision: a95f586492b2b7e8ff2cc8ac7f91bc43c0cccc40
dockerfiles-transmission-openvpn-1  | Creating TUN device /dev/net/tun
dockerfiles-transmission-openvpn-1  | Using OpenVPN provider: CUSTOM
dockerfiles-transmission-openvpn-1  | Running with VPN_CONFIG_SOURCE auto
dockerfiles-transmission-openvpn-1  | No bundled config script found for CUSTOM. Defaulting to external config
dockerfiles-transmission-openvpn-1  | Downloading configs from https://github.com/haugene/vpn-configs-contrib/archive/main.zip into /tmp/tmp.rfVLbCMXrl
dockerfiles-transmission-openvpn-1  | Extracting configs to /tmp/tmp.jOrQVsHb5x
dockerfiles-transmission-openvpn-1  | ERROR: Could not find any configs for provider CUSTOM in downloaded configs
dockerfiles-transmission-openvpn-1  | Cleanup: deleting /tmp/tmp.rfVLbCMXrl and /tmp/tmp.jOrQVsHb5x
dockerfiles-transmission-openvpn-1  | Starting OpenVPN using config default.ovpn
dockerfiles-transmission-openvpn-1  | Modifying /etc/openvpn/custom/default.ovpn for best behaviour in this container
dockerfiles-transmission-openvpn-1  | Modification: Point auth-user-pass option to the username/password file
dockerfiles-transmission-openvpn-1  | sed: cannot rename /etc/openvpn/custom/sedhOfE8h: Device or resource busy
dockerfiles-transmission-openvpn-1  | Modification: Change ca certificate path
dockerfiles-transmission-openvpn-1  | sed: cannot rename /etc/openvpn/custom/sedEQMF6s: Device or resource busy
dockerfiles-transmission-openvpn-1  | Modification: Change ping options
dockerfiles-transmission-openvpn-1  | sed: cannot rename /etc/openvpn/custom/sedBzBjVx: Device or resource busy
dockerfiles-transmission-openvpn-1  | sed: cannot rename /etc/openvpn/custom/sedaojvXB: Device or resource busy
dockerfiles-transmission-openvpn-1  | sed: cannot rename /etc/openvpn/custom/sedfkJXBG: Device or resource busy
dockerfiles-transmission-openvpn-1  | sed: cannot rename /etc/openvpn/custom/sedSZvFmN: Device or resource busy
dockerfiles-transmission-openvpn-1  | Modification: Update/set resolv-retry to 15 seconds
dockerfiles-transmission-openvpn-1  | sed: cannot rename /etc/openvpn/custom/sedsrTJhR: Device or resource busy
dockerfiles-transmission-openvpn-1  | sed: cannot rename /etc/openvpn/custom/sedEzmkpX: Device or resource busy
dockerfiles-transmission-openvpn-1  | Modification: Change tls-crypt keyfile path
dockerfiles-transmission-openvpn-1  | sed: cannot rename /etc/openvpn/custom/sedw8gSh6: Device or resource busy
dockerfiles-transmission-openvpn-1  | Modification: Set output verbosity to 3
dockerfiles-transmission-openvpn-1  | sed: cannot rename /etc/openvpn/custom/sedsn8q09: Device or resource busy
dockerfiles-transmission-openvpn-1  | sed: cannot rename /etc/openvpn/custom/sedkH3YQf: Device or resource busy
dockerfiles-transmission-openvpn-1  | Modification: Remap SIGUSR1 signal to SIGTERM, avoid OpenVPN restart loop
dockerfiles-transmission-openvpn-1  | sed: cannot rename /etc/openvpn/custom/sedd6rA7j: Device or resource busy
dockerfiles-transmission-openvpn-1  | sed: cannot rename /etc/openvpn/custom/sedY39z7m: Device or resource busy
dockerfiles-transmission-openvpn-1  | Setting OpenVPN credentials...
dockerfiles-transmission-openvpn-1  | adding route to local network 192.168.1.0/24 via 172.19.0.1 dev eth0
dockerfiles-transmission-openvpn-1  | Tue Sep 27 00:15:16 2022 Multiple --up scripts defined.  The previously configured script is overridden.
dockerfiles-transmission-openvpn-1  | Tue Sep 27 00:15:16 2022 WARNING: file '/etc/openvpn/custom/openvpn-credential.txt' is group or others accessible
dockerfiles-transmission-openvpn-1  | Tue Sep 27 00:15:16 2022 OpenVPN 2.4.7 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Mar 22 2022
dockerfiles-transmission-openvpn-1  | Tue Sep 27 00:15:16 2022 library versions: OpenSSL 1.1.1f  31 Mar 2020, LZO 2.10
dockerfiles-transmission-openvpn-1  | Tue Sep 27 00:15:16 2022 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
dockerfiles-transmission-openvpn-1  | Tue Sep 27 00:15:16 2022 Outgoing Control Channel Authentication: Using 512 bit message hash 'SHA512' for HMAC authentication
dockerfiles-transmission-openvpn-1  | Tue Sep 27 00:15:16 2022 Incoming Control Channel Authentication: Using 512 bit message hash 'SHA512' for HMAC authentication
dockerfiles-transmission-openvpn-1  | Tue Sep 27 00:15:16 2022 TCP/UDP: Preserving recently used remote address: [AF_INET]37.19.199.139:80
dockerfiles-transmission-openvpn-1  | Tue Sep 27 00:15:16 2022 Socket Buffers: R=[212992->212992] S=[212992->212992]
dockerfiles-transmission-openvpn-1  | Tue Sep 27 00:15:16 2022 UDP link local: (not bound)
dockerfiles-transmission-openvpn-1  | Tue Sep 27 00:15:16 2022 UDP link remote: [AF_INET]37.19.199.139:80
dockerfiles-transmission-openvpn-1  | Tue Sep 27 00:15:16 2022 TLS: Initial packet from [AF_INET]37.19.199.139:80, sid=de8f80ca efe1cda2
dockerfiles-transmission-openvpn-1  | Tue Sep 27 00:15:16 2022 WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this
dockerfiles-transmission-openvpn-1  | Tue Sep 27 00:15:16 2022 VERIFY OK: depth=2, C=CH, O=ProtonVPN AG, CN=ProtonVPN Root CA
dockerfiles-transmission-openvpn-1  | Tue Sep 27 00:15:16 2022 VERIFY OK: depth=1, C=CH, O=ProtonVPN AG, CN=ProtonVPN Intermediate CA 1
dockerfiles-transmission-openvpn-1  | Tue Sep 27 00:15:16 2022 VERIFY KU OK
dockerfiles-transmission-openvpn-1  | Tue Sep 27 00:15:16 2022 Validating certificate extended key usage
dockerfiles-transmission-openvpn-1  | Tue Sep 27 00:15:16 2022 ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication
dockerfiles-transmission-openvpn-1  | Tue Sep 27 00:15:16 2022 VERIFY EKU OK
dockerfiles-transmission-openvpn-1  | Tue Sep 27 00:15:16 2022 VERIFY OK: depth=0, CN=node-us-142.protonvpn.net
dockerfiles-transmission-openvpn-1  | Tue Sep 27 00:15:16 2022 WARNING: 'link-mtu' is used inconsistently, local='link-mtu 1633', remote='link-mtu 1634'
dockerfiles-transmission-openvpn-1  | Tue Sep 27 00:15:16 2022 WARNING: 'comp-lzo' is present in remote config but missing in local config, remote='comp-lzo'
dockerfiles-transmission-openvpn-1  | Tue Sep 27 00:15:16 2022 Control Channel: TLSv1.3, cipher TLSv1.3 TLS_AES_256_GCM_SHA384, 4096 bit RSA
dockerfiles-transmission-openvpn-1  | Tue Sep 27 00:15:16 2022 [node-us-142.protonvpn.net] Peer Connection Initiated with [AF_INET]37.19.199.139:80
dockerfiles-transmission-openvpn-1  | Tue Sep 27 00:15:17 2022 SENT CONTROL [node-us-142.protonvpn.net]: 'PUSH_REQUEST' (status=1)
dockerfiles-transmission-openvpn-1  | Tue Sep 27 00:15:22 2022 SENT CONTROL [node-us-142.protonvpn.net]: 'PUSH_REQUEST' (status=1)
dockerfiles-transmission-openvpn-1  | Tue Sep 27 00:15:23 2022 AUTH: Received control message: AUTH_FAILED
dockerfiles-transmission-openvpn-1  | Tue Sep 27 00:15:23 2022 SIGTERM[soft,auth-failure] received, process exiting
dockerfiles-transmission-openvpn-1 exited with code 0

pkishino Sep 27, 2022
Collaborator

check for special characters in U/PW
why are you mounting the credentials file AND passing them in as env variables? drop the mount and check permissions on the ovpn file..you can see the modification script failing to edit it..

ydeng11 Sep 27, 2022

thx. figure out the reason. The protonvpn is using another u/pw for openvpn.
Now I am blocked by the webui. digging it

pkishino Sep 27, 2022
Collaborator

blocked? did you set u/pw for the webui via rpc?
or not loading? if not loading then you need to check your LOCAL_NETWORK and check if it's correctly set

ydeng11 Sep 27, 2022

Yeah. Let me be specific. Now I am stucked at 'initialization sequence completed'.
I try to curl localhost:9091 inside the container but got connection failed so I suppose web ui is up but reject me.
I set up LOCAL_NETWORK to 192.168.1.0/24,192.168.0.0/16 but doesn't work for me.
When I do `ip r' inside the container, I got more records than Haugene said in here before having LOCAL_NETWORK setup as

0.0.0.0/1 via 10.19.0.1 dev tun0
default via 172.19.0.1 dev eth0
10.19.0.0/16 dev tun0 proto kernel scope link src 10.19.0.11
37.19.199.139 via 172.19.0.1 dev eth0
128.0.0.0/1 via 10.19.0.1 dev tun0
172.19.0.0/16 dev eth0 proto kernel scope link src 172.19.0.2

BTW I am running inside WSL2. I am newbie to network so I am not sure I got it right for my local network. I just checked my router and its ip is 192.168.1.1. So I think I should use 192.168.1.0/24 which doesn't work yet.

pkishino · 2022-09-27T04:23:29Z

pkishino
Sep 27, 2022
Collaborator

did you check here: https://haugene.github.io/docker-transmission-openvpn/vpn-networking/ What is the ip of the docker container externally on the host? I've never used WSL so not sure if there is something that needs configuring there or so

…

Message ID: <haugene/docker-transmission-openvpn/repo-discussions/2275/comments/3739691 @github.com>

1 reply

ydeng11 Sep 27, 2022

Yeah. I checked. The ip of container is 172.19.0.0. I changed LOCAL_NETWORK to 172..0.0/16,172..1.0/24 but doesn't work as well.
I checked 'ss -nlp' inside container and it seems no process is listening on 9091.

It looks like transimission is still not up.

pkishino · 2022-10-11T08:34:28Z

pkishino
Oct 11, 2022
Collaborator

post the whole startup log please, also, you could try to ue the proxy container from the previous link

…

On Tue, Sep 27, 2022 at 1:54 PM Eugene ***@***.***> wrote: Yeah. I checked. The ip of container is 172.19.0.0. I changed LOCAL_NETWORK to 172.*.0.0/16,172.*.1.0/24 but doesn't work as well. I checked 'ss -nlp' inside container and it seems no process is listening on 9091. [image: WindowsTerminal_JiFis007YN] <https://user-images.githubusercontent.com/13889673/192435080-b9b765f0-ac3d-4bb0-b282-b196e4c8df1a.png> It looks like transimission is still not up. — Reply to this email directly, view it on GitHub <#2275 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA7OFYTXUTXXY66V6QD7F7LWAJ4ZBANCNFSM5YM5TBKA> . You are receiving this because you commented.Message ID: <haugene/docker-transmission-openvpn/repo-discussions/2275/comments/3739878 @github.com>

1 reply

ydeng11 Oct 11, 2022

Hi @pkishino - Thanks so much! I switch to separate vpn and transmission and route transmission to vpn container. It is working well now.

deathblade666 · 2023-09-15T23:19:35Z

deathblade666
Sep 15, 2023

fwiw i got it working by grabing one of the ovpn files from protons site, kept getting Auth_Fail otherwise you can grab it from the download page if you login to their website

0 replies

Uh oh!

anyone has expirience with protonvpn free? #2275

Uh oh!

Uh oh!

Replies: 5 comments · 9 replies

Uh oh!

spupuz Jun 10, 2022 Author

Uh oh!

pkishino Jun 15, 2022 Collaborator

Uh oh!

Uh oh!

Uh oh!

Uh oh!

pkishino Sep 27, 2022 Collaborator

Uh oh!

Uh oh!

pkishino Sep 27, 2022 Collaborator

Uh oh!

Uh oh!

Uh oh!

pkishino Sep 27, 2022 Collaborator

Uh oh!

Uh oh!

pkishino Oct 11, 2022 Collaborator

Uh oh!

Uh oh!

Replies: 5 comments 9 replies

spupuz
Jun 10, 2022
Author

pkishino Jun 15, 2022
Collaborator

pkishino Sep 27, 2022
Collaborator

pkishino Sep 27, 2022
Collaborator

pkishino
Sep 27, 2022
Collaborator

pkishino
Oct 11, 2022
Collaborator