Skip to content

Media library integration (Radarr/Sonarr)

upPollo can upload directly from your media library, even after Radarr or Sonarr have renamed the files: it queries their APIs for the original release name, rebuilds the release structure via links, and uploads that.

How it works

  1. upPollo fetches the root folder paths from all enabled Radarr/Sonarr instances and detects automatically when the given path lies inside a library.
  2. It queries Radarr (movies) or Sonarr (TV) for the original release name from the grab history.
  3. It recreates the release structure under the original names using hardlinks, symlinks, or copies (see Link modes) — single movie files, single episodes, or full season packs.
  4. The upload runs on the recreated structure.

Requirements: the files must have been grabbed through Radarr/Sonarr (history with a sceneName must exist), the APIs must be reachable from where upPollo runs, and files should follow the TRaSH naming recommendations. Files imported manually (no history) fall back to path-derived names.

Configuration

mediaserver:
    radarr_instances:
        - name: "Radarr"
          enabled: true
          url: "http://localhost:7878"
          api_key: ""        # Settings -> General -> Security
        - name: "4K Radarr"
          enabled: true
          url: "http://localhost:7879"
          api_key: ""
    sonarr_instances:
        - name: "Sonarr"
          enabled: true
          url: "http://localhost:8989"
          api_key: ""
    path_mapping:            # only if Radarr/Sonarr see different paths than upPollo
        enabled: false
        local: ""            # path as seen by upPollo, e.g. /mnt/media
        remote: ""           # path as seen by Radarr/Sonarr, e.g. /data/media

Multiple instances (e.g. separate 4K and 1080p libraries, or an anime-specific Sonarr) are queried in parallel; the first valid result wins, and the library paths of all enabled instances are combined for auto-detection.

Path mapping

When upPollo and Radarr/Sonarr run on different machines or mounts, translate the paths:

  • upPollo sees /mnt/Pool/Plex/Movies/Movie.Title.2023/movie.mkv
  • Radarr sees /media/Movies/Movie.Title.2023/movie.mkv
path_mapping:
    enabled: true
    local: "/mnt/Pool/Plex"
    remote: "/media"

The top-level link_mode option controls how upPollo places files into the client's download folder:

Mode Cross-filesystem Disk space Notes
hardlink (default) No None extra Fastest; library and download folder must share a filesystem
symlink Yes None extra Works across filesystems/ZFS datasets; on Windows, qBittorrent skips symlinks — use hardlink or copy
copy Yes Full copy Last resort when links aren't possible

A "cross-device link" error means library and download folder are on different filesystems — switch to link_mode: "symlink" (or move one of the folders).

upPollo places the release in the download folder once the upload is confirmed, while screenshots and the torrent are prepared, and uploads only when every file is in place. Each tracker's torrent then goes to the client right after its own upload, so a copy of a large release or a second tracker doesn't leave the new torrent on the tracker without a seeder. With --delay, a torrent goes to the client at the first upload after its delay has passed, or at the end of the run. The log counts how many files were hardlinked, symlinked or copied and lists each copy with its size and duration; the debug log names every file. Copies are written under a temporary name and renamed when complete, so an interrupted copy never sits under the release's file name for a later run to seed.

If the upload fails, or the CLI gets Ctrl+C or SIGTERM before a tracker has the torrent, upPollo removes the files and directories it placed; files that were already in the download folder stay. A process that is killed outright (kill -9, a power loss) cannot clean up: the files placed so far stay, and a copy in progress remains as a hidden .<file name>.partial next to them. Delete them by hand.

Source protection

Scene releases have to match SRRDB exactly: file and folder names, and the NFO. The folder becomes the torrent's root folder and takes the release name as SRRDB spells it; many scene releases keep lower-case files inside an upper-case release folder, so the file name alone does not tell the folder name. When names don't match, upPollo has to rename files or folders or replace the NFO — and doing that in your source folder would break the torrent you are seeding. So by default upPollo never touches your source. It links the release into the torrent client's download folder first and fixes up that copy, and if there is nowhere to link to it aborts the upload:

upPollo will not rename it because that would break the torrent you are seeding.
To fix: set a download_folder for your torrent client in upPollo's config …

Setting a download_folder for your torrent client is the recommended fix — hardlinks cost no extra disk space and your original stays untouched.

If you don't seed these files anywhere and would rather have upPollo fix them in place, opt out of the protection:

allow_source_modification: true

With this enabled, scene verification renames the release folder and its media files, renames or creates episode subfolders, and replaces mismatched NFOs directly in your source folder, and upPollo stops creating a staged copy purely for protection. Media library links (Radarr/Sonarr) are unaffected — those rebuild the original release naming and are still created.

Leave it off if the files are seeded in another torrent client, shared with other tools, or otherwise not yours to rewrite; the renames are not undone if the upload fails later.

Scene checks need SRRDB. If it cannot be reached, does not answer within 15 seconds, or answers with its rate-limit page, a server error or a response upPollo cannot read, the upload stops with an error: without SRRDB nothing confirms that the names and the NFO are the scene release's. upPollo asks SRRDB only once per upload after such a failure. Retry later, or set SkipSRRDB (API mode) if you vouch for the NFO. An NFO that does not match SRRDB is replaced with the scene NFO; if the scene NFO cannot be downloaded, the NFO is left out of the upload, and on your source folder the upload stops instead.

Specifying the correct path

Always point upPollo at the specific movie or season folder, never at a library root — it refuses to guess which of many folders you meant:

# wrong: library root / show root
upPollo upload /media/movies
upPollo upload "/media/tv/Show.Name.(2020)"

# right: one movie folder / one season folder
upPollo upload /media/movies/Movie.One.2023.1080p.BluRay.x264-GROUP
upPollo upload "/media/tv/Show.Name.(2020)/Season 01"

Troubleshooting

  • Library not detected — check that at least one instance is enabled: true with a valid URL and API key, that the path lies under one of the instances' root folders, and (if used) that path mapping is correct. Connection errors show up in the upPollo logs.
  • Original release name not found — the file was never grabbed through Radarr/Sonarr, or sceneName is missing in its history; upPollo falls back to path-derived names.
  • Season packs — work best when the season pack itself was grabbed; individually grabbed episodes are linked individually.