You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've also confirmed on a port forwarding tester site that my VPN address + Peer listening port is open
Log output
Attaching to transmission-docker_transmission-openvpn_1
transmission-openvpn_1 | Starting container with revision: 42eb2ee94ef9a3ce45bdccb308f9387b36c4f6e0
transmission-openvpn_1 | TRANSMISSION_HOME is currently set to: /config/transmission-home
transmission-openvpn_1 | Creating TUN device /dev/net/tun
transmission-openvpn_1 | Using OpenVPN provider: CUSTOM
transmission-openvpn_1 | Running with VPN_CONFIG_SOURCE auto
transmission-openvpn_1 | CUSTOM provider specified but not using default.ovpn, will try to find a valid config mounted to /etc/openvpn/custom
transmission-openvpn_1 | Starting OpenVPN using config openvpn.ovpn
transmission-openvpn_1 | Modifying /etc/openvpn/custom/openvpn.ovpn for best behaviour in this container
transmission-openvpn_1 | Modification: Point auth-user-pass option to the username/password file
transmission-openvpn_1 | Modification: Change ca certificate path
transmission-openvpn_1 | Modification: Change ping options
transmission-openvpn_1 | Modification: Update/set resolv-retry to 15 seconds
transmission-openvpn_1 | Modification: Change tls-crypt keyfile path
transmission-openvpn_1 | Modification: Set output verbosity to 3
transmission-openvpn_1 | Modification: Remap SIGUSR1 signal to SIGTERM, avoid OpenVPN restart loop
transmission-openvpn_1 | Modification: Updating status for config failure detection
transmission-openvpn_1 | Setting OpenVPN credentials...
transmission-openvpn_1 | adding route to local network 192.168.0.0/16 via 172.20.0.1 dev eth0
transmission-openvpn_1 | 2023-05-29 15:18:42 WARNING: Compression for receiving enabled. Compression has been used in the past to break encryption. Sent packets are not compressed unless "allow-compression yes" is also set.
transmission-openvpn_1 | 2023-05-29 15:18:42 OpenVPN 2.5.5 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Jul 14 2022
transmission-openvpn_1 | 2023-05-29 15:18:42 library versions: OpenSSL 3.0.2 15 Mar 2022, LZO 2.10
transmission-openvpn_1 | 2023-05-29 15:18:42 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
transmission-openvpn_1 | 2023-05-29 15:18:42 TCP/UDP: Preserving recently used remote address: [AF_INET]37.48.111.205:1194
transmission-openvpn_1 | 2023-05-29 15:18:42 Socket Buffers: R=[131072->131072] S=[16384->16384]
transmission-openvpn_1 | 2023-05-29 15:18:42 Attempting to establish TCP connection with [AF_INET]37.48.111.205:1194 [nonblock]
transmission-openvpn_1 | 2023-05-29 15:18:43 TCP connection established with [AF_INET]37.48.111.205:1194
transmission-openvpn_1 | 2023-05-29 15:18:43 TCP_CLIENT link local: (not bound)
transmission-openvpn_1 | 2023-05-29 15:18:43 TCP_CLIENT link remote: [AF_INET]37.48.111.205:1194
transmission-openvpn_1 | 2023-05-29 15:18:43 TLS: Initial packet from [AF_INET]37.48.111.205:1194, sid=c87fda14 10e2cbe0
transmission-openvpn_1 | 2023-05-29 15:18:43 VERIFY OK: depth=1, C=EU, ST=EU, L=SeedHost, O=website, OU=seedhost.eu, CN=website CA, name=seedhost.eu, [email protected]
transmission-openvpn_1 | 2023-05-29 15:18:43 VERIFY KU OK
transmission-openvpn_1 | 2023-05-29 15:18:43 Validating certificate extended key usage
transmission-openvpn_1 | 2023-05-29 15:18:43 ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication
transmission-openvpn_1 | 2023-05-29 15:18:43 VERIFY EKU OK
transmission-openvpn_1 | 2023-05-29 15:18:43 VERIFY OK: depth=0, C=EU, ST=EU, L=SeedHost, O=website, OU=seedhost.eu, CN=server, name=seedhost.eu, [email protected]
transmission-openvpn_1 | 2023-05-29 15:18:44 Control Channel: TLSv1.2, cipher TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384, peer certificate: 2048 bit RSA, signature: RSA-SHA256
transmission-openvpn_1 | 2023-05-29 15:18:44 [server] Peer Connection Initiated with [AF_INET]37.48.111.205:1194
transmission-openvpn_1 | 2023-05-29 15:18:45 SENT CONTROL [server]: 'PUSH_REQUEST' (status=1)
transmission-openvpn_1 | 2023-05-29 15:18:45 PUSH: Received control message: 'PUSH_REPLY,redirect-gateway,dhcp-option DNS 8.8.8.8,route 10.8.0.1,topology net30,ping 10,ping-restart 120,ifconfig 10.8.0.14 10.8.0.13,peer-id 0,cipher AES-256-GCM'
transmission-openvpn_1 | 2023-05-29 15:18:45 OPTIONS IMPORT: timers and/or timeouts modified
transmission-openvpn_1 | 2023-05-29 15:18:45 OPTIONS IMPORT: --ifconfig/up options modified
transmission-openvpn_1 | 2023-05-29 15:18:45 OPTIONS IMPORT: route options modified
transmission-openvpn_1 | 2023-05-29 15:18:45 OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified
transmission-openvpn_1 | 2023-05-29 15:18:45 OPTIONS IMPORT: peer-id set
transmission-openvpn_1 | 2023-05-29 15:18:45 OPTIONS IMPORT: adjusting link_mtu to 1627
transmission-openvpn_1 | 2023-05-29 15:18:45 OPTIONS IMPORT: data channel crypto options modified
transmission-openvpn_1 | 2023-05-29 15:18:45 Outgoing Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
transmission-openvpn_1 | 2023-05-29 15:18:45 Incoming Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
transmission-openvpn_1 | 2023-05-29 15:18:45 net_route_v4_best_gw query: dst 0.0.0.0
transmission-openvpn_1 | 2023-05-29 15:18:45 net_route_v4_best_gw result: via 172.20.0.1 dev eth0
transmission-openvpn_1 | 2023-05-29 15:18:45 ROUTE_GATEWAY 172.20.0.1/255.255.0.0 IFACE=eth0 HWADDR=02:42:ac:14:00:02
transmission-openvpn_1 | 2023-05-29 15:18:45 TUN/TAP device tun0 opened
transmission-openvpn_1 | 2023-05-29 15:18:45 net_iface_mtu_set: mtu 1500 for tun0
transmission-openvpn_1 | 2023-05-29 15:18:45 net_iface_up: set tun0 up
transmission-openvpn_1 | 2023-05-29 15:18:45 net_addr_ptp_v4_add: 10.8.0.14 peer 10.8.0.13 dev tun0
transmission-openvpn_1 | 2023-05-29 15:18:47 net_route_v4_add: 37.48.111.205/32 via 172.20.0.1 dev [NULL] table 0 metric -1
transmission-openvpn_1 | 2023-05-29 15:18:47 net_route_v4_del: 0.0.0.0/0 via 172.20.0.1 dev [NULL] table 0 metric -1
transmission-openvpn_1 | 2023-05-29 15:18:47 net_route_v4_add: 0.0.0.0/0 via 10.8.0.13 dev [NULL] table 0 metric -1
transmission-openvpn_1 | 2023-05-29 15:18:47 net_route_v4_add: 10.8.0.1/32 via 10.8.0.13 dev [NULL] table 0 metric -1
transmission-openvpn_1 | RTNETLINK answers: File exists
transmission-openvpn_1 | Up script executed with device=tun0 ifconfig_local=10.8.0.14
transmission-openvpn_1 | Updating TRANSMISSION_BIND_ADDRESS_IPV4 to the ip of tun0 : 10.8.0.14
transmission-openvpn_1 |
transmission-openvpn_1 | -------------------------------------
transmission-openvpn_1 | Transmission will run as
transmission-openvpn_1 | -------------------------------------
transmission-openvpn_1 | User name: root
transmission-openvpn_1 | User uid: 0
transmission-openvpn_1 | User gid: 0
transmission-openvpn_1 | -------------------------------------
transmission-openvpn_1 |
transmission-openvpn_1 | Updating Transmission settings.json with values from env variables
transmission-openvpn_1 | Attempting to use existing settings.json for Transmission
transmission-openvpn_1 | Successfully used existing settings.json /config/transmission-home/settings.json
transmission-openvpn_1 | Overriding bind-address-ipv4 because TRANSMISSION_BIND_ADDRESS_IPV4 is set to 10.8.0.14
transmission-openvpn_1 | Overriding download-dir because TRANSMISSION_DOWNLOAD_DIR is set to /data/completed
transmission-openvpn_1 | Overriding incomplete-dir because TRANSMISSION_INCOMPLETE_DIR is set to /data/incomplete
transmission-openvpn_1 | Overriding rpc-password because TRANSMISSION_RPC_PASSWORD is set to [REDACTED]
transmission-openvpn_1 | Overriding rpc-port because TRANSMISSION_RPC_PORT is set to 9091
transmission-openvpn_1 | Overriding rpc-username because TRANSMISSION_RPC_USERNAME is set to
transmission-openvpn_1 | Overriding utp-enabled because TRANSMISSION_UTP_ENABLED is set to false
transmission-openvpn_1 | Overriding watch-dir because TRANSMISSION_WATCH_DIR is set to /data/watch
transmission-openvpn_1 | sed'ing True to true
transmission-openvpn_1 | STARTING TRANSMISSION
transmission-openvpn_1 | Transmission startup script complete.
transmission-openvpn_1 | 2023-05-29 15:18:47 Initialization Sequence Completed
I created a test torrent that contains a simple txt file to ensure that my client can accept peer connections and upload. I've added my test torrent to this transmission client to seed it, then I added it to a known working rtorrent instance to download it from this transmission client. The rtorrent instance never connects to this transmission instance. I've also tried downloading from a qBittorrent client to connect to my transmission client, but it also never does.
The trackers I used for this test torrent are (I just googled for these):
It looks like Transmission can talk to these trackers:
The strange thing is, I can get it to upload a little bit on an Ubuntu iso torrent:
I was thinking it may have something to do with the RTNETLINK answers: File exists message in the docker logs, but I can access the Web UI just fine using the host IP 192.168.###.###, so I think that route is being created successfully and already exists when I bring up the container.
I added this entry of my Peer listening port to my docker-compose.yml file in the ports section:
- `51413:51413`
I also verified that ufw is not running on this host, so I don't think it's a firewall issue.
I also verified that the VPN's IP and port are open to the world:
I also verified that this VPN provider is bittorrent-friendly on a Windows machine using OpenVPN + qBittorrent GUI to seed, and that worked just fine while seeding
EDIT: more logs
I found out how to set the message level, by setting the TRANSMISSION_MESSAGE_LEVEL=3 environment variable in my docker-compose.yml file. Here are the error messages I'm seeing when it tries to communicate with the trackers:
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Docker compose file
Transmission Network settings
I've also confirmed on a port forwarding tester site that my VPN address +
Peer listening port
is openLog output
I created a test torrent that contains a simple txt file to ensure that my client can accept peer connections and upload. I've added my test torrent to this transmission client to seed it, then I added it to a known working
rtorrent
instance to download it from this transmission client. Thertorrent
instance never connects to this transmission instance. I've also tried downloading from a qBittorrent client to connect to my transmission client, but it also never does.The trackers I used for this test torrent are (I just googled for these):
It looks like Transmission can talk to these trackers:
The strange thing is, I can get it to upload a little bit on an Ubuntu iso torrent:
I was thinking it may have something to do with the
RTNETLINK answers: File exists
message in the docker logs, but I can access the Web UI just fine using the host IP192.168.###.###
, so I think that route is being created successfully and already exists when I bring up the container.I have attached the test torrent I'm using below:
test.txt.torrent.zip
A few more things I've tried
Peer listening port
to mydocker-compose.yml
file in theports
section:ufw
is not running on this host, so I don't think it's a firewall issue.EDIT: more logs
I found out how to set the message level, by setting the
TRANSMISSION_MESSAGE_LEVEL=3
environment variable in mydocker-compose.yml
file. Here are the error messages I'm seeing when it tries to communicate with the trackers:EDIT 2: ipv6
I tried enabling ipv6 for Docker daemon, and that got rid of the above
Couldn't connect socket ...
errors.That didn't fix actual real issue of not being able to upload, though.
Beta Was this translation helpful? Give feedback.
All reactions