this post was submitted on 24 Feb 2024
48 points (91.4% liked)

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

54716 readers
321 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
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
48
How to install QBittorrent search plugins on a seedbox? (lemm.ee)
submitted 9 months ago by Kribensis@lemm.ee to c/piracy@lemmy.dbzer0.com
15 comments fedilink hide all child comments
 

Hi all! I have a Feral seedbox that runs QBit and can't seem to install search plugins. I've tried a few things:

  • From the unofficial search plugins page, open the raw python for 1337x and paste its URL into QBit after opening Search plugins > Install new plugin > Plugin path.
  • Download that same .py file and FTP it to my seedbox. In Plugin path, enter ~/.local/share/qBittorrent/nova3/engines/one337x.py
  • Restart Qbit, since the above is my plugins directory anyway, so maybe it will detect the new plugin. Nope.

Am I missing something stupid? The "official" instructions tell me to browse for a local file, but there's no file browser in this version of QBit (4.3.9 if it matters).

What's driving me crazy is I'm pretty sure I've successfully done this before. I know I can use Jackett (or Sonarr), but the first feels unfinished and buggy and the the second is way more than I need for my use case.

Does anyone here use Qbittorrent search plugins and see what I'm screwing up? Thanks!

you are viewing a single comment's thread
view the rest of the comments
[–] Kribensis@lemm.ee 3 points 9 months ago (1 children)

The 1337x plugin wants Python 3.6.0. My slot had 2.x, so I updated to 3.9. But, the plugin also wants Qbit 4.4.x. Feral always installs 4.3.9 with a --noupdateflag, since that's the version they've tested. I figured I was beat, but just for fun tried to install another plugin that my requirements met. That didn't work either 😂

At that point, I reinstalled Jackett and added 1337x. Which wouldn't work without installing FlareSolverr, which requires Docker, which is unsupported on Feral since it needs root. Nice!

Another commenter noted I could just use Prowlarr (and I was going to) but that also requires Docker, so this story has a sad ending. That ending is me pasting in magnet links from another tab and wishing for three hours of my life back...

[–] beeng@discuss.tchncs.de 3 points 9 months ago (1 children)
[–] Kribensis@lemm.ee 3 points 9 months ago* (last edited 9 months ago)

You're right. For Prowlarr, not sure why I thought that. It installed no problem, but thinking about it more, doesn't do anything for me since there is no difference between searching in Prowlarr and in some browser tab 😂

For flaresolverr, when I run the binary, I get this: [3288970] Error loading Python lib '/media/sdy1/myusername/flaresolverr/libpython3.11.so.1.0': dlopen: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.35' not found (required by /media/sdy1/myusername/flaresolverr/libpython3.11.so.1.0)

I don't know Linux, but an AI search indicates flaresolverr wants to update GLIBC (a GNU library) and that could break shit. That's where I chose to stop before, but I'll ask Feral. At this point, I'm committed.