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

54577 readers

179 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

[email protected]

qbittorrent-nox = Firewalled / qbittorrent = Online (discuss.tchncs.de)

submitted 8 months ago by [email protected] to c/[email protected]

7 comments fedilink hide all child comments

Hello sailors,

I wanted to try out Arr* and installed and configured everything for the first few days (Native, Arch). Just tinkering around.

Radarr and Sonarr used qbittorrent at first, but the permissions gave me trouble. I installed qbittorrent-nox and run it via systemd for a different user. This fixed my permission troubles.

However, even though both run with the same settings, nox is firewalled (DHT: 0 nodes, stuck on getting the metadata) while the regular version shows online and downloads with good speeds.

I use MullvadVPN (doesn't offer Port Forwarding anymore). I opened a port in my router.

I'm pretty new to this. Does anyone have any idea what could be the problem? Do I have to add something to the systemd service?

Any hints wouldbe appreciated! Thanks for reading!

systemd service:

[Unit]
Description=qBittorrent-nox service
Documentation=man:qbittorrent-nox(1)
Wants=network-online.target
After=network-online.target nss-lookup.target

[Service]
Type=exec
User=qbittorrent-nox
group=arr
ExecStart=/usr/bin/qbittorrent-nox -webui-port=8080

[Install]
WantedBy=multi-user.target

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

[–] [email protected] 2 points 8 months ago

Are they attempting to listen on the same port, so one of them is failing to? Try setting a different port number for the two