Skip to content

qBittorrent & downloads

Stalled jobs, folders, labels, and categories for qBittorrent on TrueNAS @ 192.168.2.203. Feeds Sonarr/Radarr/Lidarr. See qBittorrent doc.

QBT-001: Torrent stalled at 0%?

Stack context: qBittorrent on NAS · categories → import paths Integrated runbooks: Media pipeline — stage 3 · qBittorrent

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Check trackers tab — working trackers?
  2. Dead torrent — 0 seeds forever.
  3. Remove and search again in Sonarr/Radarr.
  4. Disk space on pool. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: qBittorrent don't touch
QBT-002: Torrent stalled mid-download?

Stack context: qBittorrent on NAS · categories → import paths Integrated runbooks: Media pipeline — stage 3 · qBittorrent

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Pause and resume.
  2. Check seeders count — may be dead.
  3. NAS reboot interrupted — resume should continue.
  4. Firewall not issue on LAN client. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: qBittorrent don't touch
QBT-003: Wrong folder — file not where Sonarr expects?

Stack context: qBittorrent on NAS · categories → import paths Integrated runbooks: Media pipeline — stage 3 · qBittorrent

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Options → Downloads paths in qBittorrent.
  2. Must match *arr remote path mapping.
  3. Categories may override subfolder.
  4. Fix mount not Windows A: letter. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: qBittorrent don't touch
QBT-004: Category tv-sonarr not applied?

Stack context: qBittorrent on NAS · categories → import paths Integrated runbooks: Media pipeline — stage 3 · qBittorrent

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Sonarr download client settings category field.
  2. Case-sensitive exact match.
  3. Manual adds get uncategorized.
  4. Edit torrent → set category after add. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: qBittorrent don't touch
QBT-005: Category movies-radarr missing?

Stack context: qBittorrent on NAS · categories → import paths Integrated runbooks: Media pipeline — stage 3 · qBittorrent

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Same as TV — Radarr sends category.
  2. Test with manual search grab.
  3. Uncategorized breaks import filter.
  4. Reconfigure Radarr download client. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: qBittorrent don't touch
QBT-006: Category music-lidarr missing?

Stack context: qBittorrent on NAS · categories → import paths Integrated runbooks: Media pipeline — stage 3 · qBittorrent

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Lidarr download client category music-lidarr.
  2. Verify spelling.
  3. Sync test grab from Lidarr.
  4. Manual torrents need manual category. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: qBittorrent don't touch
QBT-007: Download complete but Sonarr did not import?

Stack context: qBittorrent on NAS · categories → import paths Integrated runbooks: Media pipeline — stage 3 · qBittorrent

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Activity error in Sonarr — read message.
  2. Remote path mapping.
  3. Category must match.
  4. File still in complete folder — manual import. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: qBittorrent don't touch
QBT-008: Cannot open qBittorrent Web UI?

Stack context: qBittorrent on NAS · categories → import paths Integrated runbooks: Media pipeline — stage 3 · qBittorrent

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. TrueNAS → Apps → qBittorrent running?
  2. LAN URL http://192.168.2.203:port from app config.
  3. Credentials Vaultwarden.
  4. Not on Windows PC — NAS only. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: qBittorrent don't touch
QBT-009: qBittorrent slow despite gigabit?

Stack context: qBittorrent on NAS · categories → import paths Integrated runbooks: Media pipeline — stage 3 · qBittorrent

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Seeder limited — not line speed.
  2. Many active torrents share bandwidth.
  3. Check global speed limits in settings.
  4. Disk IO on NAS during import. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: qBittorrent don't touch
QBT-010: Accidentally deleted torrent and files?

Stack context: qBittorrent on NAS · categories → import paths Integrated runbooks: Media pipeline — stage 3 · qBittorrent

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. If imported, media safe in A:/Media.
  2. If mid-download, re-search in *arr.
  3. Do not delete after import if seeding needed.
  4. ZFS snapshot recovery — technical last resort. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: qBittorrent don't touch
QBT-011: Should I delete torrent after import?

Stack context: qBittorrent on NAS · categories → import paths Integrated runbooks: Media pipeline — stage 3 · qBittorrent

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Keep seeding for Aither ratio.
  2. Hardlink means file shared with library.
  3. Remove torrent only when ratio met — see aither doc.
  4. Never delete torrent AND files if hardlinked wrong. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: qBittorrent don't touch
QBT-012: Labels vs categories?

Stack context: qBittorrent on NAS · categories → import paths Integrated runbooks: Media pipeline — stage 3 · qBittorrent

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. This stack uses categories for *arr.
  2. Labels optional for your manual sorting.
  3. Do not confuse with Sonarr categories.
  4. Manual Aither grabs — set category if automating. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: qBittorrent don't touch
