can't download torrents after restarting container #2327
Replies: 4 comments 7 replies
-
docker-transmission-openvpn-restarted.txt This is the full container log, with openvpn verbosity set to 11 to make sure there was communication between the container and PIA. |
Beta Was this translation helpful? Give feedback.
-
Rebuilt with the dev image. docker-transmission-openvpn_dev-freshstart.txt: docker container logs. docker-transmisison-openvpn_dev-restarted.txt: same as freshstart, but the container was stopped and started. networktests.txt: made sure the VPN connectivity was present, sure looks like it is. docker compose: self explanatory. docker-transmisison-openvpn_dev-restarted.txt |
Beta Was this translation helpful? Give feedback.
-
For anyone running into this issue, I fixed it on my machine by deleting the folders that were linked to the volumes (i.e. delete any previous configs) and then pulled in from the dev branch. Deleting the folders is what ultimately fixed it for me because I initially pulled in the dev branch and still ran into issue where it wouldn't connect to port 19999. |
Beta Was this translation helpful? Give feedback.
-
I managed to not fix, but work around, the problem. I wrote a quick bash script to just rm -f the container, remove the old volumes and image, then calls my docker compose again. Set it as a service, so that when I reboot my Ubuntu host, it just runs that script at system startup. Rebooting the host system is the only time I can, for now, forsee the container running into an issue. Works good enough for me. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
For some reason, Transmission cannot download any torrents after the container is, for any reason, stopped and started again. PIA is my provider. I will say I have no issues and torrenting works without issue upon first creating the container. The issue only comes up if I have to stop the container and start it again - for host maintenance or whatever.
Docker Compose:
Container Logs at first launch:
Transmission logs at first launch:
During this time, I had no issue. Grabbed a couple torrents, and saved them to where I wanted them - all good.
Container logs after stopping/starting: Attached, modified verbosity made it quite long.
I will note here I modified /etc/openvpn/modify-openvpn-config.sh to increase openvpn's verbosity to 11, for troubleshooting. VPN connectivity to the outside workd was fine as far as I could tell. Pings succeeded to the VPN gateway IP and traceroutes to 8.8.8.8 went through.
Transmission logs after stopping/starting
Any advise is appreciated. I did notice this when transmission started after the container was stopped:
I'd like ty try and use PIA as a custom provider with one of their ovpn files, to rule out anything specific to haugene - could use a pointer on getting that right.
Docker Compose for 'custom' PIA
This one at the moment isn't launching properly, probbly due to an error on my part.
Beta Was this translation helpful? Give feedback.
All reactions