Elektrine lite

← Feed

@crow@leminal.space

2026-11-13 19:49 UTC

qBitTorrent kills my VPN, Transmission does not. How to troubleshoot? cross-posted from: leminal.space/post/41927223 I’m noob at Linux (it just works), so I have no idea how to start troubleshooting this weird issue, any help appreciated! The setup: stock EndeavourOS, ProtonVPN, qBitTorrent bound to the VPN interface (and Transmission); the issue: if qBit is running, no matter the load or the server (I have access to P2P-enabled servers), it kills my VPN connection in a matter of minutes, Transmission does not. It is reproducible, launching qBit means getting disconnected, without fail; the timeline: no issues since I installed EndeavourOS (a year and a half or so), it started happening five to seven days ago, though since a few months ago I would get the same disconnection while qBitting, but only once a day and only while I was away and the system was locked, after I came back to it and reconnect, stable until shutdown. In the months between I haven’t made any changes to my system, just got a new GPU a year ago; what I tried: I initially though it was a VPN app problem, so I tried reinstalling it, both native and flatpak, after deleting all of its data of course. Transmission works but I prefer qBit so I’d love to go back to using it. Where do I start troubleshooting? I currently can’t be at my PC, so I can’t troubleshoot “live”, but I figured posting this early means more people seeing it and getting more input. Thanks in advance! ip link (VPN, no qBit): pastebin.com/RtwDqiEN ip link (VPN, qBit): same identical output (verified with Kate, EndeavourOS text file reader) journalctl qbit: pastebin.com/e2XCgGKy journalctl PVPN: pastebin.com/DiPBvP5W dmesg: empty for both “torrent” and “proton” sudo dmesg -l err: virt/tdx: TDX not supported by the host platform

Replies (9)

  • @Moonrise2473@feddit.it 2026-11-13 20:22

    Proton VPN free or paid? Proton VPN free detects torrenting and throttles connection to halt Otherwise it could be too many connections? 20 years ago my router crashed when I opened eMule, It was because I didn’t limit connections

    Open ##5530806

  • @Chronographs@lemmy.zip 2026-11-13 20:27

    I had a similar issue and reached out to proton support,though I didn’t try transmission to see if it was isolated to qbt. They said their anti-ddos protections were being triggered and the issue has mostly went away after setting qbt to start paused and limiting the maximum amount of connections.

    Open ##5530859

  • @monstoor@lemmy.dbzer0.com 2026-11-13 21:01

    My personal preference is AirVPN. They are Linux-friendly and do not throttle.

    Open ##5531237

  • @frongt@lemmy.zip 2026-11-13 21:13

    What do you mean “kills”? A see a timeout exception, which is weird, but shouldn’t crash the whole VPN client. I’m not sure how running in a flatpak would affect a VPN, so I would try it with a regular client.

    Open ##5531373

  • @ExcessShiv@lemmy.dbzer0.com 2026-11-14 07:09

    I had a similar issue with proton VPN, also paid. I run it all in docker with the *arr suit and gluetun, and it kept timing out and disconnecting. I added flaresolverr to the setup and it has worked without issues since.

    Open ##5533516

  • @hylaea@reddthat.com 2026-11-14 13:17

    happened here to. started qBitTorrent, Protonvpn dropped. No probs with Mullvad-vpn.

    Open ##5534729

  • @technocrit@lemmy.dbzer0.com 2026-11-14 15:11

    Are you using the Proton app? Have you tried importing a WireGuard config directly? I use Debian and I import my WireGuard config directly in the network settings. I’ve never had any problems apart from VPN congestion.

    Open ##5535142

  • It could be you’re not on one of the proton p2p servers which they allow torrenting on.

    Open ##5535266

  • @BremboTheFourth@piefed.ca 2026-11-16 13:12

    I don’t have any great wisdom other than to say to be extra cautious messing with this. I had issues a few years back with qbittorrent and protonvpn where I guess somehow I accidentally configured it so that qbit was showing my actual public IP even while I was connected to the VPN. Wound up getting a nice letter from my provider before I even realized anything was wrong. Switched back to transmission and haven’t had issues since lol

    Open ##5547204