How to route public torrent traffic over VPN?


Hello, today I received a takedown notice from my VPS provider, so I’m looking for an easy way to route only the torrent traffic of one of the BT clients over VPN (so I can use for example rtorrent for private torrents and deluge for the public ones).
Can you help me to achieve this? I’ve been searching for information on this site but I’m confused how to proceed


Hello @hijacked

I think there is not “easy way” to do this.
Some people did it and it seems to work but it asks a lot of work.
You can find some links to help you : (you may need to translate it in English)

Keep us updated if you find a way!

1 Like

It seems that it’s harder than I expected… I found these 2 repos with projects to implement a deluge version with VPN routing… but I’m not sure if it can be implemented to my seedbox installation. I think it would be a great idea if quickbox devs can create an script like these to help the people who want a VPN routing for our sedboxes

or you could just not use public trackers on your vps. if you want to use public trackers, you should be using a host that is ok with using public trackers.

I looked into this awhile ago. I’ve yet to implement it. The answer that was suggested to me was through firewall rules. My post was called VPN and Kill Switch and is probably still out there (on these forums). See if this works: VPN and Kill Switch / FIrewall

I also would be very interested in this answer.

I’ll look more into “private” trackers. I’m doing this so I can move to a seedbox (from local VM server(s)).

Thank you. Let me know if the link doesn’t work.

Another quick solution could be to use this docker container which runs transmission behind OpenVPN vpn client :

And connect services that QuickBox offers (Radarr, Sonarr, etc) to the dockerized Transmission (through the WebUI).

Need to be tested :slight_smile: