cross-posted from: https://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): https://pastebin.com/RtwDqiEN

ip link (VPN, qBit): same identical output (verified with Kate, EndeavourOS text file reader)

journalctl qbit: https://pastebin.com/e2XCgGKy

journalctl PVPN: https://pastebin.com/DiPBvP5W

dmesg: empty for both “torrent” and “proton”

sudo dmesg -l err: virt/tdx: TDX not supported by the host platform

FINGERS CROSSED but it seems that lowering max connections DID fix it, though I’m currently on >20/10/5/4 and it’s limiting. I’ll try upping and see where it lands on, and hopefully that’ll be it.

As per this comment

~~https://leminal.space/post/41934365/26536143~~

Proton must have changed something on their end since I used to run qBit with 500 max connections up >until the problem started

UPDATE days later: nevermind, the issue was not fixed by anything other than reducing the amount of active torrents. Seems like PVPN doesn’t like me having 400+ active torrents, even though just a few of them are actively being seeded. Transmission did not show the same behaviour because I only imported ~20 torrents to test. Guess you can’t really seed everything forever…

  • BremboTheFourth@piefed.ca
    link
    fedilink
    English
    arrow-up
    2
    ·
    3 days ago

    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

    • crow@leminal.spaceOP
      link
      fedilink
      English
      arrow-up
      1
      ·
      3 days ago

      Thanks, but it’s fine, I’ve been torrenting with qBit + Proton for a few years now, never had issues of that kind. Binding the client to the VPN interface and enabling permanent kill switch means never leaking your actual IP, barring maybe possible bugs in either one

      • BremboTheFourth@piefed.ca
        link
        fedilink
        English
        arrow-up
        2
        ·
        2 days ago

        I had the perma kill switch set within protonvpn’s app, and as long as “bind to the VPN interface” just means “select the VPN connection in qbit’s settings” I had that too. Or at least I thought I did. Iunno I guess transmission doesn’t make you fuck with that at all so