search

haugene / vpn-configs-contrib

A collection of configs for various VPN providers
GNU General Public License v3.0
172 stars 739 forks source link

PRIVADO Vpn not work anymore ... without reason #252

Open Bschalck opened 7 months ago

Bschalck commented 7 months ago

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

docker run --cap-add=NET_ADMIN \ -v /data/Transmssion:/data \ -e OPENVPN_PROVIDER=PRIVADO \ -e OPENVPN_CONFIG=ams-005 \ -e OPENVPN_USERNAME=my_username_changed_here \ -e OPENVPN_PASSWORD='' \ -e LOCAL_NETWORK=192.168.1.0/24 \ -e TRANSMISSION_WATCH_DIR_FORCE_GENERIC=true \ -e TRANSMISSION_WATCH_DIR=/data/watch \ -e TRANSMISSION_RPC_USERNAME=username \ -e TRANSMISSION_RPC_PASSWORD= \ -e TRANSMISSION_RPC_AUTHENTICATION_REQUIRED=true \ -v /dev/net/tun:/dev/net/tun \ -e CREATE_TUN_DEVICE=false \ -p 9091:9091 \ haugene/transmission-openvpn

Current Behavior

it doesn't work :) The conf didn't change since 9 months without any problem.

It suddenly did not work since few days .

Expected Behavior

It should work like always :)

How have you tried to solve the problem?

I tryu to choose another config file, same issue :/

Log output

Starting container with revision: 81277fb6f8ae6aeb57f913172d4d45c7af8c0b31 TRANSMISSION_HOME is currently set to: /config/transmission-home Using OpenVPN provider: PRIVADO Running with VPN_CONFIG_SOURCE auto No bundled config script found for PRIVADO. Defaulting to external config Will get configs from https://github.com/haugene/vpn-configs-contrib.git Cloning https://github.com/haugene/vpn-configs-contrib.git into /config/vpn-configs-contrib Cloning into '/config/vpn-configs-contrib'... Updating files: 100% (7546/7546), done. Found configs for PRIVADO in /config/vpn-configs-contrib/openvpn/privado, will replace current content in /etc/openvpn/privado Starting OpenVPN using config ams-005.ovpn Modifying /etc/openvpn/privado/ams-005.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.1.0/24 via 172.17.0.1 dev eth0 2023-11-10 14:33:59 DEPRECATED OPTION: --cipher set to 'AES-256-CBC' but missing in --data-ciphers (AES-256-GCM:AES-128-GCM). Future OpenVPN version will ignore --cipher for cipher negotiations. Add 'AES-256-CBC' to --data-ciphers or change --cipher 'AES-256-CBC' to --data-ciphers-fallback 'AES-256-CBC' to silence this warning. 2023-11-10 14:33:59 OpenVPN 2.5.5 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Jul 14 2022 2023-11-10 14:33:59 library versions: OpenSSL 3.0.2 15 Mar 2022, LZO 2.10 2023-11-10 14:33:59 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts 2023-11-10 14:33:59 TCP/UDP: Preserving recently used remote address: [AF_INET]91.148.224.50:1194 2023-11-10 14:33:59 Socket Buffers: R=[212992->212992] S=[212992->212992] 2023-11-10 14:33:59 UDP link local: (not bound) 2023-11-10 14:33:59 UDP link remote: [AF_INET]91.148.224.50:1194 2023-11-10 14:34:59 [UNDEF] Inactivity timeout (--ping-exit), exiting 2023-11-10 14:34:59 SIGTERM[soft,ping-exit] received, process exiting

Environment

- OS: debian 11
- Docker:last version

Anything else?

thanks for your task :)

pkishino commented 7 months ago

looking at the logs you see it ends with a SIGTERM [ping-exit] ..this means the vpn server triggered this.. check with privado for newer configs most likely. Then you can try using a new one with CUSTOM provider as per wiki, if it works again, create a PR and we can update the configs here. thanks

Twit123 commented 3 months ago

Privado now has new configs and the file names have all changed. I've tried the UK ones using my own fork (which works) but I have no idea how to create a PR. The new configs are here https://privadovpn.com/apps/ovpn_configs.zip .

contagon commented 3 months ago

Some kind soul made an automatic update script in the privado directory; opened PR #278 that runs it and fixes this. Tested on one of the zurich configs and it worked.

contagon commented 2 months ago

278 was merged in - I believe this can be closed.