Skip to content

Seed on dupe

With seed_on_dupe enabled, upPollo reacts to a detected duplicate by downloading the existing torrent from the tracker and seeding it with your local files, instead of failing the upload. Useful when you want to contribute seeding to releases that already exist.

Configuration

seed_on_dupe: true
seed_on_dupe_match: "exact"  # or "sizeonly"

# under your active torrent client:
qbittorrent:
    hash_check: "ondupe"     # recommended with seed_on_dupe
  • seed_on_dupe_match: "exact" (default) — each media file in the torrent must exist locally with the same name and the exact same size.
  • seed_on_dupe_match: "sizeonly" — filenames are ignored; for each file size in the torrent, your directory must contain at least as many media files of that size. Useful when the existing torrent uses a different naming convention.
  • hash_check: "ondupe" — hash-check only the torrents added by seed on dupe, so your client verifies the files can actually seed without re-checking every normal upload. ("always" and "never" work as their names suggest; --check-hash forces a check either way.)

How it works

Duplicates are caught at two points:

  1. Before upload — the dupe check finds an existing torrent with a similar name and size (thresholds: name_similarity, size_similarity).
  2. During upload — the tracker rejects the upload because the info hash or name is already taken; upPollo then locates the existing torrent.

In both cases upPollo downloads the existing .torrent, verifies your local files against its file list, and — if verification passes — adds it to your client pointed at your files. No upload happens.

Dry runs and /api/upload/check

Dry runs and /api/upload/check handle a dupe the same way, without adding anything to your client: they download the existing .torrent into the temp directory and verify your files against it. If verification passes, the dupe check counts as passed, dupe_reason starts with seed_on_dupe: and names the dupe, and the check is valid. An automation that only calls /api/upload after a valid check therefore still seeds a release that someone else uploaded while it was downloading. If verification fails, the check fails with the verification error in dupe_reason.

The check compares file sizes only, also with seed_on_dupe_match: "exact". The upload links a scene release under its SRRDB file names and renames files during scene verification before it compares names; the check does neither, so the names it sees can still change. In the rare case that the sizes match but the names still differ after the upload's renaming, the check passes and the upload then fails with the verification error.

File list verification

Only media files are verified (.mkv, .mp4, .avi, .mov, .wmv, .flv, .ts, .m4v, .mpg, .mpeg, .m2ts, .vob, .webm):

  • Every media file in the torrent must exist locally with an exactly matching size (and matching name, in exact mode).
  • Extra local files are fine — subtitles, NFOs, samples, and other non-media files are ignored entirely.

If verification fails, upPollo lists the missing files and size mismatches, does not add the torrent to your client, and exits with an error. This prevents torrents sitting at 0% in your client.

Verifying torrent filelist matches local files...
✗ Torrent filelist does not match local files:
Media file comparison failed (2/3 files match):
  Missing files (1):
    - Series.Name.S01E03.1080p.WEB-DL.x264-GROUP.mkv

When to use it

Enable it when your files are the exact, unmodified release — e.g. uploading from a library that may already contain tracker releases. Leave it disabled if your files are re-encoded, renamed and resized, or otherwise differ from the original: verification would fail anyway, and silently seeding near-matches is exactly what it protects against.

Troubleshooting

  • "Media file verification failed" — you don't have the complete, unmodified release. Compare file sizes; if only the names differ, switch to seed_on_dupe_match: "sizeonly".
  • "Failed to download duplicate torrent" — check your tracker API key, your network, and whether the torrent still exists on the tracker.
  • Warnings about extra files — normal; only missing or mismatched media files fail verification.