NNTmux

NNTmux is a modern, self-hosted Usenet indexer in a single container.

  • Downloaders
  • Tools & Utilities
  • Web & Publishing
NNTmux is a modern, self-hosted Usenet indexer in a single container. It bundles MariaDB, Redis, Manticore, a web UI, queue workers, a scheduler and the tmux indexing engine, and automatically scans Usenet to collect headers and build a fast, searchable release index. For homelab users who want a private, Newznab-style Usenet search built from their own feeds, with API access.

Platform availability

Available on 1 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

64/100 Good

Maintained
100last commit 8 days ago
Popular
50304 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
304 GB minimum RAM

Availability: platform listings confirmed today, links checked 24 days ago

GitHub stars
304
Open issues
6
Last commit
2026-11-13
Latest release
4.2
License
GPL-3.0
Activity
declining

Checked 8 days ago - source: GitHub (NNTmux/newznab-tmux)

Resources & Compatibility

Minimum requirements: 4 GB RAM. ARM (e.g. Raspberry Pi) is not supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Copy and edit .env before starting Docker Make a copy of .env.example as .env, then fill in the database details, COMPOSER_AUTH (a GitHub token so Composer can fetch code), and turn on the Docker service hostnames section. Docker Compose (the tool that starts the app's containers) needs these values, or the build and start will fail. source
  • Run the first-run installer after start After the containers are up, run make artisan cmd='nntmux:install'. This first-time setup prepares NNTmux so it is ready to use instead of erroring. source
  • Build the web interface files Run make npm-build after installation. This creates the front-end assets the browser needs; without it, the web UI can be missing or incomplete. source

Fetched 45 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

What can I do if I cannot log in to NNTmux behind Apache or a reverse proxy?

Make sure the hostname in the Apache NNTmux configuration's ServerName matches the host you use in the browser. One user was able to log in only after adding the matching host entry to the hosts file.

What Docker setup gotcha do users report?

Users say the Docker instructions can be confusing and may lead to a missing config file error. This is a common stumbling point when creating a Usenet indexer with NNTmux.

Why might NNTmux not create the NZB folders?

NNTmux may not automatically create the resources/nzb folders. One user fixed it by creating the folders and setting the correct chmod and chown permissions.

What can I check if no releases come in after a clean install?

Do not start indexing immediately from the admin home after installation. Enable the tmux scripts, allow binary updates, and configure backfill, update releases, and postprocess settings before starting.

Answers sourced from github.com, www.reddit.com, www.reddit.com, www.reddit.com

Community

Collected 53 days ago - public community threads