Piracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ

54565 readers

590 users here now

⚓ Dedicated to the discussion of digital piracy, including ethical problems and legal advancements.

Rules • Full Version

1. Posts must be related to the discussion of digital piracy

2. Don't request invites, trade, sell, or self-promote

3. Don't request or link to specific pirated titles, including DMs

4. Don't submit low-quality posts, be entitled, or harass others

Loot, Pillage, & Plunder

📜 c/Piracy Wiki (Community Edition):

💰 Please help cover server costs.


Ko-fi	Liberapay

founded 1 year ago

MODERATORS

db0@lemmy.dbzer0.com

sunbrothersco@lemmy.dbzer0.com

dataprolet@lemmy.dbzer0.com

Flatworm7591@lemmy.dbzer0.com

RandomLegend@lemmy.dbzer0.com

Ubuntu server can't connect to some sites when qbittorrent is running (sh.itjust.works)

submitted 1 year ago* (last edited 1 year ago) by ZeroCooler@sh.itjust.works to c/piracy@lemmy.dbzer0.com

12 comments fedilink hide all child comments

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!

you are viewing a single comment's thread
view the rest of the comments

[–] reverendsteveii@lemm.ee 2 points 1 year ago* (last edited 1 year ago) (1 children)

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.

[–] ZeroCooler@sh.itjust.works 1 points 1 year ago

The issue would resolve almost immediately after killing Qbit.