Nzbhydra2
Nzbhydra2 is a meta search application for NZB indexers, the spiritual successor to NZBmegasearcH, and an evolution of the original application NZBHydra. It provides easy access to a number of raw and newznab based indexers.
Image details
Source details
Configuration
TypeContainerlinuxlinuxserver/nzbhydra2:latest5076:5076/tcp/config : /srv/lsio/nzbhydra2/config/downloads : /srv/lsio/nzbhydra2/downloadsPUID=1000PGID=1000TZ=Etc/UTCunless-stoppedTemplate by technorabilia
Notes
Ensure to create the following volume directories on the host file system, or modify the paths in the volume mapping section under the advanced options below, as needed.
mkdir -p /srv/lsio/nzbhydra2/config
mkdir -p /srv/lsio/nzbhydra2/downloads
Installation
- Ensure both Docker and Portainer are installed, and up-to-date
- Log into your Portainer web UI
- Under Settings → App Templates, paste the below URL
- Head to Home → App Templates, and the list of apps will show up
- Select the app you wish to deploy, fill in any config options, and hit Deploy
Template Import URL
https://raw.githubusercontent.com/Lissy93/portainer-templates/main/templates.json
Show Me
docker run -d --name Nzbhydra2 \
-p 5076:5076/tcp \
-e 'PUID=1000' \
-e 'PGID=1000' \
-e 'TZ=Etc/UTC' \
-v /srv/lsio/nzbhydra2/config:/config \
-v /srv/lsio/nzbhydra2/downloads:/downloads \
--restart=unless-stopped \
linuxserver/nzbhydra2:latestSave this file as compose.yaml and run docker compose up -d
Use this only as a guide.
services:
nzbhydra2:
image: linuxserver/nzbhydra2:latest
ports:
- 5076:5076/tcp
volumes:
- /srv/lsio/nzbhydra2/config:/config
- /srv/lsio/nzbhydra2/downloads:/downloads
environment:
PUID: '1000'
PGID: '1000'
TZ: Etc/UTC
restart: unless-stopped
Save this file as nzbhydra2-stack.yml, then from a manager node, run docker stack deploy -c nzbhydra2-stack.yml nzbhydra2
version: '3.8'
services:
nzbhydra2:
image: linuxserver/nzbhydra2:latest
ports:
- 5076:5076/tcp
volumes:
- /srv/lsio/nzbhydra2/config:/config
- /srv/lsio/nzbhydra2/downloads:/downloads
environment:
PUID: '1000'
PGID: '1000'
TZ: Etc/UTC
deploy:
restart_policy:
condition: any
Save each file below into a folder, then run kubectl apply -f .
Written for k3s, but works on any cluster: bind mounts use hostPath, named volumes get a
persistent volume claim, and ports are exposed via a LoadBalancer service.
nzbhydra2-deployment.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
name: nzbhydra2
labels:
app: nzbhydra2
spec:
replicas: 1
selector:
matchLabels:
app: nzbhydra2
template:
metadata:
labels:
app: nzbhydra2
spec:
containers:
- name: nzbhydra2
image: linuxserver/nzbhydra2:latest
env:
- name: PUID
value: '1000'
- name: PGID
value: '1000'
- name: TZ
value: Etc/UTC
ports:
- containerPort: 5076
protocol: TCP
volumeMounts:
- name: nzbhydra2-data-0
mountPath: /config
- name: nzbhydra2-data-1
mountPath: /downloads
volumes:
- name: nzbhydra2-data-0
hostPath:
path: /srv/lsio/nzbhydra2/config
- name: nzbhydra2-data-1
hostPath:
path: /srv/lsio/nzbhydra2/downloads
nzbhydra2-service.yaml
apiVersion: v1
kind: Service
metadata:
name: nzbhydra2
spec:
type: LoadBalancer
selector:
app: nzbhydra2
ports:
- name: 5076-tcp
port: 5076
targetPort: 5076
protocol: TCP
Save this file as ~/.config/containers/systemd/nzbhydra2.container
[Unit]
Description=Nzbhydra2
[Container]
Image=linuxserver/nzbhydra2:latest
ContainerName=nzbhydra2
PublishPort=5076:5076/tcp
Environment=PUID=1000
Environment=PGID=1000
Environment=TZ=Etc/UTC
Volume=/srv/lsio/nzbhydra2/config:/config
Volume=/srv/lsio/nzbhydra2/downloads:/downloads
[Service]
Restart=always
[Install]
WantedBy=default.targetThen reload systemd and start the service:
systemctl --user daemon-reload
systemctl --user start nzbhydra2For a system-wide service, use /etc/containers/systemd/ and drop --user.
For more installation options, see the Documentation in our GitHub repo
For app-specific guidance, check Nzbhydra2's own repo at theotherp/nzbhydra2