QBT-013: Magnet link from Aither not adding?

Stack context: qBittorrent on NAS · categories → import paths Integrated runbooks: Media pipeline — stage 3 · qBittorrent

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Web UI → Add torrent link.
  2. Paste magnet.
  3. Set category if for Sonarr later.
  4. Check duplicate already in queue. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: qBittorrent don't touch
QBT-014: Upload ratio stuck?

Stack context: qBittorrent on NAS · categories → import paths Integrated runbooks: Media pipeline — stage 3 · qBittorrent

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Seed after complete — do not pause forever.
  2. Private tracker needs upload time.
  3. See aither-and-trackers.md ratio tips.
  4. Queue bandwidth limits affect ratio speed. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: qBittorrent don't touch
QBT-015: Web UI shows offline from Sonarr?

Stack context: qBittorrent on NAS · categories → import paths Integrated runbooks: Media pipeline — stage 3 · qBittorrent

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Host IP or docker name wrong.
  2. Test from Sonarr container network.
  3. Username password in download client settings.
  4. qBittorrent must allow alternative Web UI auth if enabled. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: qBittorrent don't touch
QBT-016: Port forwarding needed?

Stack context: qBittorrent on NAS · categories → import paths Integrated runbooks: Media pipeline — stage 3 · qBittorrent

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Home ISP — incoming not required for many swarms.
  2. Outgoing connections enough for most.
  3. Tracker may list port closed — often OK.
  4. VPN doc when configured. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: qBittorrent don't touch
QBT-017: Downloads path on wrong dataset?

Stack context: qBittorrent on NAS · categories → import paths Integrated runbooks: Media pipeline — stage 3 · qBittorrent

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. TrueNAS app volume for downloads dataset.
  2. Must share filesystem with Media for hardlinks.
  3. Fix in app config not qBittorrent GUI alone.
  4. Restart app after mount change. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: qBittorrent don't touch
QBT-018: Incomplete folder filling disk?

Stack context: qBittorrent on NAS · categories → import paths Integrated runbooks: Media pipeline — stage 3 · qBittorrent

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Clear completed imports stuck.
  2. Remove dead torrents.
  3. Check pool space TrueNAS.
  4. Pause new grabs until space freed. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: qBittorrent don't touch
QBT-019: Duplicate torrent same hash?

Stack context: qBittorrent on NAS · categories → import paths Integrated runbooks: Media pipeline — stage 3 · qBittorrent

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. qBittorrent rejects duplicate.
  2. Normal if Sonarr retried.
  3. Remove failed duplicate entry.
  4. Blocklist bad release in Sonarr. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: qBittorrent don't touch
QBT-020: Force recheck after NAS crash?

Stack context: qBittorrent on NAS · categories → import paths Integrated runbooks: Media pipeline — stage 3 · qBittorrent

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Right torrent → Force recheck.
  2. Large files take time.
  3. Do not force start during recheck.
  4. Verify 100% before expect import. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: qBittorrent don't touch
QBT-021: Queue order wrong?

Stack context: qBittorrent on NAS · categories → import paths Integrated runbooks: Media pipeline — stage 3 · qBittorrent

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Default FIFO.
  2. Super seeding off for typical use.
  3. Category filters in view only.
  4. arr manages priority via separate grabs. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive:* qBittorrent don't touch
QBT-022: Global download limit set accidentally?

Stack context: qBittorrent on NAS · categories → import paths Integrated runbooks: Media pipeline — stage 3 · qBittorrent

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Options → Speed → unlimited for LAN.
  2. Scheduler may throttle at night.
  3. Check alternative speed limits.
  4. Remove limit for max speed. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: qBittorrent don't touch
QBT-023: Torrent shows missing files?

Stack context: qBittorrent on NAS · categories → import paths Integrated runbooks: Media pipeline — stage 3 · qBittorrent

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Mount path changed after reboot.
  2. Force recheck or relocate.
  3. TrueNAS dataset not mounted.
  4. Fix volume then recheck. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: qBittorrent don't touch
QBT-024: Adding torrent manually for family request?

Stack context: qBittorrent on NAS · categories → import paths Integrated runbooks: Media pipeline — stage 3 · qBittorrent

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Prefer Overseerr — not manual qBittorrent.
  2. If admin manual grab, set correct category.
  3. Do not change default save paths.
  4. See using-qbittorrent-dont-touch guide. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: qBittorrent don't touch
QBT-025: Web UI session expired?

Stack context: qBittorrent on NAS · categories → import paths Integrated runbooks: Media pipeline — stage 3 · qBittorrent

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Re-login Vaultwarden creds.
  2. Bookmark LAN URL.
  3. Session timeout normal.
  4. Do not expose Web UI publicly without auth. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: qBittorrent don't touch
