That said, it looks like it hasn’t been updated in over a year… I wonder if there’s anything else out there that does the same thing as this. (EDIT: Yes. Google brings up plenty of choices.)
I switched from that container to one that uses qbittorrent and a VPN.
qBittorrent web UI works better on a phone for my use case, and I kept having to manually restart the transmission container whenever the VPN connection dropped.
I run qBittorrent on a server (with a VPN as the only outside connection) and use an open source app to control it from my mobile devices. It can catch magnet: links and torrent files and send them to qBittorrent via its API.
I was never a huge fan of those binhex containers assuming that’s what you’re using. Updates become a chore for maintainers when containers try to do too much and they also become responsible for making sure everything works together. Also, just me, but I don’t like the idea of funneling other traffic that needs a vpn through a container that is tightly coupled to my torrent client.
I’ve always used Transmission, since there’s a Docker container I use that bakes in your VPN-of-choice & a killswitch.
https://haugene.github.io/docker-transmission-openvpn/
That said, it looks like it hasn’t been updated in over a year… I wonder if there’s anything else out there that does the same thing as this. (EDIT: Yes. Google brings up plenty of choices.)
You can set qBittorrent to only use a certain interface, and set that to the wireguard interface of your VPN.
I switched from that container to one that uses qbittorrent and a VPN.
qBittorrent web UI works better on a phone for my use case, and I kept having to manually restart the transmission container whenever the VPN connection dropped.
I run qBittorrent on a server (with a VPN as the only outside connection) and use an open source app to control it from my mobile devices. It can catch magnet: links and torrent files and send them to qBittorrent via its API.
I was never a huge fan of those binhex containers assuming that’s what you’re using. Updates become a chore for maintainers when containers try to do too much and they also become responsible for making sure everything works together. Also, just me, but I don’t like the idea of funneling other traffic that needs a vpn through a container that is tightly coupled to my torrent client.
Recommend trying a standalone transmission container and using a gluetun container’s network. https://docker-compose.de/en/gluetun/
I been using Transmission since it came out 20 years ago. I never understood why you would use anything else.
It’s FOSS and has the simplest interface with all the options.