Hey all, ran into a weird issue with my Ubuntu server running qbittorrent-nox I can’t seem to figure out.
When Qbittorrent is running, I can’t load some sites. How I discovered this was Jackett was failing tests to my trackers. Sometimes all trackers would fail, other times only a couple would.
From the server I ran a curl to the tracker URLs and confirmed they were not loading.
Pcap shows the TLS hello go out, but no response from the server.
Once I kill the qbittorrent process, everything works.
Wondering if anyone has any ideas or has seen this issue before.
Things I’ve tried:
Disabled ipv6
Changed Qbit UI port
Paused Torrents
re-installed openssl
rebooted about 150 times and counting
Qbit version is 4.5.5
Ubuntu 22.04.3 headless running on Esxi
Appreciate any ideas!
Edit: So after much frustration and some other weird things, restored to a previous snapshot and the issue seems to have resolved. Appreciate all the troubleshooting ideas and responses!
From your description I would gues that the affected trackers have some rate or connection limits, and your qbittorrent announces are exceeding them.
try setting a higher announce interval, like 1+ hours
Anonamouse just announced that they’re likely to ban some client/version pairs precisely because of announce floods. Thing is, does the problem clear up instantly when the client is killed, or does it take time? The latter would indicate a server side van expiring, the former some issue on the client side.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !piracy@lemmy.dbzer0.com
⚓ Dedicated to the discussion of digital piracy, including ethical problems and legal advancements.
From your description I would gues that the affected trackers have some rate or connection limits, and your qbittorrent announces are exceeding them. try setting a higher announce interval, like 1+ hours
Anonamouse just announced that they’re likely to ban some client/version pairs precisely because of announce floods. Thing is, does the problem clear up instantly when the client is killed, or does it take time? The latter would indicate a server side van expiring, the former some issue on the client side.
The issue would resolve almost immediately after killing Qbit.