Replies: 2 comments 6 replies
-
Hmm I'm not sure. If these are just torrents, try without port forwarding. I personally use deluge without port forwarding, getting easily 10MB/s which is more than enough for me. Maybe try with Deluge, it might be the torrent client acting strange...? |
Beta Was this translation helpful? Give feedback.
-
I'm having the exact same problem as of two days, using private internet access and Transmission as torrent client. All my other containers work flawlessly through gluetun, no ports forwarded. My compose file is nearly identical to OP's. Looking at the Transmission logs, it keeps failing at trying to scrape the torrent. Jackett and Nzbget have no problems connecting to the web. |
Beta Was this translation helpful? Give feedback.
-
Hi all,
I have a Synology running DSM 7 and have a number of docker containers set up to do media management (Donarr, Radarr, Bazarr, SABNZBD, Plex, etc) which all works swimmingly, and in order to manage torrents I wanted to run Jackett and Qbittorrent containers, connecting to VPN via a Gluetun container.
I have managed to get them all seemingly successfully set up, and I can validate that Gluetun is connected (though I've recently had some issues with some Australian servers) and that Jackett is connected through Gluetun, but torrents added to qbittorrent just keeps getting stuck at Downloading Metadata, and no matter what I've tried I just can't get it to consistently work. It seems to fail to connect to the trackers, and shows 0 seed/peers connected and MUCH smaller number of available seeds/peers than the torrent details suggested.
I'm 100% sure I'm just doing (or not doing) something that should be obvious, but I feel like I've been belting my head against a wall for ages.
The docker-compose file contains:
Beta Was this translation helpful? Give feedback.
All reactions