QBT-026: qBittorrent uses too much RAM?

Stack context: qBittorrent on NAS · categories → import paths Integrated runbooks: Media pipeline — stage 3 · qBittorrent

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Many active torrents increase use.
  2. Limit active downloads in settings.
  3. Normal on NAS during heavy queue.
  4. Restart app if leak suspected. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: qBittorrent don't touch
QBT-027: After TrueNAS reboot torrents paused?

Stack context: qBittorrent on NAS · categories → import paths Integrated runbooks: Media pipeline — stage 3 · qBittorrent

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Global pause on startup setting.
  2. Resume all or disable auto pause.
  3. Wait for apps to start before resume.
  4. Sonarr will re-grab if needed. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: qBittorrent don't touch
QBT-028: Connection status yellow in Web UI?

Stack context: qBittorrent on NAS · categories → import paths Integrated runbooks: Media pipeline — stage 3 · qBittorrent

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. DHT and trackers still may work.
  2. Check NAS internet.
  3. DNS issue on TrueNAS.
  4. Restart qBittorrent container. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: qBittorrent don't touch
QBT-029: Where are completed files on Windows?

Stack context: qBittorrent on NAS · categories → import paths Integrated runbooks: Media pipeline — stage 3 · qBittorrent

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Browse via Sonarr import path not qBittorrent UI.
  2. Complete folder on pool not always mapped to A:.
  3. A:/Media has library not raw downloads.
  4. Use Web UI path display for complete folder. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: qBittorrent don't touch
QBT-030: Seeding priority for ratio?

Stack context: qBittorrent on NAS · categories → import paths Integrated runbooks: Media pipeline — stage 3 · qBittorrent

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Do not throttle seeding to zero.
  2. Private tracker account health.
  3. Queue shows upload stats.
  4. Balance download vs seed bandwidth. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: qBittorrent don't touch
QBT-031: Torrent added uncategorized — fix?

Stack context: qBittorrent on NAS · categories → import paths Integrated runbooks: Media pipeline — stage 3 · qBittorrent

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Select torrent → Set category.
  2. Match tv-sonarr movies-radarr or music-lidarr.
  3. Sonarr may not auto-import uncategorized.
  4. Prevent by fixing arr client config. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive:* qBittorrent don't touch
QBT-032: qBittorrent update on TrueNAS?

Stack context: qBittorrent on NAS · categories → import paths Integrated runbooks: Media pipeline — stage 3 · qBittorrent

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Update via TrueNAS Apps.
  2. Snapshot pool first.
  3. Verify Web UI port after update.
  4. Test Sonarr download client connection. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: qBittorrent don't touch
QBT-033: Double download same release?

Stack context: qBittorrent on NAS · categories → import paths Integrated runbooks: Media pipeline — stage 3 · qBittorrent

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Sonarr/Radarr should dedupe.
  2. Remove worse duplicate torrent.
  3. Blocklist release if bad.
  4. Check why both grabbed — indexer dup. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: qBittorrent don't touch
QBT-034: Disk IO error in qBittorrent log?

Stack context: qBittorrent on NAS · categories → import paths Integrated runbooks: Media pipeline — stage 3 · qBittorrent

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Pool degraded or disk fault — urgent.
  2. Check SMART and pool status.
  3. Stop heavy IO until healthy.
  4. See storage-smart-scrub FAQ. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: qBittorrent don't touch
QBT-035: Watch folder not used?

Stack context: qBittorrent on NAS · categories → import paths Integrated runbooks: Media pipeline — stage 3 · qBittorrent

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. This stack uses API from *arr not watch folder.
  2. Do not enable watch folder unless intended.
  3. API category method is standard here.
  4. Manual magnet is fine. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: qBittorrent don't touch
QBT-036: Bind interface wrong?

Stack context: qBittorrent on NAS · categories → import paths Integrated runbooks: Media pipeline — stage 3 · qBittorrent

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Should use default NAS interface.
  2. VPN bind when added later.
  3. Wrong bind = no connectivity.
  4. Leave default until VPN doc done. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: qBittorrent don't touch
QBT-037: Share ratio limit in qBittorrent?

Stack context: qBittorrent on NAS · categories → import paths Integrated runbooks: Media pipeline — stage 3 · qBittorrent

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Do not set aggressive auto-delete.
  2. Tracker ratio rules on Aither.
  3. Manual management preferred.
  4. Seeding supports account standing. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: qBittorrent don't touch
QBT-038: Logs for import debugging?

Stack context: qBittorrent on NAS · categories → import paths Integrated runbooks: Media pipeline — stage 3 · qBittorrent

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. qBittorrent shows complete path.
  2. Sonarr Activity shows import side.
  3. Cross-check same path both sides.
  4. TrueNAS app logs for both apps. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: qBittorrent don't touch