Skip to content

NZBHydra 2 in Autopirate Docker Swarm stack

Get your FREE "elfhosted" NZBHydra instance for demo / trial 🥳

Want to see a live demo, or "kick the tyres" 🚙 before you commit to self-hosting NZBHydra?

Try out an "ElfHosted" 🧝 instance of NZBHydra for FREE!

Warning

This is not a complete recipe - it's a component of the AutoPirate "uber-recipe", but has been split into its own page to reduce complexity.

NZBHydra2 is a meta search for NZB indexers. It provides easy access to a number of raw and newznab based indexers. You can search all your indexers from one place and use it as an indexer source for tools like Sonarr, Radarr or CouchPotato.

NZBHydra Screenshot

Features include:

  • Searches Anizb, BinSearch, NZBIndex and any newznab compatible indexers. Merges all results, filters them by a number of configurable restrictions, recognizes duplicates and returns them all in one place
  • Add results to NZBGet or SABnzbd
  • Support for all relevant media IDs (IMDB, TMDB, TVDB, TVRage, TVMaze) and conversion between them
  • Query generation, meaning a query will be generated if only a media ID is provided in the search and the indexer doesn't support the ID or if no results were found
  • Compatible with Sonarr, Radarr, NZBGet, SABnzbd, nzb360, CouchPotato, Mylar, Lazy Librarian, Sick Beard, Jackett, Watcher, etc.
  • Search and download history and extensive stats. E.g. indexer response times, download shares, NZB age, etc.
  • Authentication and multi-user support
  • Automatic update of NZB download status by querying configured downloaders
  • RSS support with configurable cache times
  • Torrent support (Although I prefer Jackett for this):
  • For GUI searches, allowing you to download torrents to a blackhole folder
  • A separate Torznab compatible endpoint for API requests, allowing you to merge multiple trackers
  • Extensive configurability
  • Migration of database and settings from v1

Inclusion into AutoPirate

To include NZBHydra2 in your AutoPirate stack, include something like the following example in your autopirate.yml docker-compose stack definition file:

nzbhydra2:
  image: lscr.io/linuxserver/hydra2:latest
  env_file : /var/data/config/autopirate/nzbhydra2.env
  volumes:
   - /var/data/autopirate/nzbhydra2:/config
  networks:
  - internal
  deploy:
    labels:
      # traefik
      - traefik.enable=true
      - traefik.docker.network=traefik_public

      # traefikv1
      - traefik.frontend.rule=Host:nzbhydra.example.com
      - traefik.port=5076
      - traefik.frontend.auth.forward.address=http://traefik-forward-auth:4181
      - traefik.frontend.auth.forward.authResponseHeaders=X-Forwarded-User
      - traefik.frontend.auth.forward.trustForwardHeader=true        

      # traefikv2
      - "traefik.http.routers.nzbhydra.rule=Host(`nzbhydra.example.com`)"
      - "traefik.http.routers.nzbhydra.entrypoints=https"
      - "traefik.http.services.nzbhydra.loadbalancer.server.port=5076"
      - "traefik.http.routers.nzbhydra.middlewares=forward-auth"

Fast-track with premix! 🚀

I automatically and instantly share (with my sponsors) a private "premix" git repository, which includes necessary docker-compose and env files for all published recipes. This means that sponsors can launch any recipe with just a git pull and a docker stack deploy 👍.

🚀 Update: Premix now includes an ansible playbook, so that sponsors can deploy an entire stack + recipes, with a single ansible command! (more here)

Assemble more tools..

Continue through the list of tools below, adding whichever tools your want to use, and finishing with the end section:

Chef's notes 📓


  1. In many cases, tools will integrate with each other. I.e., Radarr needs to talk to SABnzbd and NZBHydra, Ombi needs to talk to Radarr, etc. Since each tool runs within the stack under its own name, just refer to each tool by name (i.e. "radarr"), and docker swarm will resolve the name to the appropriate container. You can identify the tool-specific port by looking at the docker-compose service definition. 

Tip your waiter (sponsor) 👏

Did you receive excellent service? Want to compliment the chef? (..and support development of current and future recipes!) Sponsor me on Github / Ko-Fi / Patreon, or see the contribute page for more (free or paid) ways to say thank you! 👏

Employ your chef (engage) 🤝

Is this too much of a geeky PITA? Do you just want results, stat? I do this for a living - I'm a full-time Kubernetes contractor, providing consulting and engineering expertise to businesses needing short-term, short-notice support in the cloud-native space, including AWS/Azure/GKE, Kubernetes, CI/CD and automation.

Learn more about working with me here.

Flirt with waiter (subscribe) 💌

Want to know now when this recipe gets updated, or when future recipes are added? Subscribe to the RSS feed, or leave your email address below, and we'll keep you updated.

Your comments? 💬