The LinuxServer.io team brings you another container release featuring:
- regular and timely application updates
- easy user mappings (PGID, PUID)
- custom base image with s6 overlay
- weekly base OS updates with common layers across the entire LinuxServer.io ecosystem to minimise space usage, down time and bandwidth
- regular security updates
Find us at:
- Blog - all the things you can do with our containers including How-To guides, opinions and much more!
- Discord - realtime support / chat with the community and the team.
- Discourse - post on our community forum.
- GitHub - view the source for all of our repositories.
- Open Collective - please consider helping us by either donating or contributing to our budget
linuxserver/nzbhydra2
Nzbhydra2 is a meta search application for NZB indexers, the spiritual successor to NZBmegasearcH, and an evolution of the original application NZBHydra.
It provides easy access to a number of raw and newznab based indexers.
Supported Architectures
We utilise the docker manifest for multi-platform awareness. More information is available from docker here and our announcement here.Simply pulling
lscr.io/linuxserver/nzbhydra2:latest should retrieve the correct image for your arch, but you can also pull specific arch images via tags.The architectures supported by this image are:
| Architecture | Available | Tag | | :----: | :----: | ---- | | x86-64 | ✅ | amd64-\
Version Tags
This image provides various versions that are available via tags. Please read the descriptions carefully and exercise caution when using unstable or development tags.| Tag | Available | Description | | :----: | :----: |--- | | latest | ✅ | Stable releases | | dev | ✅ | Prereleases from their GitHub |
Application Setup
The web interface is at<your ip>:5076 , to set up indexers and connections to your nzb download applications.Usage
To help you get started creating a container from this image you can either use docker-compose or the docker cli.>!NOTE >Unless a parameter is flagged as 'optional', it is mandatory and a value must be provided.
docker-compose (recommended, click here for more info)
---
services:
nzbhydra2:
image: lscr.io/linuxserver/nzbhydra2:latest
container_name: nzbhydra2
environment:
- PUID=1000
- PGID=1000
- TZ=Etc/UTC
volumes:
- /path/to/nzbhydra2/data:/config
- /path/to/downloads:/downloads #optional
ports:
- 5076:5076
restart: unless-stoppeddocker cli (click here for more info)
docker run -d \
--name=nzbhydra2 \
-e PUID=1000 \
-e PGID=1000 \
-e TZ=Etc/UTC \
-p 5076:5076 \
-v /path/to/nzbhydra2/data:/config \
-v /path/to/downloads:/downloads `#optional` \
--restart unless-stopped \
lscr.io/linuxserver/nzbhydra2:latestParameters
Containers are configured using parameters passed at runtime (such as those above). These parameters are separated by a colon and indicate<external>:<internal> respectively. For example, -p 8080:80 would expose port 80 from inside the container to be accessible from the host's IP on port 8080 outside the container.| Parameter | Function | | :----: | --- | |
-p 5076:5076 | WebUI |
| -e PUID=1000 | for UserID - see below for explanation |
| -e PGID=1000 | for GroupID - see below for explanation |
| -e TZ=Etc/UTC | specify a timezone to use, see this list. |
| -v /config | Where nzbhydra2 should store config data. |
| -v /downloads | NZB download folder. |Environment variables from files (Docker secrets)
You can set any environment variable from a file by using a special prependFILE__.As an example:
-e FILE__MYVAR=/run/secrets/mysecretvariableWill set the environment variable
MYVAR based on the contents of the /run/secrets/mysecretvariable file.Umask for running applications
For all of our images we provide the ability to override the default umask settings for services started within the containers using the optional-e UMASK=022 setting.
Keep in mind umask is not chmod it subtracts from permissions based on it's value it does not add. Please read up here before asking for support.User / Group Identifiers
When using volumes (-v flags), permissions issues can arise between the host OS and the container, we avoid this issue by allowing you to specify the user PUID and group PGID.Ensure any volume directories on the host are owned by the same user you specify and any permissions issues will vanish like magic.
In this instance
PUID=1000 and PGID=1000, to find yours use id your_user as below:id your_userExample output:
uid=1000(your_user) gid=1000(your_user) groups=1000(your_user)Docker Mods
We publish various Docker Mods to enable additional functionality within the containers. The list of Mods available for this image (if any) as well as universal mods that can be applied to any one of our images can be accessed via the dynamic badges above.
Support Info
- Shell access whilst the container is running:
```bash
docker exec -it nzbhydra2 /bin/bash
```- To monitor the logs of the container in realtime:
```bash
docker logs -f nzbhydra2
```- Container version number:
```bash
docker inspect -f '{{ index .Config.Labels "build_version" }}' nzbhydra2
```- Image version number:
```bash
docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/nzbhydra2:latest
```Updating Info
Most of our images are static, versioned, and require an image update and container recreation to update the app inside. With some exceptions (noted in the relevant readme.md), we do not recommend or support updating apps inside the container. Please consult the Application Setup section above to see if it is recommended for the image.Below are the instructions for updating containers:
Via Docker Compose
- Update images:
* All images:
```bash
docker-compose pull
```
* Single image:
```bash
docker-compose pull nzbhydra2
```- Update containers:
* All containers:
```bash
docker-compose up -d
```
* Single container:
```bash
docker-compose up -d nzbhydra2
```- You can also remove the old dangling images:
```bash
docker image prune
```Via Docker Run
- Update the image:
```bash
docker pull lscr.io/linuxserver/nzbhydra2:latest
```- Stop the running container:
```bash
docker stop nzbhydra2
```- Delete the container:
```bash
docker rm nzbhydra2
```- Recreate a new container with the same docker run parameters as instructed above (if mapped correctly to a host folder, your
/configfolder and settings will be preserved) - You can also remove the old dangling images:
```bash
docker image prune
```Image Update Notifications - Diun (Docker Image Update Notifier)
>!TIP >We recommend Diun for update notifications. Other tools that automatically update containers unattended are not recommended or supported.Building locally
If you want to make local modifications to these images for development purposes or just to customize the logic:git clone https://github.com/linuxserver/docker-nzbhydra2.git
cd docker-nzbhydra2
docker build \
--no-cache \
--pull \
-t lscr.io/linuxserver/nzbhydra2:latest .The ARM variants can be built on x8664 hardware and vice versa using
lscr.io/linuxserver/qemu-staticdocker run --rm --privileged lscr.io/linuxserver/qemu-static --resetOnce registered you can define the dockerfile to use with
-f Dockerfile.aarch64.Versions
- 18.07.24: - Rebase to Ubuntu Noble. Remove standalone JRE (#46).
- 04.07.23: - Deprecate armhf. As announced here
- 22.01.23: - Update release URL for arch-specific packages.
- 20.01.23: - Update dependencies for v5.
- 10.12.22: - Bump master JRE to v17. Default mapIpToHost to false.
- 11.09.22: - Migrate to s6v3.
- 03.05.22: - Rebase to Jammy.
- 18.04.22: - Rebase to Alpine 3.15.
- 01.05.20: - Reorganize container, Relocate app to /app/nzbhydra2/bin, Create /app/nzbhydra2/packageinfo, Use nzbhydra2wrapperPy3.py from zip.
- 14.04.20: - Correct Name, Hydra2 -> NZBHydra2.
- 08.01.20: - Switch to python3.
- 05.01.20: - Add dev tag for prereleases.
- 23.03.19: - Switching to new Base images, shift to arm32v7 tag.
- 11.02.19: - Add pipeline logic and multi arch.
- 18.08.18: - Bump java version to 10, (bionic currently refers to it as version 11).
- 10.08.18: - Rebase to ubuntu bionic.
- 15.04.18: - Change to port 5076 in the Dockerfile.
- 11.01.18: - Initial Release.
Serve Nzbhydra2 on your own domain behind Caddy, Nginx or Traefik. Fill in your domain and copy the result. It's a starting point, some apps need their own base URL or extra headers set too.
Proxying nzbhydra2.example.com to http://Nzbhydra2:5076
Add this to your Caddyfile
nzbhydra2.example.com {
reverse_proxy http://Nzbhydra2:5076
}Check the logs first
Nine times out of ten the logs tell you exactly what went wrong.
- In Portainer, go to Containers, click the container, then Logs. Or run
docker logs Nzbhydra2 - Exit codes help too:
137means killed, usually out of memory.126or127means the command inside the image is broken.
Port already in use
If deployment fails with "Bind for 0.0.0.0:5076 failed: port is already allocated", something else on your server is using that port.
- Find what's using it:
sudo ss -tlnp | grep :5076 - Stop the other service, or pick a different host port. In
5076:5076only the left number is yours to change, the right one belongs to the app.
Running but the page won't load
The container is up but nothing appears in your browser.
- Use your server's real IP:
http://your-server-ip:5076. The 0.0.0.0 link Portainer shows isn't a real address. - Give it a minute after first deploy, Nzbhydra2 can take a while to initialise.
- Make sure your firewall allows the port, e.g.
sudo ufw allow 5076
Permission denied on volumes
If the logs show "permission denied", the app can't write to its data folder on the host.
- Fix the ownership:
sudo chown -R 1000:1000 /srv/lsio/nzbhydra2/config(and the same for the other mapped folders) - Or set the
PUIDandPGIDvariables (defaults 1000:1000) to match your own user, found withid $USER
Image won't pull
Test the pull directly on the host: docker pull linuxserver/nzbhydra2:latest
- "manifest unknown" means the tag no longer exists. This template uses
latest, so try pinning a specific version instead. - "toomanyrequests" is the Docker Hub rate limit. Log in with
docker loginto raise it. - "no space left on device" means a full disk. Reclaim space with
docker system prune
"exec format error"
This means the image was built for a different CPU architecture than your server.
- This image supports:
amd64, arm64 - Check yours with
uname -m: x86_64 is amd64, aarch64 is arm64. Raspberry Pi and other ARM boards are the usual culprits.
Container keeps restarting
The unless-stopped restart policy relaunches the app after every crash, so the real error can scroll past.
- Check the logs right after a restart, the last few lines before it died are the useful ones.
- Get the exit code with
docker inspect Nzbhydra2 --format '{{.State.ExitCode}}' - Still stuck? Redeploy once with the restart policy set to
noso the failure stays visible.
Raise an issue
Found something which isn't working as it should? Here's how to report it.
- Bug within the app: Open an issue on theotherp/nzbhydra2
- Template not working: Open an issue on technorabilia/portainer-templates
- This website not working: Open an issue on lissy93/portainer-templates