-
I'm trying to setup the service using Docker Compose. This is what I have so far: networks: # Probably needs to be removed — check later
default:
driver: bridge
external: false
name: openvpn-network
services:
transmission-openvpn:
cap_add:
- NET_ADMIN
container_name: transmission-openvpn
environment:
CREATE_TUN_DEVICE: "true"
LOCAL_NETWORK: "192.168.0.0/16" # Not sure about this one
OPENVPN_CONFIG: "Server1-TCP443"
OPENVPN_PASSWORD: "PASSWORD_FROM_FreeVPN.me"
OPENVPN_PROVIDER: "CUSTOM"
OPENVPN_USERNAME: "USER_FROM_FreeVPN.me"
image: docker.io/haugene/transmission-openvpn:5.3
logging:
driver: json-file
options:
max-size: 5M
ports:
- "9091:9091"
volumes:
- "${PWD}/assets/config/:/config"
- "${PWD}/assets/downloads/:/data"
- "${PWD}/assets/provider/FreeVPN.me/:/etc/openvpn/custom/" I don't have anything in [x80486@uplink:~/transmission-openvpn]$ ll assets/provider/FreeVPN.me/
total 44K
-r--r--r-- 1 x80486 5.2K Aug 30 20:06 Server1-TCP80.ovpn
-r--r--r-- 1 x80486 5.2K Aug 30 20:42 Server1-TCP443.ovpn
-r--r--r-- 1 x80486 5.1K Aug 30 19:36 Server1-UDP53.ovpn
-r--r--r-- 1 x80486 5.1K Aug 30 19:36 Server1-UDP40000.ovpn
-r--r--r-- 1 x80486 1.2K Aug 30 19:36 ca.crt
-r--r--r-- 1 x80486 1.2K Aug 30 19:36 client.crt
-r--r--r-- 1 x80486 1.7K Aug 30 19:36 client.key So far, I think I was able to (almost) put all the pieces together, but the container is not able to start correctly: [x80486@uplink:~]$ docker logs --follow transmission-openvpn
Starting container with revision: fd609f2ace1970858d3c32fcbd6c271b3d274d39
TRANSMISSION_HOME is currently set to: /config/transmission-home
Creating TUN device /dev/net/tun
Using OpenVPN provider: CUSTOM
Running with VPN_CONFIG_SOURCE auto
CUSTOM provider specified but not using default.ovpn, will try to find a valid config mounted to /etc/openvpn/custom
Starting OpenVPN using config Server1-TCP443.ovpn
Modifying /etc/openvpn/custom/Server1-TCP443.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/16 via 172.18.0.1 dev eth0
2025-08-31 00:42:31 Unrecognized option or missing or extra parameter(s) in /etc/openvpn/custom/Server1-TCP443.ovpn:18: block-outside-dns (2.5.11)
2025-08-31 00:42:31 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.
2025-08-31 00:42:31 OpenVPN 2.5.11 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Sep 17 2024
2025-08-31 00:42:31 library versions: OpenSSL 3.0.2 15 Mar 2022, LZO 2.10
2025-08-31 00:42:31 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
2025-08-31 00:42:31 WARNING: Your certificate has expired!
2025-08-31 00:42:31 Outgoing Control Channel Authentication: Using 256 bit message hash 'SHA256' for HMAC authentication
2025-08-31 00:42:31 Incoming Control Channel Authentication: Using 256 bit message hash 'SHA256' for HMAC authentication
2025-08-31 00:42:31 TCP/UDP: Preserving recently used remote address: [AF_INET]94.102.51.26:443
2025-08-31 00:42:31 Socket Buffers: R=[131072->131072] S=[16384->16384]
2025-08-31 00:42:31 Attempting to establish TCP connection with [AF_INET]94.102.51.26:443 [nonblock]
2025-08-31 00:42:31 TCP: connect to [AF_INET]94.102.51.26:443 failed: Connection refused
2025-08-31 00:42:31 SIGTERM[connection failed(soft),init_instance] received, process exiting I've also tried Is there a way to move forward with this setup? I'm unsure if this is a problem with the provider or something with the certificates 🤔 |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
There may be something wrong with that provider. I tried a different one, with the exact same configuration, adjusting the parameters (e.g.: username, password, *.ovpn files, etc.), and everything works fine. |
Beta Was this translation helpful? Give feedback.
There may be something wrong with that provider. I tried a different one, with the exact same configuration, adjusting the parameters (e.g.: username, password, *.ovpn files, etc.), and everything works fine.