Skip to content



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.


NZBGet performs the same function as SABnzbd (downloading content from Usenet servers), but it's lightweight and fast(er), written in C++ (as opposed to Python).

NZBGet Screenshot

Inclusion into AutoPirate

To include NZBGet in your AutoPirate stack (The only reason you wouldn't use NZBGet, would be if you were using SABnzbd instead), include the following in your autopirate.yml stack definition file:

  env_file : /var/data/config/autopirate/nzbget.env  
   - /var/data/autopirate/nzbget:/config
   - /var/data/media:/data
  - internal
      # traefik
      - traefik.enable=true

      # traefikv1
      - traefik.port=6789
      - 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.nzbget.rule=Host(``)"
      - "traefik.http.routers.nzbget.entrypoints=https"
      - ""
      - "traefik.http.routers.nzbget.middlewares=forward-auth"


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. Since we're relying on Traefik Forward Auth to protect us, we can just disable NZGet's own authentication, by changing ControlPassword to null in nzbget.conf (i.e. ControlPassword=

  2. 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 / 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 provide 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.

Notify me 🔔

Be the first to know when recipes are added / improved!

    We won't send you spam. Unsubscribe at any time. No monkey-business.

    Powered By ConvertKit

    Your comments? 💬

    Last update: November 1, 2021
    Back to top