Closed tim2thatom closed 3 years ago
Hmm. I don't know. PIA is really acting up these days. There could be a new instability in the image as well of course but it seems less likely at this point as it works well for many users on many providers. There is an issue with connecting to UDP trackers that I haven't gotten to the bottom of yet though. Users with different providers have the same issue. But you are not able to connect to any trackers at all?
Can you pull the image again to make sure that you are running the latest version? Not sure it will fix anything but from your logs you don't seem to be at the newest.
What are the error messages you got from the transmission log? Also, from the docker log seems you have some permission problem.
Thanks @haugene I wiped the images, container, and added the :latest tag. I'm currently running 93d0141d928ec661411e2c6f0e079aeff2c018dd. I tested another three torrents and all are still failing to connect to any trackers.
However I was able to connect to this test torrent at http://torrent.unix-ag.uni-kl.de/torrents/KNOPPIX_V8.6.1-2019-10-14-EN.torrent
Thanks, @RickyXwang those permission errors have been there for over two years, never caused an issue.
Hey, I'm having this exact issue too, a test torrent shows I'm connecting through PIA but I can't connect to any other torrents
I hadn't tried the PIA_OPENVPN_CONFIG_BUNDLE: "openvpn-ip-nextgen"
environment variable yet, on trying it I get this looping and erroring
Starting container with revision: c42e60cda031c612c9f572d87664f7dbdb9314fc
Using OpenVPN provider: PIA
Provider PIA has a custom setup script, executing it
Downloading OpenVPN config bundle openvpn-ip-nextgen into temporary file /tmp/tmp.hKoadO
Extract OpenVPN config bundle into PIA directory /etc/openvpn/pia
Starting OpenVPN using config Sweden.ovpn
Modifying /etc/openvpn/pia/Sweden.ovpn for best behaviour in this container
Setting OpenVPN credentials...
Fri Nov 13 01:12:37 2020 OpenVPN 2.4.9 x86_64-alpine-linux-musl [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [MH/PKTINFO] [AEAD] built on Apr 20 2020
Fri Nov 13 01:12:37 2020 library versions: OpenSSL 1.1.1g 21 Apr 2020, LZO 2.10
Fri Nov 13 01:12:37 2020 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
Fri Nov 13 01:12:37 2020 CRL: loaded 1 CRLs from file [[INLINE]]
Fri Nov 13 01:12:37 2020 TCP/UDP: Preserving recently used remote address: [AF_INET]46.246.3.150:1198
Fri Nov 13 01:12:37 2020 UDP link local: (not bound)
Fri Nov 13 01:12:37 2020 UDP link remote: [AF_INET]46.246.3.150:1198
Fri Nov 13 01:13:38 2020 [UNDEF] Inactivity timeout (--ping-exit), exiting
Fri Nov 13 01:13:38 2020 SIGTERM[soft,ping-exit] received, process exiting
Starting container with revision: c42e60cda031c612c9f572d87664f7dbdb9314fc
Using OpenVPN provider: PIA
Provider PIA has a custom setup script, executing it
Downloading OpenVPN config bundle openvpn-ip-nextgen into temporary file /tmp/tmp.HjcHhN
Extract OpenVPN config bundle into PIA directory /etc/openvpn/pia
Starting OpenVPN using config Sweden.ovpn
Modifying /etc/openvpn/pia/Sweden.ovpn for best behaviour in this container
Setting OpenVPN credentials...
Fri Nov 13 01:13:39 2020 OpenVPN 2.4.9 x86_64-alpine-linux-musl [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [MH/PKTINFO] [AEAD] built on Apr 20 2020
Fri Nov 13 01:13:39 2020 library versions: OpenSSL 1.1.1g 21 Apr 2020, LZO 2.10
Fri Nov 13 01:13:39 2020 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
Fri Nov 13 01:13:39 2020 CRL: loaded 1 CRLs from file [[INLINE]]
Fri Nov 13 01:13:39 2020 TCP/UDP: Preserving recently used remote address: [AF_INET]46.246.3.150:1198
Fri Nov 13 01:13:39 2020 UDP link local: (not bound)
Fri Nov 13 01:13:39 2020 UDP link remote: [AF_INET]46.246.3.150:1198
This is my config (it's ansible not docker compose but they work v similarly)
name: transmissionvpn
image: haugene/transmission-openvpn:dev
pull: yes
env:
PUID: "{{ uid }}"
PGID: "{{ gid }}"
VIRTUAL_HOST: "transmissionvpn.{{ user.domain }}"
VIRTUAL_PORT: "9091"
LETSENCRYPT_HOST: "transmissionvpn.{{ user.domain }}"
LETSENCRYPT_EMAIL: "{{ user.email }}"
UMASK_SET: "002"
CREATE_TUN_DEVICE: "true"
OPENVPN_PROVIDER: "{{ transmissionvpn.vpn_prov|default('pia',true) }}"
OPENVPN_USERNAME: "{{ transmissionvpn.vpn_user|default('username',true) }}"
OPENVPN_PASSWORD: "{{ transmissionvpn.vpn_pass|default('password',true) }}"
OPENVPN_CONFIG: "Sweden"
DISABLE_PORT_UPDATER: "no"
TRANSMISSION_ALT_SPEED_DOWN: "30"
TRANSMISSION_RATIO_LIMIT: "0"
TRANSMISSION_RATIO_LIMIT_ENABLED: "true"
TRANSMISSION_WATCH_DIR_ENABLED: "false"
TRANSMISSION_HOME: "/opt/transmissionvpn"
TZ: "{{ tz }}"
PIA_OPENVPN_CONFIG_BUNDLE: "openvpn-ip-nextgen"
volumes: "{{ default_volumes + torrents_downloads_path|default([]) }}"
labels:
"com.github.cloudbox.cloudbox_managed": "true"
capabilities:
- NET_ADMIN
networks:
- name: cloudbox
aliases:
- transmissionvpn
purge_networks: yes
restart_policy: always
state: started
I know it isn't much, but when it works on one torrent it kind of means that a lot is working. I mean, it has internet and it's connected to VPN. That's kind of the job of this image. The rest is up to OpenVPN, the provider and Transmission. Now, we've fucked things up before so I'm not ruling it out :laughing: But PIA is such a mess these days, so have you tried many servers (1,2,3,many) and had the same results?
I can report the same problem, I also cannot connect to udp trackers but vpn is setup correctly and torrents with http trackers work fine. (I'm having the issue with both PIA and NordVPN). On the other hand, if I spin up an alpine:3.12 image, install transmission-daemon/openvpn and set things up manually with a minimal configuration everything works perfectly (including udp trackers). So not sure why its not working properly on the main image. I don't think its its a routing problem, because I am able to connect to remote udp sockets from inside the container and successfully pass data.
I wrote to support, the root cause seems that somehow they are using Russian DNS from MTS??? This is blocking a lot of data and trackers also. You can test it e.g. by visiting https://lostfilm.tv under your container, you will be redirected to the Block Landing page of Russian provider under this link: http://blocked.mts.ru/?host=?url=http%3A%2F%2Flostfilm.tv. This is happens also when I use PIA Client on laptop.
Simple to test:
ports:
- "9092:8888"
....
environment:
- WEBPROXY_ENABLED=true
- WEBPROXY_PORT=8888
- WEBPROXY_USERNAME=proxyuser
- WEBPROXY_PASSWORD=somepassword
curl -x http://proxyuser:somepassword@127.0.0.1:9092 http://lostfilm.tv -L
-x to user proxy -L to follow redirect
There is also similar ticket here #1465
@GAS85 I can confirm my issue is the same, using that test, setting the DNS of the container to something else doesn't seem to override that though unfortunately, is this a setting we can change in openvpn or are we stuck waiting for PIA to sort it out ?
Scrap that I was being impatient, setting the dns servers on the containers gets torrents started for me, but I'm still hitting the mts.ru block page interestingly
@JackDallas Can you share what DNS servers you're using and how you're setting them?
Yes, I can confirm this is happening with my setup as well. No torrents downloading and all of them having issues with Announcing.
The http torrent that @tim2thatom posted I was able to get started though the :6969 port did not Announce either. Here is my docker-compose (I JUST added dns and it didn't resolve anything)
transmissionvpn:
image: haugene/transmission-openvpn:latest
container_name: transmissionvpn
restart: unless-stopped
cap_add:
- NET_ADMIN
logging:
driver: "json-file"
options:
max-size: "10m"
depends_on:
- "traefik"
- "organizrv2"
networks:
- traefik_proxy
ports:
- 9091:9091
environment:
- PUID=0
- PGID=0
- TRANSMISSION_WEB_UI=combustion
- CREATE_TUN_DEVICE=true
- OPENVPN_PROVIDER=PIA
- OPENVPN_CONFIG=US Seattle
- OPENVPN_USERNAME=user
- OPENVPN_PASSWORD=pass
- WEBPROXY_ENABLED=false
- LOCAL_NETWORK=192.168.1.0/24
- TRANSMISSION_INCOMPLETE_DIR=$userdir/Downloads/TOR
- TRANSMISSION_SCRIPT_TORRENT_DONE_ENABLED=true
- TRANSMISSION_SCRIPT_TORRENT_DONE_FILENAME=/scripts/on-complete.sh
- TRANSMISSION_RATIO_LIMIT_ENABLED=true
- TRANSMISSION_RATIO_LIMIT=2
- TRANSMISSION_SPEED_LIMIT_UP_ENABLED=true
- TRANSMISSION_SPEED_LIMIT_UP=3000
dns:
- 8.8.8.8
- 1.1.1.1
volumes:
- $userdir/transmission:/data
- /mnt/freenas:/mnt/freenas
- /etc/localtime:/etc/localtime:ro
- $userdir/scripts/on-complete.sh:/scripts/on-complete.sh
- $userdir/scripts/transmission-pre-start.sh:/scripts/transmission-pre-start.sh
Could the issue be stemming from this IPv6 error that i'm seeing below? I never needed IPv6 before...have been running this way for a year or two.
Provider PIA has a custom startup script, executing it,
Downloading OpenVPN config bundle openvpn-nextgen into temporary file /tmp/tmp.KPppnm,
Extract OpenVPN config bundle into PIA directory /etc/openvpn/pia,
Modify configs for this container,
Starting OpenVPN using config US Seattle.ovpn,
Setting OpenVPN credentials...,
adding route to local network 192.168.0.0/16 via 172.20.0.1 dev eth0,
Fri Nov 13 08:58:19 2020 OpenVPN 2.4.9 x86_64-alpine-linux-musl [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [MH/PKTINFO] [AEAD] built on Apr 20 2020,
Fri Nov 13 08:58:19 2020 library versions: OpenSSL 1.1.1g 21 Apr 2020, LZO 2.10,
Fri Nov 13 08:58:19 2020 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts,
Fri Nov 13 08:58:19 2020 CRL: loaded 1 CRLs from file [[INLINE]],
Fri Nov 13 08:58:19 2020 TCP/UDP: Preserving recently used remote address: [AF_INET]x.x.x.x:1198,
Fri Nov 13 08:58:19 2020 UDP link local: (not bound),
Fri Nov 13 08:58:19 2020 UDP link remote: [AF_INET]x.x.x.x:1198,
Fri Nov 13 08:58:19 2020 WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this,
Fri Nov 13 08:58:20 2020 [seattle401] Peer Connection Initiated with [AF_INET]x.x.x.x:1198,
Fri Nov 13 08:58:21 2020 OpenVPN ROUTE6: OpenVPN needs a gateway parameter for a --route-ipv6 option and no default was specified by either --route-ipv6-gateway or --ifconfig-ipv6 options,
Fri Nov 13 08:58:21 2020 OpenVPN ROUTE: failed to parse/resolve route for host/network: 2000::/3,
Fri Nov 13 08:58:21 2020 TUN/TAP device tun0 opened,
Fri Nov 13 08:58:21 2020 /sbin/ip link set dev tun0 up mtu 1500,
Fri Nov 13 08:58:21 2020 /sbin/ip addr add dev tun0 10.60.112.7/24 broadcast 10.60.112.255,
Fri Nov 13 08:58:21 2020 /etc/openvpn/tunnelUp.sh tun0 1500 1553 10.60.112.7 255.255.255.0 init,
Up script executed with tun0 1500 1553 10.60.112.7 255.255.255.0 init,
Updating TRANSMISSION_BIND_ADDRESS_IPV4 to the ip of tun0 : 10.60.112.7,
Using Combustion UI, overriding TRANSMISSION_WEB_HOME,
Updating Transmission settings.json with values from env variables,
Using existing settings.json for Transmission /data/transmission-home/settings.json,
Overriding bind-address-ipv4 because TRANSMISSION_BIND_ADDRESS_IPV4 is set to 10.60.112.7,
Overriding download-dir because TRANSMISSION_DOWNLOAD_DIR is set to /data/completed,
Overriding incomplete-dir because TRANSMISSION_INCOMPLETE_DIR is set to $user/Downloads/TOR,
Overriding ratio-limit because TRANSMISSION_RATIO_LIMIT is set to 2,
Overriding ratio-limit-enabled because TRANSMISSION_RATIO_LIMIT_ENABLED is set to true,
Overriding rpc-port because TRANSMISSION_RPC_PORT is set to 9091,
Overriding script-torrent-done-enabled because TRANSMISSION_SCRIPT_TORRENT_DONE_ENABLED is set to true,
Overriding script-torrent-done-filename because TRANSMISSION_SCRIPT_TORRENT_DONE_FILENAME is set to /scripts/on-complete.sh,
Overriding speed-limit-up because TRANSMISSION_SPEED_LIMIT_UP is set to 3000,
Overriding speed-limit-up-enabled because TRANSMISSION_SPEED_LIMIT_UP_ENABLED is set to true,
Overriding watch-dir because TRANSMISSION_WATCH_DIR is set to /data/watch,
sed'ing True to true,
,
-------------------------------------,
Transmission will run as,
-------------------------------------,
User name: root,
User uid: 0,
User gid: 0,
-------------------------------------,
,
STARTING TRANSMISSION,
Provider PIA has a script for automatic port forwarding. Will run it now.,
If you want to disable this, set environment variable DISABLE_PORT_UPDATER=yes,
Transmission startup script complete.,
Fri Nov 13 08:58:21 2020 WARNING: OpenVPN was configured to add an IPv6 route over tun0. However, no IPv6 has been configured for this interface, therefore the route installation may fail or may not work as expected.,
Fri Nov 13 08:58:21 2020 Initialization Sequence Completed,
yes: Broken pipe,
,
,
,
curl: (7) Failed to connect to 10.60.112.1 port 19999: Connection refused,
Fri Nov 13 08:58:26 PST 2020: getSignature error,
,
the has been a fatal_error,
date: invalid date '',
port is ,
curl: (7) Failed to connect to 10.60.112.1 port 19999: Connection refused,
Fri Nov 13 08:58:27 PST 2020: bindPort error,
,
the has been a fatal_error,
transmission auth not required,
waiting for transmission to become responsive,
setting transmission port to ,
localhost:9091/transmission/rpc/ responded: "success",
Checking port...,
Error: portTested: http error 400: Bad Request,
,
initial setup complete!,
,
waiting for rebind loop.................,
token expiry ,
remaining = -1605286718,
Fri Nov 13 08:58:38 PST 2020: Getting PF token,
curl: (7) Failed to connect to 10.60.112.1 port 19999: Connection refused,
Fri Nov 13 08:58:38 PST 2020: getSignature error,
,
the has been a fatal_error,
date: invalid date '',
Fri Nov 13 08:58:38 PST 2020: Obtained PF token. Expires at ,
curl: (7) Failed to connect to 10.60.112.1 port 19999: Connection refused,
Fri Nov 13 08:58:38 PST 2020: bindPort error,
,
the has been a fatal_error,
Fri Nov 13 08:58:38 PST 2020: Server accepted PF bind,
Fri Nov 13 08:58:38 PST 2020: Forwarding on port ,
Fri Nov 13 08:58:38 PST 2020: Rebind interval: 1800 seconds,
Seems to be related to this port 19999 having a connection refused.
I've been having similar issues for a few weeks now. While some (very few) torrents are able to connect to trackers and download, most can't and get stuck at "magnetized transfer - receiving metadata". I've tried using dev build, 3.1, latest etc. but no luck.
transmission-vpn:
container_name: transmission-vpn
#image: haugene/transmission-openvpn:dev
#image: haugene/transmission-openvpn:3.1
image: haugene/transmission-openvpn:latest
cap_add:
- NET_ADMIN
#devices:
#- /dev/net/tun
restart: always
ports:
- "9091:9091"
- "8888:8888"
dns:
- 1.1.1.1
#- 1.0.0.1
- 8.8.8.8
#- 8.8.4.4
volumes:
- /etc/localtime:/etc/localtime:ro
- ${USERDIR}/docker/transmission-vpn:/data
- ${USERDIR}/docker/shared:/shared
- /mnt/data/WD3tbdownloads:/data/watch
- /mnt/data/WD3tbdownloads/completed:/data/completed
- /mnt/data/WD3tbdownloads/incomplete:/data/incomplete
environment:
- OPENVPN_PROVIDER=PIA
- OPENVPN_USERNAME=user
- OPENVPN_PASSWORD=pass
- WEBPROXY_ENABLED=false
#- OPENVPN_CONFIG=US Seattle
#- OPENVPN_CONFIG=dummy
#- OPENVPN_CONFIG=CA Vancouver
- OPENVPN_OPTS=--inactive 3600 --ping 10 --ping-exit 60
- LOCAL_NETWORK=192.168.3.0/24
#- LOCAL_NETWORK=192.168.3.0/16
- PUID=${PUID}
- PGID=${PGID}
- TZ=${TZ}
- TRANSMISSION_RPC_AUTHENTICATION_REQUIRED=true
- TRANSMISSION_RPC_HOST_WHITELIST="127.0.0.1,192.168.3.57"
- TRANSMISSION_RPC_PASSWORD=pass
- TRANSMISSION_RPC_USERNAME=user
#- TRANSMISSION_UMASK=002
- TRANSMISSION_UMASK=2
#- TRANSMISSION_RATIO_LIMIT=1.00
#- TRANSMISSION_RATIO_LIMIT=1
#- TRANSMISSION_RATIO_LIMIT_ENABLED=true
logging:
driver: json-file
options:
max-size: 10m
logs:
Using OpenVPN provider: PIA,
Provider PIA has a custom startup script, executing it,
Downloading OpenVPN config bundle openvpn-nextgen into temporary file /tmp/tmp.jJbEhj,
Extract OpenVPN config bundle into PIA directory /etc/openvpn/pia,
Modify configs for this container,
No VPN configuration provided. Using default.,
Setting OpenVPN credentials...,
adding route to local network 192.168.3.0/24 via 172.18.0.1 dev eth0,
Fri Nov 13 09:11:36 2020 OpenVPN 2.4.9 x86_64-alpine-linux-musl [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [MH/PKTINFO] [AEAD] built on Apr 20 2020,
Fri Nov 13 09:11:36 2020 library versions: OpenSSL 1.1.1g 21 Apr 2020, LZO 2.10,
Fri Nov 13 09:11:36 2020 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts,
Fri Nov 13 09:11:36 2020 CRL: loaded 1 CRLs from file [[INLINE]],
Fri Nov 13 09:11:36 2020 TCP/UDP: Preserving recently used remote address: [AF_INET]45.132.143.231:1198,
Fri Nov 13 09:11:36 2020 UDP link local: (not bound),
Fri Nov 13 09:11:36 2020 UDP link remote: [AF_INET]45.132.143.231:1198,
Fri Nov 13 09:11:36 2020 WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this,
Fri Nov 13 09:11:36 2020 [bahamas401] Peer Connection Initiated with [AF_INET]45.132.143.231:1198,
Fri Nov 13 09:11:38 2020 TUN/TAP device tun0 opened,
Fri Nov 13 09:11:38 2020 /sbin/ip link set dev tun0 up mtu 1500,
Fri Nov 13 09:11:38 2020 /sbin/ip addr add dev tun0 10.1.112.11/24 broadcast 10.1.112.255,
Fri Nov 13 09:11:38 2020 /etc/openvpn/tunnelUp.sh tun0 1500 1558 10.1.112.11 255.255.255.0 init,
Up script executed with tun0 1500 1558 10.1.112.11 255.255.255.0 init,
Updating TRANSMISSION_BIND_ADDRESS_IPV4 to the ip of tun0 : 10.1.112.11,
Updating Transmission settings.json with values from env variables,
Using existing settings.json for Transmission /data/transmission-home/settings.json,
Overriding bind-address-ipv4 because TRANSMISSION_BIND_ADDRESS_IPV4 is set to 10.1.112.11,
Overriding download-dir because TRANSMISSION_DOWNLOAD_DIR is set to /data/completed,
Overriding incomplete-dir because TRANSMISSION_INCOMPLETE_DIR is set to /data/incomplete,
Overriding rpc-authentication-required because TRANSMISSION_RPC_AUTHENTICATION_REQUIRED is set to True,
Overriding rpc-host-whitelist because TRANSMISSION_RPC_HOST_WHITELIST is set to 127.0.0.1,192.168.3.57,
Overriding rpc-password because TRANSMISSION_RPC_PASSWORD is set to xxpass,
Overriding rpc-port because TRANSMISSION_RPC_PORT is set to 9091,
Overriding rpc-username because TRANSMISSION_RPC_USERNAME is set to xxuser,
Overriding umask because TRANSMISSION_UMASK is set to 2,
Overriding watch-dir because TRANSMISSION_WATCH_DIR is set to /data/watch,
sed'ing True to true,
Enforcing ownership on transmission config directories,
Applying permissions to transmission config directories,
Setting owner for transmission paths to 1000:140,
Setting permission for files (644) and directories (755),
Setting permission for watch directory (775) and its files (664),
,
-------------------------------------,
Transmission will run as,
-------------------------------------,
User name: abc,
User uid: 1000,
User gid: 140,
-------------------------------------,
,
STARTING TRANSMISSION,
Provider PIA has a script for automatic port forwarding. Will run it now.,
If you want to disable this, set environment variable DISABLE_PORT_UPDATER=yes,
Transmission startup script complete.,
Fri Nov 13 09:11:38 2020 Initialization Sequence Completed,
,
,
,
yes: Broken pipe,
port is 29129,
the port has been bound to 29129 Fri Nov 13 17:11:45 UTC 2020,
transmission auth required,
waiting for transmission to become responsive,
transmission became responsive,
5 100% 22.01 GB Unknown 0.0 0.0 0.0 Idle Mr.Robot.S03.1080p.AMZN.WEB-DL.DDP5.1.H.264-NTb,
Sum: 54.75 GB 0.0 0.0,
setting transmission port to 29129,
localhost:9091/transmission/rpc/ responded: "success",
Checking port...,
Port is open: Yes,
,
initial setup complete!,
,
waiting for rebind loop.................,
token expiry 1610687422,
remaining = 5399906,
update: w0d4's comment on #1465 worked for me - transmission now finding trackers & downloading.
https://github.com/haugene/docker-transmission-openvpn/issues/1465#issuecomment-724512351
@dmsalomon Very interesting that it works with a plain alpine and then installing openvpn and transmission.
I've been checking the diff on the most important parts of the setup. Namely the Dockerfile openvpn/start.sh and transmission/start.sh and I can't find anything that stands out.
Checked the versions and OpenVPN is upgraded two patch versions while Transmission is the same.
kristian@hx1c:~$ docker run --rm -it haugene/transmission-openvpn:2.14 transmission-daemon --version
transmission-daemon 3.00 (bb6b5a062e)
kristian@hx1c:~$ docker run --rm -it haugene/transmission-openvpn:3.1 transmission-daemon --version
transmission-daemon 3.00 (bb6b5a062e)
kristian@hx1c:~$ docker run --rm -it haugene/transmission-openvpn:2.14 openvpn --version
OpenVPN 2.4.7 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on May 27 2020
kristian@hx1c:~$ docker run --rm -it haugene/transmission-openvpn:3.1 openvpn --version
OpenVPN 2.4.9 x86_64-alpine-linux-musl [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [MH/PKTINFO] [AEAD] built on Apr 20 2020
Don't want to go that way just yet. So it might be something we're doing to configure Transmission the wrong way. Can you test again, then exit Transmission (so it flushes its settings to file) and then compare the settings.json with what you get if you kill Transmission in the main repo?
We are doing the Updating TRANSMISSION_BIND_ADDRESS_IPV4 to the ip of tun0 : 10.1.112.11
. Maybe it doesn't like it. But again. Why is this not working for you while it works here. Containers are supposed to be agnostic to the underlying hardware, right? Do we need to start comparing kernel versions?
kristian@hx1c:~$ uname -r
5.4.0-53-generic
@acct412 @lastb0isct Your logs don't seem to come from the latest version of the image? Or have you cropped them?
@JackDallas Can you share what DNS servers you're using and how you're setting them?
@tim2thatom I'm using ansible which maps to docker compose, and cloudflare dns (but that's preference, google 8.8.8.8 should work too)
docker-compose:
dns:
- 1.1.1.1
- 1.0.0.1
ansible:
dns_servers:
- 1.1.1.1
- 1.0.0.1
docker cli:
--dns=1.1.1.1
Thanks @JackDallas I've already got that mapped for the container. Maybe need to for docker as well.
@acct412 I see you commented out your OPENVPN_CONFIG. Can you check and see which PIA server you're currently connected to? I've copied the important parts of your compose including adding "ALL" to cap_add but still no success. I believe your success might be limited to the PIA server you're currently connected to.
@acct412 I see you commented out your OPENVPN_CONFIG. Can you check and see which PIA server you're currently connected to? I've copied the important parts of your compose including adding "ALL" to cap_add but still no success. I believe your success might be limited to the PIA server you're currently connected to.
I have absolutely no idea what I'm doing - I'll be happy to help but are you able to point me in the right direction? I don't know how to do that.
edit: running ubuntu 18.04 lts
@acct412 Are you running Portainer and know how to access the console of the container? Or know how to BASH into a container directly?
@acct412 Are you running Portainer and know how to access the console of the container? Or know how to BASH into a container directly?
Yes I'm running portainer & can access container console.
Should the GUI be saying that the port is closed?
@acct412 @lastb0isct Your logs don't seem to come from the latest version of the image? Or have you cropped them?
@haugene -- using :latest tag in my image for my docker-compose yml.
@acct412 Nice! When you can, in portainer select your transmission container, select console, then "connect", copy this code wget -qO- http://ipecho.net/plain | xargs echo
then right click in the console and select "paste as plain text". Please share the IP address it spits out. Much appreciated.
@tim2thatom 192.106.134.82
looks like Argentina? may explain the slower than normal DL speeds.
thanks for the assistance!
@tim2thatom Dunno if this will be helpful, but I ran the snippet from your comment and got 188.126.89.11
. I think I'm experiencing the exact same issue.
@acct412 @lastb0isct Your logs don't seem to come from the latest version of the image? Or have you cropped them?
@haugene -- using :latest tag in my image for my docker-compose yml.
@lastb0isct Please pull the image. image: haugene/transmission-openvpn:latest
in docker-compose yml does not mean it will use the latest version, it was the "latest" at the time you created the container.
docker-compose pull
docker-compose up -d
In a recent update, the image version is logged in the start script.
@acct412 @lastb0isct Your logs don't seem to come from the latest version of the image? Or have you cropped them?
@haugene -- using :latest tag in my image for my docker-compose yml.
@lastb0isct Please pull the image.
image: haugene/transmission-openvpn:latest
in docker-compose yml does not mean it will use the latest version, it was the "latest" at the time you created the container.
docker-compose pull
docker-compose up -d
In a recent update, the image version is logged in the start script.
Pulled latest version and seems I'm getting the same error:
Using OpenVPN provider: PIA,
Provider PIA has a custom startup script, executing it,
Downloading OpenVPN config bundle openvpn-nextgen into temporary file /tmp/tmp.NjFAHm,
Extract OpenVPN config bundle into PIA directory /etc/openvpn/pia,
Modify configs for this container,
Starting OpenVPN using config US Seattle.ovpn,
Setting OpenVPN credentials...,
adding route to local network 192.168.0.0/16 via 172.20.0.1 dev eth0,
Fri Nov 13 23:21:22 2020 OpenVPN 2.4.9 x86_64-alpine-linux-musl [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [MH/PKTINFO] [AEAD] built on Apr 20 2020,
Fri Nov 13 23:21:22 2020 library versions: OpenSSL 1.1.1g 21 Apr 2020, LZO 2.10,
Fri Nov 13 23:21:22 2020 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts,
Fri Nov 13 23:21:22 2020 CRL: loaded 1 CRLs from file [[INLINE]],
Fri Nov 13 23:21:22 2020 TCP/UDP: Preserving recently used remote address: [AF_INET]154.21.20.101:1198,
Fri Nov 13 23:21:22 2020 UDP link local: (not bound),
Fri Nov 13 23:21:22 2020 UDP link remote: [AF_INET]154.21.20.101:1198,
Fri Nov 13 23:21:22 2020 WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this,
Fri Nov 13 23:21:22 2020 [seattle415] Peer Connection Initiated with [AF_INET]154.21.20.101:1198,
Fri Nov 13 23:21:23 2020 OpenVPN ROUTE6: OpenVPN needs a gateway parameter for a --route-ipv6 option and no default was specified by either --route-ipv6-gateway or --ifconfig-ipv6 options,
Fri Nov 13 23:21:23 2020 OpenVPN ROUTE: failed to parse/resolve route for host/network: 2000::/3,
Fri Nov 13 23:21:23 2020 TUN/TAP device tun0 opened,
Fri Nov 13 23:21:23 2020 /sbin/ip link set dev tun0 up mtu 1500,
Fri Nov 13 23:21:23 2020 /sbin/ip addr add dev tun0 10.6.112.5/24 broadcast 10.6.112.255,
Fri Nov 13 23:21:23 2020 /etc/openvpn/tunnelUp.sh tun0 1500 1553 10.6.112.5 255.255.255.0 init,
Up script executed with tun0 1500 1553 10.6.112.5 255.255.255.0 init,
Executing /scripts/transmission-pre-start.sh,
/scripts/transmission-pre-start.sh returned 0,
Updating TRANSMISSION_BIND_ADDRESS_IPV4 to the ip of tun0 : 10.6.112.5,
Using Combustion UI, overriding TRANSMISSION_WEB_HOME,
Updating Transmission settings.json with values from env variables,
Using existing settings.json for Transmission /data/transmission-home/settings.json,
Overriding bind-address-ipv4 because TRANSMISSION_BIND_ADDRESS_IPV4 is set to 10.6.112.5,
Overriding download-dir because TRANSMISSION_DOWNLOAD_DIR is set to /data/completed,
Overriding incomplete-dir because TRANSMISSION_INCOMPLETE_DIR is set to /mnt/freenas/Downloads/TOR,
Overriding ratio-limit because TRANSMISSION_RATIO_LIMIT is set to 2,
Overriding ratio-limit-enabled because TRANSMISSION_RATIO_LIMIT_ENABLED is set to true,
Overriding rpc-port because TRANSMISSION_RPC_PORT is set to 9091,
Overriding script-torrent-done-enabled because TRANSMISSION_SCRIPT_TORRENT_DONE_ENABLED is set to true,
Overriding script-torrent-done-filename because TRANSMISSION_SCRIPT_TORRENT_DONE_FILENAME is set to /scripts/on-complete.sh,
Overriding speed-limit-up because TRANSMISSION_SPEED_LIMIT_UP is set to 3000,
Overriding speed-limit-up-enabled because TRANSMISSION_SPEED_LIMIT_UP_ENABLED is set to true,
Overriding watch-dir because TRANSMISSION_WATCH_DIR is set to /data/watch,
sed'ing True to true,
,
-------------------------------------,
Transmission will run as,
-------------------------------------,
User name: root,
User uid: 0,
User gid: 0,
-------------------------------------,
,
STARTING TRANSMISSION,
Provider PIA has a script for automatic port forwarding. Will run it now.,
If you want to disable this, set environment variable DISABLE_PORT_UPDATER=yes,
Transmission startup script complete.,
Fri Nov 13 23:21:23 2020 WARNING: OpenVPN was configured to add an IPv6 route over tun0. However, no IPv6 has been configured for this interface, therefore the route installation may fail or may not work as expected.,
Fri Nov 13 23:21:23 2020 Initialization Sequence Completed,
,
,
,
yes: Broken pipe,
curl: (7) Failed to connect to 10.6.112.1 port 19999: Connection refused,
Fri Nov 13 23:21:29 PST 2020: getSignature error,
,
the has been a fatal_error,
date: invalid date '',
port is ,
curl: (7) Failed to connect to 10.6.112.1 port 19999: Connection refused,
Fri Nov 13 23:21:29 PST 2020: bindPort error,
,
the has been a fatal_error,
transmission auth not required,
waiting for transmission to become responsive,
setting transmission port to ,
localhost:9091/transmission/rpc/ responded: "success",
Checking port...,
Error: portTested: http error 400: Bad Request,
,
initial setup complete!,
,
waiting for rebind loop.................,
token expiry ,
remaining = -1605338500,
Fri Nov 13 23:21:40 PST 2020: Getting PF token,
curl: (7) Failed to connect to 10.6.112.1 port 19999: Connection refused,
Fri Nov 13 23:21:40 PST 2020: getSignature error,
,
the has been a fatal_error,
date: invalid date '',
Fri Nov 13 23:21:40 PST 2020: Obtained PF token. Expires at ,
curl: (7) Failed to connect to 10.6.112.1 port 19999: Connection refused,
Fri Nov 13 23:21:41 PST 2020: bindPort error,
,
the has been a fatal_error,
Fri Nov 13 23:21:41 PST 2020: Server accepted PF bind,
Fri Nov 13 23:21:41 PST 2020: Forwarding on port ,
Fri Nov 13 23:21:41 PST 2020: Rebind interval: 1800 seconds,
Hello,
I have the exact same problem, I tried every bit of solutions people gave around this issue, nothing worked for me...
@acct412 Thank you. Tried PIA's Argentina, still can't connect. I'm out of ideas I'm afraid.
It also looks like a problem with UDP trackers to me. exec
ing a shell in the containers verifies that I can resolve DNS queries and retrieve http resources, but transmission still won't connect to any UDP trackers. I have tried changing DNS settings, adding ALL
capacity, tried every server for PIA, manually downloaded vpn profiles, and every other recommendation, so I'm at a loss for more ideas.
@acct412 did you change anything else about your compose you posted here other than cap_add: -ALL ?
@tim2thatom unfortunately no, i just compared the 2 documents.
Thanks for checking @acct412 . Would you mind posting your log now that it's working so I can compare against mine?
These are my logs from portainer - if there's a better or more comprehensive log available let me know and I can post those.
I just tried another download and it's working.
the port has been bound to 24216 Sat Nov 14 01:31:58 PST 2020,
the port has been bound to 24216 Sat Nov 14 02:01:58 PST 2020,
the port has been bound to 24216 Sat Nov 14 02:31:59 PST 2020,
the port has been bound to 24216 Sat Nov 14 03:02:00 PST 2020,
the port has been bound to 24216 Sat Nov 14 03:32:00 PST 2020,
the port has been bound to 24216 Sat Nov 14 04:02:01 PST 2020,
the port has been bound to 24216 Sat Nov 14 04:32:02 PST 2020,
the port has been bound to 24216 Sat Nov 14 05:02:03 PST 2020,
the port has been bound to 24216 Sat Nov 14 05:32:04 PST 2020,
the port has been bound to 24216 Sat Nov 14 06:02:04 PST 2020,
the port has been bound to 24216 Sat Nov 14 06:32:05 PST 2020,
the port has been bound to 24216 Sat Nov 14 07:02:06 PST 2020,
Sat Nov 14 07:27:28 2020 [greenland402] Inactivity timeout (--ping-exit), exiting,
Sat Nov 14 07:27:28 2020 /sbin/ip addr del dev tun0 10.7.112.2/24,
Sat Nov 14 07:27:28 2020 /etc/openvpn/tunnelDown.sh tun0 1500 1558 10.7.112.2 255.255.255.0 init,
Sending kill signal to transmission-daemon,
Sat Nov 14 07:27:28 2020 SIGTERM[soft,ping-exit] received, process exiting,
Starting container with revision: 93d0141d928ec661411e2c6f0e079aeff2c018dd,
Using OpenVPN provider: PIA,
Provider PIA has a custom startup script, executing it,
Downloading OpenVPN config bundle openvpn-nextgen into temporary file /tmp/tmp.NbCLmH,
Extract OpenVPN config bundle into PIA directory /etc/openvpn/pia,
Modify configs for this container,
No VPN configuration provided. Using default.,
Setting OpenVPN credentials...,
adding route to local network 192.168.3.0/24 via 172.18.0.1 dev eth0,
Sat Nov 14 07:27:42 2020 OpenVPN 2.4.9 x86_64-alpine-linux-musl [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [MH/PKTINFO] [AEAD] built on Apr 20 2020,
Sat Nov 14 07:27:42 2020 library versions: OpenSSL 1.1.1g 21 Apr 2020, LZO 2.10,
Sat Nov 14 07:27:42 2020 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts,
Sat Nov 14 07:27:42 2020 CRL: loaded 1 CRLs from file [[INLINE]],
Sat Nov 14 07:27:42 2020 TCP/UDP: Preserving recently used remote address: [AF_INET]156.146.63.151:1198,
Sat Nov 14 07:27:42 2020 UDP link local: (not bound),
Sat Nov 14 07:27:42 2020 UDP link remote: [AF_INET]156.146.63.151:1198,
Sat Nov 14 07:27:43 2020 WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this,
Sat Nov 14 07:27:43 2020 [paris402] Peer Connection Initiated with [AF_INET]156.146.63.151:1198,
Sat Nov 14 07:27:44 2020 OpenVPN ROUTE6: OpenVPN needs a gateway parameter for a --route-ipv6 option and no default was specified by either --route-ipv6-gateway or --ifconfig-ipv6 options,
Sat Nov 14 07:27:44 2020 OpenVPN ROUTE: failed to parse/resolve route for host/network: 2000::/3,
Sat Nov 14 07:27:44 2020 TUN/TAP device tun0 opened,
Sat Nov 14 07:27:44 2020 /sbin/ip link set dev tun0 up mtu 1500,
Sat Nov 14 07:27:44 2020 /sbin/ip addr add dev tun0 10.17.112.249/24 broadcast 10.17.112.255,
Sat Nov 14 07:27:44 2020 /etc/openvpn/tunnelUp.sh tun0 1500 1553 10.17.112.249 255.255.255.0 init,
Up script executed with tun0 1500 1553 10.17.112.249 255.255.255.0 init,
Updating TRANSMISSION_BIND_ADDRESS_IPV4 to the ip of tun0 : 10.17.112.249,
Updating Transmission settings.json with values from env variables,
Using existing settings.json for Transmission /data/transmission-home/settings.json,
Overriding bind-address-ipv4 because TRANSMISSION_BIND_ADDRESS_IPV4 is set to 10.17.112.249,
Overriding download-dir because TRANSMISSION_DOWNLOAD_DIR is set to /data/completed,
Overriding incomplete-dir because TRANSMISSION_INCOMPLETE_DIR is set to /data/incomplete,
Overriding rpc-authentication-required because TRANSMISSION_RPC_AUTHENTICATION_REQUIRED is set to true,
Overriding rpc-host-whitelist because TRANSMISSION_RPC_HOST_WHITELIST is set to 127.0.0.1,192.168.3.57,
Overriding rpc-password because TRANSMISSION_RPC_PASSWORD is set to [REDACTED],
Overriding rpc-port because TRANSMISSION_RPC_PORT is set to 9091,
Overriding rpc-username because TRANSMISSION_RPC_USERNAME is set to XXUSER,
Overriding umask because TRANSMISSION_UMASK is set to 2,
Overriding watch-dir because TRANSMISSION_WATCH_DIR is set to /data/watch,
sed'ing True to true,
Enforcing ownership on transmission config directories,
Applying permissions to transmission config directories,
Setting owner for transmission paths to 1000:140,
Setting permission for files (644) and directories (755),
Setting permission for watch directory (775) and its files (664),
,
-------------------------------------,
Transmission will run as,
-------------------------------------,
User name: abc,
User uid: 1000,
User gid: 140,
-------------------------------------,
,
STARTING TRANSMISSION,
Provider PIA has a script for automatic port forwarding. Will run it now.,
If you want to disable this, set environment variable DISABLE_PORT_UPDATER=yes,
Transmission startup script complete.,
Sat Nov 14 07:27:45 2020 WARNING: OpenVPN was configured to add an IPv6 route over tun0. However, no IPv6 has been configured for this interface, therefore the route installation may fail or may not work as expected.,
Sat Nov 14 07:27:45 2020 Initialization Sequence Completed,
,
,
,
yes: Broken pipe,
port is 50839,
the port has been bound to 50839 Sat Nov 14 07:27:52 PST 2020,
transmission auth required,
waiting for transmission to become responsive,
transmission became responsive,
9 100% 22.01 GB Unknown 0.0 0.0 0.0 Idle Mr.Robot.S03.1080p.AMZN.WEB-DL.DDP5.1.H.264-NTb,
Sum: 175.2 GB 0.0 0.0,
setting transmission port to 50839,
localhost:9091/transmission/rpc/ responded: "success",
Checking port...,
Port is open: Yes,
,
initial setup complete!,
,
waiting for rebind loop.................,
token expiry 1610796483,
remaining = 5428800,
the port has been bound to 50839 Sat Nov 14 07:58:04 PST 2020,
the port has been bound to 50839 Sat Nov 14 08:28:04 PST 2020,
the port has been bound to 50839 Sat Nov 14 08:58:05 PST 2020,
Thanks again @acct412 . It looks like you're connected to France. I've mirrored your setup exactly, matched the logs, and set OPENVPN_CONFIG to France and still nothing.
I am also getting this error as well. the HTTP
trackers work fine, but the UDP
trackers don't work for me.
I get something like this when a torrent is added:
transmission_1 | waiting for rebind loop.................
transmission_1 | token expiry 1610812782
transmission_1 | remaining = 5417890
but when I look on the UI, the UDP trackers aren't connected. Is it on PIA's end? I didn't have this issue before until they switched servers.. :/
@haugene At the risk of sounding extremely dumb, I have to report that everythings seems to be working again on the main haugene/transmission-openvpn image, and I don't believe I don't think it has anything to do with tweaks to my configuration. I can't make heads or tails of what was going wrong, but at least everything is resolved for me personally. I see that others are still having problems, so it doesn't seem that the issue was a temporary issue with the trackers themselves. As I said, I'm very confused.
Somehow it works for me. I find out that if I create new container from the scratch and new folder where new setting being saved, transmission works. So something goes wrong with update transmission from 2 to 3.
I do delete settings.json
and dht.dat
from transmission-home
also update my docker compose config and seems good now.
I find out that e.g. TRANSMISSION_RATIO_LIMIT=2.00
causing an error when container starts, have to update it to TRANSMISSION_RATIO_LIMIT=2
, and I goes via all settings line by line and each time delete settings.json
before to restart container, because it is now persistent and had a lot of data that was not configured in compose file.
This error is still presented https://github.com/haugene/docker-transmission-openvpn/issues/1507#issuecomment-726618928, but it also could be that site itself hides him from the VPN... Not sure here and have no update from PIA.
I can confirm that removing the old transmission-home
folder resolves the problem. I compared the two versions (the backup and new) and the only difference was the peer-port
in settings.json
. In the old settings it was 0
, in the new it was a high numbered port.
Yes ! Removing the transmission-home worked for me too !
I tried removing only settings.json
and dht.dat
from the folder first and it did not work.
Thanks @GAS85 for the solution
interestingly enough, I think deleting the transmission-home folder has also solved the issue for me as well. not all trackers are connecting, but a number of the udp ones that werent previously seem to be working now.
This is quite interesting as well. In my case I didn't recreate the container, only renamed the transmission-home to transmission-home.old just in case. The folder got recreated and everything is working good now, who knows for how long is going to be.
Can confirm that what @GAS85 and others have said worked. Interesting. Anyway, thanks! I'm on the latest version now.
Yep, same for me, replacing transmission-home fixed it -- sucks because my existing torrents won't be loaded back up when doing this. Would be nice if we could figure out what the issue stems from here.
Yep, same for me, replacing transmission-home fixed it -- sucks because my existing torrents won't be loaded back up when doing this. Would be nice if we could figure out what the issue stems from here.
Oh what you gotta do is load the old config and copy the magnets, end of story.
Yep, same for me, replacing transmission-home fixed it -- sucks because my existing torrents won't be loaded back up when doing this. Would be nice if we could figure out what the issue stems from here.
Oh what you gotta do is load the old config and copy the magnets, end of story.
Which old configs? People are saying that they had to remove everything for it to work. The resume/torrents folders?
Yep, same for me, replacing transmission-home fixed it -- sucks because my existing torrents won't be loaded back up when doing this. Would be nice if we could figure out what the issue stems from here.
Oh what you gotta do is load the old config and copy the magnets, end of story.
Which old configs? People are saying that they had to remove everything for it to work. The resume/torrents folders?
Well what I did in my case was rename the folder to transmission-home.old so I didn't lose it. Also my torrents before doing that, I copied the magnet links right from the GUI to a notepad.
When the new configs loaded then I added the torrents manually. I still have my old config just in case
@GAS85 Great catch! Thanks a lot - that looks to be it! :tada: @joshuata's comment in addition to others seems to point at some errors in the settings.json.
@lastb0isct if you still have the old transmission-home folder you could probably switch back and just delete the settings.json file first (take a backup of the settings file). A new settings.json will then be generated and knowing the difference to the old one would be super interesting.
@lastb0isct if you still have the old transmission-home folder you could probably switch back and just delete the settings.json file first (take a backup of the settings file). A new settings.json will then be generated and knowing the difference to the old one would be super interesting.
Seems that it was working well but now i'm getting some disconnects again. I tried deleting the settings.json and restarting the container again so it recreate the settings.json. But I'm getting some announce errors and most of my downloads are stuck downloading under 20kb/s... Yesterday I was downloading at 10MB/s easily.
I'm out of ideas :sweat_smile: Some of this might be provider specific also? Have you tried to use different server locations and verified it across more geographical regions?
I took a different tack. I'm running this inside a k3s cluster, not Docker. Looking through the transmission.log I can see the following. It is complaining about invalid CERTS. Opened the ubuntu torrent file in WebGUI and it seems to load ok into the torrents directory and into the Gui. I'm using TORGUARD for my vpn and trying to download the generic Ubuntu image from their website. It didn't attach to the trackers either. Maybe this log will help.
[2020-11-17 21:57:37.672] Transmission 3.00 (bb6b5a062e) started (/home/buildozer/aports/community/transmission/src/transmission-3.00/libtransmission/session.c:769) [2020-11-17 21:57:37.673] RPC Server Adding address to whitelist: 127.0.0.1 (/home/buildozer/aports/community/transmission/src/transmission-3.00/libtransmission/rpc-server.c:956) [2020-11-17 21:57:37.673] RPC Server Adding address to whitelist: ::1 (/home/buildozer/aports/community/transmission/src/transmission-3.00/libtransmission/rpc-server.c:956) [2020-11-17 21:57:37.673] RPC Server Serving RPC and Web requests on 0.0.0.0:9091/transmission/ (/home/buildozer/aports/community/transmission/src/transmission-3.00/libtransmission/rpc-server.c:1243) [2020-11-17 21:57:37.673] Port Forwarding Stopped (/home/buildozer/aports/community/transmission/src/transmission-3.00/libtransmission/port-forwarding.c:196) [2020-11-17 21:57:37.673] DHT Generating new id (/home/buildozer/aports/community/transmission/src/transmission-3.00/libtransmission/tr-dht.c:389) [2020-11-17 21:57:37.673] Using settings from "/data/transmission-home" (/home/buildozer/aports/community/transmission/src/transmission-3.00/daemon/daemon.c:646) [2020-11-17 21:57:37.673] Saved "/data/transmission-home/settings.json" (/home/buildozer/aports/community/transmission/src/transmission-3.00/libtransmission/variant.c:1221) [2020-11-17 21:57:37.673] Watching "/data/watch" for new .torrent files (/home/buildozer/aports/community/transmission/src/transmission-3.00/daemon/daemon.c:698) [2020-11-17 21:58:07.671] DHT Attempting bootstrap from dht.transmissionbt.com (/home/buildozer/aports/community/transmission/src/transmission-3.00/libtransmission/tr-dht.c:299) [2020-11-17 21:58:12.670] DHT dht.transmissionbt.com:6881: Try again (/home/buildozer/aports/community/transmission/src/transmission-3.00/libtransmission/tr-dht.c:136) [2020-11-17 21:58:46.666] Saved "/data/transmission-home/torrents/5fff0e1c8ac414860310bcc1cb76ac28e960efbe.torrent" (/home/buildozer/aports/community/transmission/src/transmission-3.00/libtransmission/variant.c:1221) [2020-11-17 21:58:46.668] ubuntu-20.10-desktop-amd64.iso Queued for verification (/home/buildozer/aports/community/transmission/src/transmission-3.00/libtransmission/verify.c:272) [2020-11-17 21:58:46.668] ubuntu-20.10-desktop-amd64.iso Verifying torrent (/home/buildozer/aports/community/transmission/src/transmission-3.00/libtransmission/verify.c:220) [2020-11-17 21:58:47.670] web will verify tracker certs using envvar CURL_CA_BUNDLE: none (/home/buildozer/aports/community/transmission/src/transmission-3.00/libtransmission/web.c:455) [2020-11-17 21:58:47.670] web NB: this only works if you built against libcurl with openssl or gnutls, NOT nss (/home/buildozer/aports/community/transmission/src/transmission-3.00/libtransmission/web.c:457) [2020-11-17 21:58:47.670] web NB: invalid certs will show up as 'Could not connect to tracker' like many other errors (/home/buildozer/aports/community/transmission/src/transmission-3.00/libtransmission/web.c:458) [2020-11-17 21:58:52.667] ubuntu-20.10-desktop-amd64.iso Could not connect to tracker (/home/buildozer/aports/community/transmission/src/transmission-3.00/libtransmission/announcer.c:1085) [2020-11-17 21:58:52.667] ubuntu-20.10-desktop-amd64.iso Retrying announce in 20 seconds. (/home/buildozer/aports/community/transmission/src/transmission-3.00/libtransmission/announcer.c:1094) [2020-11-17 21:58:52.667] ubuntu-20.10-desktop-amd64.iso Could not connect to tracker (/home/buildozer/aports/community/transmission/src/transmission-3.00/libtransmission/announcer.c:1085) [2020-11-17 21:58:52.667] ubuntu-20.10-desktop-amd64.iso Retrying announce in 20 seconds. (/home/buildozer/aports/community/transmission/src/transmission-3.00/libtransmission/announcer.c:1094) [2020-11-17 21:59:13.667] DHT dht.transmissionbt.com:6881: Try again (/home/buildozer/aports/community/transmission/src/transmission-3.00/libtransmission/tr-dht.c:136) [2020-11-17 21:59:16.666] ubuntu-20.10-desktop-amd64.iso Scrape error: Could not connect to tracker (/home/buildozer/aports/community/transmission/src/transmission-3.00/libtransmission/announcer.c:1392) [2020-11-17 21:59:16.667] ubuntu-20.10-desktop-amd64.iso Retrying scrape in 337 seconds. (/home/buildozer/aports/community/transmission/src/transmission-3.00/libtransmission/announcer.c:1401) [2020-11-17 21:59:18.667] ubuntu-20.10-desktop-amd64.iso Could not connect to tracker (/home/buildozer/aports/community/transmission/src/transmission-3.00/libtransmission/announcer.c:1085) [2020-11-17 21:59:18.668] ubuntu-20.10-desktop-amd64.iso Retrying announce in 304 seconds. (/home/buildozer/aports/community/transmission/src/transmission-3.00/libtransmission/announcer.c:1094) [2020-11-17 21:59:22.668] ubuntu-20.10-desktop-amd64.iso Could not connect to tracker (/home/buildozer/aports/community/transmission/src/transmission-3.00/libtransmission/announcer.c:1085) [2020-11-17 21:59:22.668] ubuntu-20.10-desktop-amd64.iso Retrying announce in 950 seconds. (/home/buildozer/aports/community/transmission/src/transmission-3.00/libtransmission/announcer.c:1094) [2020-11-17 21:59:47.667] DHT dht.transmissionbt.com:6881: Try again (/home/buildozer/aports/community/transmission/src/transmission-3.00/libtransmission/tr-dht.c:136) [2020-11-17 22:00:05.667] ubuntu-20.10-desktop-amd64.iso Scrape error: Could not connect to tracker (/home/buildozer/aports/community/transmission/src/transmission-3.00/libtransmission/announcer.c:1392) [2020-11-17 22:00:05.668] ubuntu-20.10-desktop-amd64.iso Retrying scrape in 921 seconds. (/home/buildozer/aports/community/transmission/src/transmission-3.00/libtransmission/announcer.c:1401)
Seems that it was working well but now i'm getting some disconnects again. I tried deleting the settings.json and restarting the container again so it recreate the settings.json. But I'm getting some announce errors and most of my downloads are stuck downloading under 20kb/s... Yesterday I was downloading at 10MB/s easily.
Check your settings.json and docker-compose.yaml. It could be that you enable speed limit, but do not overwrite it to the correct values in this case you will see very low speed as per default https://github.com/haugene/docker-transmission-openvpn/blob/master/transmission/default-settings.json
Describe the problem Since October 31st 2020 Transmission has stopped connecting to trackers. Sonarr and Radarr are both still able to connect with Transmission but fails to connect or download. My previous Docker Compose worked flawlessly for over two years. I've added
PIA_OPENVPN_CONFIG_BUNDLE=openvpn-ip-nextgen
, changed the OPENVPN_CONFIG to Israel, and changed the DNS to Google. I tested the container withwget -qO- http://ipecho.net/plain | xargs echo
and it returns the PIA Israel server ip so it appears to be connecting to PIA however the trackers will not initialize. I've looked through the other reports of issues with PIA and have tried all solutions I've come across but Transmission still refuses to connect. Any help would be greatly appreciated.Add your docker run command Current Docker Compose
Previously Working Docker Compose
Logs
Host system: