0

Web UI - how to bypass confirmation screen?

preview

Semi recently I started getting a confirmation screen for all newly added torrents. This is a waste of time when I have my settings such that new things are automatically setup the way I like. It’s especially bad when bulk adding. Is there a way to disable it?

Semi recently I started getting a confirmation screen for all newly added torrents. This is a waste of time when I have my settings such that new things are automatically setup the way I like. It’s especially bad when bulk adding. Is there a way to disable it?

0

GitHub - dessalines/qbit-pause: A library for qBittorrent to pause popular torrents

GitHub GitHub - dessalines/qbit-pause: A library for qBittorrent to pause popular torrents github.com
preview

From the README:

Pausing popular torrents isn’t something that qBittorrent handles well. This library uses 2 criteria to pause / stop torrents.

They are stopped if they are:

  • Popular (IE have a lot of total seeds), and
  • You’ve given back more than what you’ve taken (IE a seed ratio > 1)

Requirements

  • Rust
  • A qBittorrent server.
  • An API key generated through the web UI.
  • A crontab where this script can be periodically run.

Usage

This will pause torrents with a ratio >= 2, and more than 10 total seeds.

cargo run -- \
--api-key API_KEY \
--endpoint ENDPOINT \
--ratio 2 \
--total-seeds 10

From the README:

Pausing popular torrents isn’t something that qBittorrent handles well. This library uses 2 criteria to pause / stop torrents.

They are stopped if they are:

  • Popular (IE have a lot of total seeds), and
  • You’ve given back more than what you’ve taken (IE a seed ratio > 1)

Requirements

  • Rust
  • A qBittorrent server.
  • An API key generated through the web UI.
  • A crontab where this script can be periodically run.

Usage

This will pause torrents with a ratio >= 2, and more than 10 total seeds.

cargo run -- \
--api-key API_KEY \
--endpoint ENDPOINT \
--ratio 2 \
--total-seeds 10
0

qBittorrent port over proxy?

preview

I run qBittorrent on NAS that is connecting over a VPN to a proxy server running on Raspberry Pi in another country. qBittorrent’s bottom bar indicates I am behind a firewall.

I have opened 6881 port (same as in qBittorrent) in router settings but it still registers as closed on web open port checker. Checking ss -tulpn | grep 6881 shows that there is a tailnet IP listening on this port. Also, ufw accepts both tcp and udp from 6881. But it still registers as closed.

In another post I made user stated that qBittorrent ports are not working over proxy but also suggested to ask here. Just want to confirm if it is so.

I run qBittorrent on NAS that is connecting over a VPN to a proxy server running on Raspberry Pi in another country. qBittorrent’s bottom bar indicates I am behind a firewall.

I have opened 6881 port (same as in qBittorrent) in router settings but it still registers as closed on web open port checker. Checking ss -tulpn | grep 6881 shows that there is a tailnet IP listening on this port. Also, ufw accepts both tcp and udp from 6881. But it still registers as closed.

In another post I made user stated that qBittorrent ports are not working over proxy but also suggested to ask here. Just want to confirm if it is so.

0

High disk read compared to seeding speed

preview

Hi, I’m having a problem with my qBittorrent setup that I can’t quite debug or find information on.

I’m seeding from a hard drive and I get something like 5-15 MBps of seeding capacity depending on the day. However I noticed upon inspecting a system monitor (I am running Debian 13) the total disk IO read was about 4x the seeding speed.

I’ve tweaked the advanced settings all I can to no avail. I am using the version of QBit from Devian 13 main. It’s 5.Something.

Would anyone have insight on this problem? I’ll take anything at this point. The application is using about 250MB of RAM.

Hi, I’m having a problem with my qBittorrent setup that I can’t quite debug or find information on.

I’m seeding from a hard drive and I get something like 5-15 MBps of seeding capacity depending on the day. However I noticed upon inspecting a system monitor (I am running Debian 13) the total disk IO read was about 4x the seeding speed.

I’ve tweaked the advanced settings all I can to no avail. I am using the version of QBit from Devian 13 main. It’s 5.Something.

Would anyone have insight on this problem? I’ll take anything at this point. The application is using about 250MB of RAM.

0

qBittorrent / Is there a way to automatically detect and activate demanded torrents with no active seeders?

preview

cross-posted from: lemmy.dbzer0.com/post/41847693

Aiii! I have some rare torrents with only a few active seeders, but I can only seed about 8 torrents at a time due to my very slow server. If I try to seed more, Jellyfin doesn’t work properly.

Currently, I select a few torrents to seed for a few days, and then I switch to new ones. However, I feel bad for those who need to download torrents with only a few or no seeders while I have them but not actively seeding. I could activate these “dead” torrents, but I don’t want to waste my bandwidth by not seeding most of the time.

Is there a way to automatically detect and activate demanded torrents with no active seeders? While deactivating running torrents which don’t are in need of seeding?

cross-posted from: lemmy.dbzer0.com/post/41847693

Aiii! I have some rare torrents with only a few active seeders, but I can only seed about 8 torrents at a time due to my very slow server. If I try to seed more, Jellyfin doesn’t work properly.

Currently, I select a few torrents to seed for a few days, and then I switch to new ones. However, I feel bad for those who need to download torrents with only a few or no seeders while I have them but not actively seeding. I could activate these “dead” torrents, but I don’t want to waste my bandwidth by not seeding most of the time.

Is there a way to automatically detect and activate demanded torrents with no active seeders? While deactivating running torrents which don’t are in need of seeding?

0

PSA qBittorrent-nox v5.0.0 moves removed torrent data to .Trash by default

preview

cross-posted from: lemm.ee/post/44090528

When removing a torrent with “Also remove the content files” instead of deleting the files it moves to .Trash-ID, even on headless/docker systems.

Issue github.com/qbittorrent/qBittorrent/issues/21497

cross-posted from: lemm.ee/post/44090528

When removing a torrent with “Also remove the content files” instead of deleting the files it moves to .Trash-ID, even on headless/docker systems.

Issue github.com/qbittorrent/qBittorrent/issues/21497

0

Not much going on here

preview

Just a post to say I use and like qBittorrent :) and have for years, initially on Windows but have been on Linux exclusively (currently LMDE) for 12 months, got it via Flatpack

Just a post to say I use and like qBittorrent :) and have for years, initially on Windows but have been on Linux exclusively (currently LMDE) for 12 months, got it via Flatpack