Movie Hunt Documentation

Overview

• Discover: Browse and search movies (TMDB), request a movie to send to your indexers and download client.
• Collection: View requested movies and their status (requested / available). Mark as available or remove from collection.
• Activity: Queue (current downloads), History, Blocklist, and Movie Hunt–specific logs.
• Settings: Instances, Indexers, Clients, Profiles, Root Folders, Remote Mappings, Custom Formats, Movie Management.

Running in Docker – Endpoints and Paths

Movie Hunt runs inside the same Huntarr container. There is no separate container or port for Movie Hunt. Getting endpoints and paths right in Docker is the most common source of issues.

Docker paths: /config, /downloads, /media

Inside the Huntarr container, these paths are the ones you will use in Movie Hunt. Mount them from your host so the container can read and write files.

Example for new users: In your Docker run or Compose, map host folders so the container sees them like this:

• /config → your Huntarr appdata (e.g. /path/on/host/appdata:/config)
• /downloads → the same folder your download client uses for completed downloads (e.g. /path/on/host/Downloads:/downloads)
• /media → your movie library (e.g. /path/on/host/Movies:/media)

Then in Movie Hunt Settings → Root Folders, add the path as the container sees it, e.g. /media or /media/Movies. Do not use your host path (e.g. /path/on/host/Movies)—that path does not exist inside the container.

Port and URL

• Single port: Huntarr (and Movie Hunt) listens on one port inside the container (default 9705). Your Docker run or compose must expose it, e.g. -p 9705:9705 or ports: ["9705:9705"].
• BASE_URL: If you serve Huntarr behind a reverse proxy on a subpath (e.g. https://example.com/huntarr), set the BASE_URL environment variable (e.g. BASE_URL=/huntarr). No extra endpoint is needed for Movie Hunt—it uses the same base URL.

Download clients (SABnzbd / NZBGet)

Movie Hunt talks to your download client over HTTP from inside the Huntarr container. You must use an address that the container can reach:

• Same Docker network: Use the container name (or service name in Docker Compose) as the hostname, e.g. http://sabnzbd:8080 or http://nzbget:6789. Do not use localhost—that refers to the Huntarr container itself.
• Host or other host: On Docker Desktop (Mac/Windows) you can use host.docker.internal (e.g. http://host.docker.internal:8080). On Linux you may need --add-host=host.docker.internal:host-gateway or the host’s actual IP.
• Use the exact port the client listens on (e.g. SABnzbd 8080, NZBGet 6789). No special “Movie Hunt” port—just the client’s normal API port.

Root folders

Root folders in Movie Hunt are paths as seen inside the Huntarr container (see Docker paths: /config, /downloads, /media). They are where Movie Hunt will place imported movies—typically your library path, e.g. /media or /media/Movies.

• Correct: Use the container path. If you mounted host /data/movies as /media in the container, add /media (or /media/Movies) as a root folder in Movie Hunt Settings.
• Also valid: If you use /config for appdata and keep a downloads subfolder there, you could use /config/Downloads for downloads and something like /media for your library—always the path inside the container.
• Wrong: Using the host path (e.g. /data/movies) in Movie Hunt—that path does not exist inside the container.

Remote path mappings

When the download client reports a path that is different from how Huntarr sees the same location, you need a remote path mapping (Settings → Movie Hunt → Remote Mappings). This is very common in Docker:

• Remote path: The path the download client uses (e.g. SABnzbd might report /downloads/complete/MovieName (2024)).
• Local path: The path where Huntarr (inside its container) can access that same directory (e.g. /downloads/complete if you mounted it there in the Huntarr container).
• If both Huntarr and the client run in Docker, ensure the same volume is mounted into both containers (possibly under different paths), then map “client path” → “Huntarr path”.

Environment variables

Movie Hunt does not require any extra environment variables. It uses the same Huntarr config and database. The same TZ, BASE_URL, and config volume you use for Huntarr apply to Movie Hunt.

Requirements

• USENET only (for now): Movie Hunt supports SABnzbd and NZBGet only. Torrent clients are not yet supported.
• TMDB API key (same as Requestarr; set in Huntarr Settings if needed) for discovery.
• At least one indexer (Movie Hunt → Settings → Indexers) for searching.
• At least one download client (SABnzbd or NZBGet) in Movie Hunt → Settings → Clients.
• At least one root folder and a profile for quality/custom formats.