Docker-transmission-openvpn: Error: portTested: http error 0: No Response

[lorgio]

I wrote this setup using docker-compose.yml below

ruby version: '2' services: transmission: container_name: transmission image: haugene/transmission-openvpn privileged: true volumes: - ~/sonarr/transmission/data:/data - /etc/localtime:/etc/localtime:ro - /Volumes/Public:/Volumes/Public environment: OPENVPN_PROVIDER: PIA OPENVPN_CONFIG: Netherlands OPENVPN_USERNAME: user OPENVPN_PASSWORD: pass ports: - "9091:9091" sonarr: container_name: sonarr image: linuxserver/sonarr ports: - "8989:8989" restart: always environment: PUID: 1001 PGID: 1001 links: - transmission volumes: - ~/sonarr/dev/rtc:/dev/rtc:ro - ~/sonarr/config:/config - ~/sonarr/tv:/tv - ~/sonarr/Downloads:/downloads

and it seems to work upto the point where sonarr sends torrent magnets to docker-transmission-openvpn container and it shows up in the UI. Except the magnets aren't able to connect to any trackers as noted in the transmission.log

[2017-03-02 04:36:11.386] SOME_SHOW Scrape error: Could not connect to tracker (announcer.c:1279)
[2017-03-02 04:36:11.386] SOME_SHOW Retrying scrape in 3648 seconds. (announcer.c:1288)

and from the container logs show this

transmission    | Thu Mar  2 04:17:34 2017 TUN/TAP device tun0 opened
transmission    | Thu Mar  2 04:17:34 2017 do_ifconfig, tt->ipv6=0, tt->did_ifconfig_ipv6_setup=0
transmission    | Thu Mar  2 04:17:34 2017 /sbin/ip link set dev tun0 up mtu 1500
transmission    | Thu Mar  2 04:17:34 2017 /sbin/ip addr add dev tun0 local 10.36.10.6 peer 10.36.10.5
transmission    | Thu Mar  2 04:17:34 2017 /etc/transmission/start.sh tun0 1500 1558 10.36.10.6 10.36.10.5 init
transmission    | Updating TRANSMISSION_BIND_ADDRESS_IPV4 to the ip of tun0 : 10.36.10.6
transmission    | Generating transmission settings.json from env variables
transmission    | 
transmission    | -------------------------------------
transmission    | Transmission will run as
transmission    | -------------------------------------
transmission    | User name:   root
transmission    | User uid:    0
transmission    | User gid:    0
transmission    | -------------------------------------
transmission    | 
transmission    | STARTING TRANSMISSION
transmission    | CONFIGURING PORT FORWARDING
transmission    | Transmission startup script complete.
transmission    | Thu Mar  2 04:17:34 2017 Initialization Sequence Completed
transmission    | Generating new client id for PIA
transmission    | Got new port 27741 from PIA
transmission    | transmission auth not required
transmission    | localhost:9091/transmission/rpc/ responded: "success"
transmission    | Checking port...
transmission    | Error: portTested: http error 0: No Response

Any ideas what the last two lines are referring to? or what might be the issue?

[Desertbeagles]

I have the same problem here. Tried PIA servers CA Toronto, Netherlands, Sweden, and Switzerland. All gave the same error.

[haugene]

I'm assuming this is a DNS error within the container. Add the dns flags in your docker-compose.yml like in the example compose file.

The last two lines are referring to the script that opens a port in your connection to PIA and then sets that as listening port in transmission. I'm guessing that that error is related to the DNS issues.

Try setting dns for the container and let me know how it goes.

[lorgio]

it looks like it has worked!!!! thank you so much @haugene

[sschadwick]

Had the same issue, this solution works!