Title. I have qbittorrent and Jellyfin running behind a Caddy reverse proxy for HTTPS on Windows. I tried using NordVPN and IPVanish SOCKS5 proxy but torrents just stall and few peers pop up but disappear right away. Tried NordVPN split tunneling but it makes qbit and JF web UIs inaccessible. Is this possible?
The best way is using a virtual machine of some type.
I use Docker with binhex/arch-qbittorrentvpn.
You should team up with this user: qBittorrent + Mullvad. Can seed + download, but can’t access Web UI from other machines. What am I doing wrong?
I have a very similar setup (Caddy as a reverse proxy for Jellyfin, Sonarr, Radarr, etc on a Windows host) and I’m using Mullvad via WireGuard with split tunneling configured for Deluge.
I used this guide to adjust the config file Mullvad provides, and set Deluge to bind to the WireGuard network adapter’s IP. Since WireGuard protocol uses static internal IPs the binding will always work unless I download a new config from Mullvad’s site that uses a different IP. This shouldn’t be an issue in qBittorrent anyway, as you can bind to a network adapter directly instead of needing an IP.
I haven’t had any issues with Deluge because it uses separate processes for the web interface and the actual torrent client, but I was using the same setup with qBittorrent for a while without any issues accessing its web interface. As far as I know, if your Caddyfile reverse proxy entry for qBittorrent’s web interface is routed to a localhost:port address, it should work regardless of what adapter qBittorent is bound to.
Why on Earth would I switch to proxy over an actual VPN?
Because it would accomplish what you’re trying to do?
Maybe you meant to reply to someone else? I described my setup because it’s already working perfectly, and OP already has most of the same infrastructure set up. Switching to a proxy would be a downgrade.
You generally can’t port forward with a proxy, and there’s nothing preventing your torrent client from bypassing it if it goes down. An actual VPN is preferable because you can bind the torrent client to the VPN’s network interface so it can’t connect over your normal internet connection.
You’re right meant for the OP. But a proxy can’t “go down” like a VPN connection. When it’s set it either works or it doesn’t route at all. SOCKS5 doesn’t need a kill witch like a VPN.
Plus, SOCKS5 is faster.
A proxy can absolutely go down, and when it does you’re relying on the torrent client to not route the traffic over your normal connection. Both Deluge and qBittorrent had problems with this in the past and needed to be updated to fix it. That bug leaked my IP and rewarded me with a couple DMCA requests, so I learned my lesson and switched to a VPN.
SOCKS5 can be faster in some cases because it’s not encrypted, but it also doesn’t prevent your ISP from throttling torrent traffic unless you enable encryption in your torrent client, which limits what peers in the swarm you can connect to.