Unofficial

QNAP NAS appsApp Center repository

Repository https://www.qnaputilities.com/repo.xml How to add it to your NAS →

Tools

QTS · QuTS hero · Windows
Free forever StorageDiag Workbench & Utilities A high-fidelity diagnostic layer for the NAS. It provides every instrument its own window, from live process tracking down to single-sector drive analysis.
  • Pulse CPU, RAM, load, VMs
  • iostat per-disk latency
  • DriveTime every bay, over time
  • SMART decoded, plus FARM
  • memhound RAM tester
  • NetScope throughput, duplex
  • Terminal shell in the panel
  • SQL Browser the QTS databases
What it does, then download →
Members only StorageDiag N Support Desk Edition. A dedicated environment for helpdesk operations. Ingest offline telemetry dumps, correlate kernel events, and troubleshoot remote hardware without an active device connection. Access restricted to support agents. Sign in to the hub → Windows NetScope Measures the link from the PC end, which is the half a NAS can never see. iperf without the command line. Download the installer → LiveCD memhound bootable USB Write it to a pendrive and boot the NAS from it. Tests 100 % of installed RAM and powers the machine off on a fault. 192 MB image → VM memhound extras The same image as an ISO and as VM disks: qcow2, VDI and VMDK, for testing the tool instead of the hardware. Browse the files →

Downloaders

How-to: replacing Download Station → QTS 6 · QuTS hero · x86_64 · arm_64
Free forever Rtorrent 16 rtorrent 0.16 with ruTorrent and a Control Center of its own. The torrent client that runs for months without being restarted, with a panel that explains what it is doing and a media library that files finished downloads where Plex, Jellyfin, Emby and Kodi expect them.
  • Control Center nine languages
  • ruTorrent patched, themed
  • Media library Movie Agent, hardlinks
  • Port check UPnP, NAT-PMP, PCP
  • Notifications WhatsApp and 20 more
  • IPv6 dual stack, Let's Encrypt
  • Performance disk and link wizard
  • Guides in the panel, offline
Try the live demo, then download →

Entertainment

Developer tools

Download clients

built from recipes

Media automation

built from recipes

Media requests and statistics

built from recipes

Live TV

built from recipes

Web and mail

How-to: website, DNS and mail → All How-to’s → built from recipes

Docs and notes

built from recipes

Network services

How-to: website, DNS and mail → All How-to’s → built from recipes

Console tools

built from recipes

■ Read this first ■

This site is an independent project. QNAP is a trademark of QNAP Systems, Inc. It is built out of pure passion and with full respect for its rightful owners.

An expression of goodwill and transparency

While I have the full legal right to use specific names in a purely descriptive manner to explain what these tools do and what platforms they support, I want to be completely transparent. My intention is solely to show goodwill and provide useful software to the community. These are entirely unofficial utilities written by a single independent developer.

The domain name

The domain includes the word qnap simply to describe the intended hardware for these tools, not the author. However, as an act of absolute goodwill: QNAP can have this domain whenever they ask. No cost, no conditions, no arguments. Simply write to silas@qnapclub.pl and the transfer will start the same day.

Trademarks and third-party rights

Within the provided programs and throughout this site, various registered trademarks may appear. All such trademarks, logos, and brand names are the sole and exclusive property of their respective owners. This includes, but is not limited to: QNAP, QTS, QuTS hero, Seagate, WD, HGST, SanDisk, Micron, Intel, Windows, Apple, Mac, Philips Hue by Signify, WinAmp, and all others. They are referenced strictly for diagnostic, compatibility, and descriptive purposes.

QNAP forum

Two places, two languages. Pick the one you want to read.

Neither forum is run from here. The Polish one is where I answer.

StorageDiag Workbench & Utilities

One QPKG, two desks. It asks once, on first sign-in, whether you came to read a diagnostic archive somebody sent you or to work the machine it is installed on — and either way the other set is one click away in the Start menu.

StorageDiag: a kernel log from a diagnostic bundle, with each error explained DriveTime SMART viewer: a disk's SMART attributes and its state MemHound memory test: bandwidth, latency and the PASS verdict CPU Lab: the benchmark kernels, one thread and all cores
Pulse: CPU, memory, load and per-process usage on a running NAS

Pulse. CPU, memory, load, processes and interfaces, live.

Inside — the Utilities desk

Inside — the Workbench desk

Installation

Recommended — from App Center. Add this site's repository once; after that this package installs and updates from App Center like any other app, and App Center picks the build for your model — so the architecture question below does not arise. App Center never offers an update to a package installed by hand; the panel still says when a new build is out.

  1. App Center → ⚙ Settings → App Repository → Add.
  2. Name it QNAP Utilities, paste https://www.qnaputilities.com/repo.xml, Add.
  3. Open QNAP Utilities in the left rail and install StorageDiag Workbench & Utilities for QNAP.

The repository panel: every package in the feed →

By hand instead: take the build for your architecture below, then App Center → Install Manually.

Download

Unsure which? Run uname -m on the NAS.

QNAP is a trademark of QNAP Systems, Inc.

MemHound

A RAM tester for a NAS you cannot take offline. It takes free memory in blocks, pins them with mlock, walks moving-inversion and checkerboard patterns over them, and maps every proven cell back to a physical address. One static binary, nothing installed.

How a test runs, what each result means and two recorded runs: the MemHound page.

memhound running over SSH: memory map, progress bar, kernel-log watch and fault counters

v0.6.8, the default run, on a live NAS.

Run it

# on the NAS, over SSH
arch=$(uname -m)
# uname says armv7l; the binary is named armhf
[ "$arch" = armv7l ] && arch=armhf
wget https://qnaputilities.com/pub/memhound/bin/memhound.tar.gz
tar zxvf memhound.tar.gz
chmod +x memhound*
./memhound-$arch

With no options it runs the whole RAM test: it frees the caches (and the ZFS ARC on QuTS hero), runs a Quick pass, then Extended passes until you press q, and ends with the verdict and Tested X MB of Y MB (Z%). Every pass keeps 256 MB free, so it is safe on a box that is serving files. --quick runs one fast sweep, and --full covers nearly all of the RAM when the machine is idle.

--bench --ui2 measures memory bandwidth and latency instead, with no fault test.

Download

No SSH? Boot it.

The bootable image covers 100 % of installed RAM, including everything QTS would be holding. Write it to a pendrive, boot the NAS from it, walk away. A fault powers the machine off. On a monitor you get the plain console, not the coloured map; the pendrive clicks once a minute while the run is healthy and writes the report, the failure map and the verdict back onto itself.

A PC, or a QNAP with HDMI: the LiveCD

The LiveCD runs the same test as ./memhound-$arch above, outside QTS or any other system, so it reaches nearly all of the RAM. Write the ISO to a stick with balenaEtcher, Rufus or dd (or burn a CD), start the machine from it with a monitor and a USB keyboard, and press 1. With no key pressed, the test starts by itself after 15 seconds, and a clean result restarts the machine 60 seconds later. The report goes to the stick's MHDATA partition, folder memhound. If the test finds bad memory, the machine shows the result and halts on purpose; hold the power button to switch it off. x86_64 only; switch Secure Boot off first if it is on.

QNAP is a trademark of QNAP Systems, Inc.

CPUhound

A per-core CPU assessment for a NAS. It reads the machine and its instruction set, runs single-thread, multi-thread, scaling and interference subtests on every core, and ends with a trust verdict: how far the numbers it measured can be believed on a box that is busy with other work. One static binary, nothing installed.

How a run works, what each verdict means, the subtests measured and two recorded runs: the CPUhound page.

CPUhound with --ui2 over SSH: the machine and its instruction sets, the CPH index, thirteen subtests with single-thread and all-core results and scaling, and the trust verdict

CPUhound 0.1.1, a full run with --ui2 on a test NAS that was busy and hot: the verdict says UNTRUSTED and why.

Run it

# on the NAS, over SSH
a=$(uname -m)
# uname says armv7l; the binary is named armhf (older ARM: armel)
[ "$a" = armv7l ] && a=armhf
wget https://qnaputilities.com/pub/cpuhound/bin/cpuhound-cli-$a
chmod +x cpuhound-cli-$a
./cpuhound-cli-$a --ui2

--ui2 draws the dashboard in 256 colours (t switches the colours while it runs); --ui is the same in 16 colours for a terminal without 256. q stops a run, and it still reports.

Started with no mode on a terminal, it asks first and then runs --full, the real benchmark. --probe is the 3-second reading instead: everything ends three seconds after launch, and its verdict is marked indicative. --quiesce none keeps the workers at normal priority so the NAS stays responsive; --cpus 0-3 limits the run to some cores; --json prints one event per line for scripts.

Download

CPUhound 0.1.1. QNAP is a trademark of QNAP Systems, Inc.

DriveTime CLI

The disk surface test of StorageDiag Workbench, on a terminal. It lists the NAS's disks, starts a quick or full surface test on the one you pick and shows its progress. It reads the disk and never writes to it. A test keeps running when you leave the screen, so you can come back to it later. One static binary, nothing installed.

How the test tells a failing disk from its slot, what each verdict means and a recorded test: the DriveTime page.

DriveTime CLI over SSH: the surface map of a 1.9 TB NVMe drive, the run, its pace, the error counters during the test and the verdict DISK GOOD

A finished daily surface test, opened with probe-ui.

Run it

# on the NAS, over SSH, as admin
a=$(uname -m)
# uname says armv7l; the binary is named armhf (older ARM: armel)
case "$a" in armv7*) a=armhf ;; armv5*|armv6*) a=armel ;; esac
wget https://qnaputilities.com/pub/drivetime/bin/drivetimed-cli-$a
chmod +x drivetimed-cli-$a
./drivetimed-cli-$a probe-ui

probe-ui lets you pick a disk and watch or start its test. Straight to one disk: probe --serial <serial> --mode quick. q leaves the screen and the test goes on; status shows where it is. The screen is 256 colours on a terminal that has them; --ui gives 16 colours and --plain plain progress lines.

The test paces itself: by default it slows down at the drive's own temperature limit (--temp-limit), and --max-rate caps its speed in MiB/s.

Download

QNAP is a trademark of QNAP Systems, Inc.

App Center repository

Every package on this site, inside App Center. Add the address once; installs and updates then come from App Center like any other app. It serves the same files as the Download buttons here.

https://www.qnaputilities.com/repo.xml

Add it

  1. App Center → ⚙ Settings → App Repository → Add.
  2. Name it QNAP Utilities, paste the address, Add. It appears in the left rail under that name.

In the repository

Reading the list…

The feed is rebuilt after every release. QNAP is a trademark of QNAP Systems, Inc.

QZilla

A web-based, dual pane file commander and multi-protocol transfer studio for the NAS. WinSCP in a browser tab: two panes, a transfer queue, and FTP, SFTP, SCP, rsync, WebDAV, SMB/CIFS, NFS, S3 and the cloud providers reachable from the same window. One self-contained Go binary, no runtime to install.

QZilla: local site on the left, Site Manager open over it with saved sites and protocols

Local site left, Site Manager over it. QZilla 2.0.452 on QuTS hero.

True “QNAP Commander app” <3 Absolute must-have! Silas Mariusz

Written by Qoolbox. Published on the community repo, not by QNAP.

Not my software and not hosted here. The link leaves for myqnap.org.

qfwpack

Opens a QNAP firmware image: decrypt the PC1 payload, read the footer, list or extract every member, rebuild an image with regenerated checksums, or prove a byte-identical round trip with selftest. Runs on Windows and on the NAS.

qfwpack command reference: every command, its arguments and what it does

The built-in command reference.

A whole directory at once

qfwpack.exe batch unpacked . --no-big

==> [2] TS-X32U_20260819-6.1.0.3591.img
unpacked ./TS-X32U_20260819-6.1.0.3591.img
  model=TS-X32U version=6.1.0 date=20260819 build=3591
  PARTIAL extract: kept 42 of 46 members (not repack-capable)
  fw/       : 42 files

--no-big drops the large members, which is what you want when reading a firmware instead of rebuilding one. The extract is then marked PARTIAL and refuses to repack.

Download

Repacked firmware can brick a NAS. A reverse-engineering tool for people who already know that.

TuneThatHue

This drives Philips Hue lights, and nothing else. You need a Hue bridge with an Entertainment area set up in the Hue app, and bulbs in it. Play music anywhere in the house; the NAS listens, finds the beat, and runs the room like a small lighting desk — strobe on the drop, lights joining one at a time through a build-up, colour moving with the track.

The TuneThatHue panel: effects, latency calibration and the senders The light wall: each lamp's colour as sent to the bridge, and the signal chain from audio to bridge Settings: base effects and the colour palettes

What it does

How the music gets in

Five ways, and you can leave them all on: one drives the lights at a time, and another takes over a couple of seconds after it goes quiet.

Where it runs

QuTS hero 6.0 or QTS 6.0 on an x86_64 NAS (the package carries its own Python for that architecture), and off the NAS as well: Windows 10/11 as a service, macOS 12+ as a launchd agent, Linux and Raspberry Pi OS as a systemd user unit, or a container. On a NAS the panel is on http://<nas>:58091/.

Installation

Recommended — from App Center. Add this site's repository once; after that this package installs and updates from App Center like any other app. App Center never offers an update to a package installed by hand; the panel still says when a new build is out.

  1. App Center → ⚙ Settings → App Repository → Add.
  2. Name it QNAP Utilities, paste https://www.qnaputilities.com/repo.xml, Add.
  3. Open QNAP Utilities in the left rail and install TuneThatHue.

The repository panel: every package in the feed →

By hand instead: take the QPKG from the links below, then App Center → Install Manually.

Download

The effects engine is the one from Music Assistant's Hue provider, copied in byte for byte, so an effect tuned here behaves the same there and the other way round.

Uses the Philips Hue Entertainment API. Not affiliated with, endorsed by or sponsored by Signify / Philips Hue, Winamp, foobar2000 or AIMP.

Linkwarden

A place to keep links that is not a browser profile, not a cloud account and not somebody else's business model. Collections, sub-collections, tags, search, public sharing, RSS subscriptions, import from every browser, an API and a browser extension.

Linkwarden dashboard with saved links as cards, beside the phone app Linkwarden dashboard: collections, tags and recent links

Screenshot: Linkwarden

Linkwarden running on a QNAP: dashboard with collections, tags and pinned links

Linkwarden 2.16 on QTS 6.1, a minute after installing it.

What is actually in the package

Upstream ships Docker and nothing else. This is the native equivalent: PostgreSQL 17 compiled for the NAS and running as its own service account, the official Node build, the application and its worker, and nginx in front. It installs from App Center like anything else, keeps its database and its files across upgrades, and applies its own migrations on every start.

What it does not do, and why

Linkwarden can archive a page as a screenshot, a PDF and single-file HTML. That needs Chromium, and Chromium on QTS needs about twenty shared libraries the firmware does not have — NSS, NSPR, gbm, udev, xkbcommon, ATK and half the X client stack. So archival is off. Everything else works: bookmarks, titles, favicons, collections, tags, sharing, search, import and export. If you want previews, point the package at a browser running elsewhere.

Did you know

PostgreSQL refuses to run as root — and on a QNAP the administrator account is root. QTS also has no su, no runuser and no setpriv. So the package carries a twenty-line program of its own whose entire job is to become somebody else before starting the database.

The first login

The install makes the administrator account itself — user linkwarden, a generated password — instead of leaving the first person who finds port 6030 to claim it. The password arrives as a warning in Control Panel → System Logs, as a notice on the desktop, and in /usr/bin/linkwarden/var/log/first-run.txt. Change it in Linkwarden, Settings → Password; public sign-up is closed, and the administrator adds everyone else. Locked out? Over SSH: /etc/init.d/linkwarden.sh passwd, which works with the app stopped too. The package carries its own guide in English and Polish: /etc/init.d/linkwarden.sh guide.

Installation

Recommended — from App Center. Add this site's repository once; after that this package installs and updates from App Center like any other app. App Center never offers an update to a package installed by hand; the panel still says when a new build is out.

  1. App Center → ⚙ Settings → App Repository → Add.
  2. Name it QNAP Utilities, paste https://www.qnaputilities.com/repo.xml, Add.
  3. Open QNAP Utilities in the left rail and install Linkwarden.

The repository panel: every package in the feed →

By hand instead: take the build for your architecture below, then App Center → Install Manually.

Download

Linkwarden is by the Linkwarden team, AGPL-3.0. Packaged here, not written here. Opens on port 6030; the install creates the administrator account and announces its password in the QNAP System Logs and on the desktop notice board. Needs about 700 MB of memory once everything is warm, so it wants a NAS with 2 GB or more.

LinkDrop Server

LinkDrop shares files from Rtorrent 16 by link, straight from one NAS to another NAS or to a browser. LinkDrop Server is the service in the middle, the program linkdropd. It registers each NAS that shares, by that NAS’s own key, keeps the share links and says whether the sharing NAS is online. When someone opens a link, it puts the receiving NAS or browser in touch with the sharing NAS, directly or through NAT traversal. It also answers STUN on UDP 3478 and serves the link host’s home page.

Who needs it

Whoever runs a LinkDrop service. Rtorrent 16’s LinkDrop uses link.qnaputilities.com, so you do not need this package to share or receive files with Rtorrent 16.

What it does not do

It never carries a file. The data goes from the sharing NAS to the receiving NAS or browser, and LinkDrop Server only brings the two together. It has no admin panel either: you set it up in WebPortico and in a settings file.

How it runs

linkdropd runs as its own unprivileged account, linkdrop, and serves HTTP on 127.0.0.1:8778 only. WebPortico on the same NAS holds the public names: one proxy site per name to http://127.0.0.1:8778, with WebSocket on and a Let’s Encrypt certificate. STUN answers on UDP 3478 on every address of the NAS, so that port has to reach the NAS from the internet.

The data folder, <volume>/LinkDropServer, sits beside the package on the same volume, so removing the package keeps every registered NAS and every link. The settings are LINKDROP_ lines in LinkDropServer/etc/server.env, read at every start. Over SSH, /etc/init.d/linkdropserver.sh takes start, stop, restart, status and log; export and import move a server’s state, settings and home page to another NAS in one tar file.

Installation

Recommended — from App Center. Add this site’s repository once; after that the package installs and updates from App Center like any other app.

  1. App Center → ⚙ Settings → App Repository → Add.
  2. Name it QNAP Utilities, paste https://www.qnaputilities.com/repo.xml, Add.
  3. Open QNAP Utilities in the left rail and install LinkDrop Server.

The repository panel: every package in the feed →

By hand instead: take the build for your architecture below, then App Center → Install Manually.

Download

Freeware by Silas, Mariusz Grzybacz. Package name LinkDropServer; the SHA-256 sums of both files are in SHA256SUMS. It runs behind WebPortico on the same NAS.

Rtorrent 16

Try it before you download it. The demo is the real panel with a fake NAS behind it — every page, every language, nothing to install. Open the live demo →

Media library: how finished downloads flow from the base folder into the library folders Quick access: speeds, the search box and the torrent list with progress, labels and ratio Seeding & Retention: when seeding ends for public and private torrents, and what happens then

Everything it does, page by page, with pictures: the Rtorrent 16 page →

Rtorrent 16 Control Center: speeds, torrent counts, disk, and a reachability card explaining why the port is closed

The Control Center on QTS 6.1. Public addresses in these screenshots are replaced with the documentation range.

rtorrent is the BitTorrent client that people leave running for months. It has no graphical interface of its own and never had one — it is a terminal program with a command interface, which is exactly why it survives on a NAS where a browser-based client would not. This package builds rtorrent 0.16 and its libtorrent from source for QTS, puts ruTorrent in front of it for day-to-day work, and adds a Control Center for everything ruTorrent was never meant to do: ports, NAT, certificates, the media library, notifications, performance and the guides.

What you get that a plain rtorrent build does not

Network and NAT page: the route out, the router's external address, and the hops beyond it

Network & NAT: what is between this NAS and the internet, hop by hop.

A little history

Both rtorrent and its libtorrent are by Jari Sundell, "rakshasa". The library came first, in 2004, and rtorrent began life inside it as the demo client that proved it worked; it moved into a repository of its own in January 2005, and the terminal interface arrived two commits later. Remote control came in 2007, which is when web interfaces became possible at all. Note that this libtorrent is not the one Deluge and qBittorrent use — two different libraries have carried that name for twenty years.

After a five-year silence the project restarted in 2024, and the 0.16 line has had twenty-three releases in twelve months, with rtorrent and libtorrent now versioned together. This package tracks it.

Did you know

Its sister project kept a NEWS file for twenty-one years whose entire contents were one line: "If you want news, watch CNN or something." It was finally deleted in 2025.

And the interface

ruTorrent is a separate program — PHP and JavaScript by Novik, first published in 2009 — that talks to rtorrent over a socket. It ships fifty plugins, and one of them draws a spectrogram of a downloaded audio file with SoX. That is the trick music trackers use to catch an MP3 re-encoded and passed off as lossless: the fake shows a hard cutoff where the high frequencies were thrown away. This package builds SoX for the NAS so the plugin works.

What leaves the NAS

Once a day the package asks this site for the latest build and sends, encrypted with a key only this site can open, the NAS model, processor, firmware, install date, the package and add-on versions, the architecture and an installation id (a SHA-256 hash of the NAS serial number, or of a random id when there is none), so the author can count installations. Nothing about your torrents, files or names goes with it. The panel tells you this once, and the switch update_check in Settings turns the check and the report off together.

Installation

Recommended — from App Center. Add this site's repository once; after that this package installs and updates from App Center like any other app. App Center never offers an update to a package installed by hand; the panel still says when a new build is out.

  1. App Center → ⚙ Settings → App Repository → Add.
  2. Name it QNAP Utilities, paste https://www.qnaputilities.com/repo.xml, Add.
  3. Open QNAP Utilities in the left rail and install Rtorrent 16.

The repository panel: every package in the feed →

By hand instead: take the build for your architecture below, then App Center → Install Manually.

Download

16.22-04W is the current build. 02H before it: with the Search add-on below the panel gains a Search page over hundreds of trackers, it takes magnets and big drops of .torrent files in its stride, the Quick access list is folded and paged, and once a day it looks for a new build and says so in the panel. Changing the web ports is now safe: as you type a number the NAS says whether it is free and names whatever holds it, and a port that is taken, below 1024, or already the QTS web interface is refused before it can stop the panel from coming back. What App Center opens follows the setting through every upgrade. Quick access shows how long each download has left, as a clock beside the row.

01Y before it made adding a torrent from a phone take nothing but the camera: the QR code the panel prints beside each category opens a small page on the phone where you pick a .torrent or paste a magnet link, and it goes into that category. Nothing to install, and no password — the link itself is the key. The WhatsApp add-on takes a .torrent forwarded straight to it, sends links you can tap, and prints a search result you can actually read on a phone.

01X before it added Seeding & Retention: a finished torrent ends when it reaches the ratio, the uploaded amount or the age you set, and you choose what happens then, down to erasing it with its data into a trash you can point anywhere and restore from. Storage protection is the other half: when the download volume runs low it deletes old finished torrents, worst ratio first, until there is room again, and it only ever deletes inside the download folder.

Before that, Since 89 the package has grown the media library: finished downloads are identified and filed into Movies, TV Shows, Anime and Music with Kids, Family, Adult and 4K branches, with the whole route drawn on one page and every switch on the drawing itself. Notifications can carry the poster on WhatsApp, and the rating, the director and the plot in your own language as text everywhere else. The fragmentation reading beside each folder now colours the volume by the size of the pieces the files are in, and says what that is likely to cost in read speed. Updating keeps your settings, your categories and your torrents.

QTS 6 and QuTS hero.

Rtorrent 16 · WhatsApp

Three ways to get a WhatsApp message when a download finishes; these are the two worth using.

The WhatsApp page in Rtorrent 16: pairing, who may talk to the bot and who gets the notifications The bot's commands, the setup steps and how the add-on differs from the hosted bot

The hosted bot — nothing to install

Open Notifications in the Control Center, press pair, and the panel shows an eight-character code. Send that code to the bot's number from your phone, and the pairing is done. The NAS then posts to our small service, which talks to Meta's official WhatsApp Cloud API. Your number is stored against a token that only your NAS has; nobody can message you by guessing a phone number, and STOP in the chat ends it immediately.

The add-on — your own bot, your own number

If you would rather no service of ours stood in between, install rtorrent16-whatsapp. It runs a WhatsApp client on the NAS itself, pairs to your own WhatsApp account by scanning a QR code from your phone, and sends from that account. No third party, no API keys, no message limits — and it is your account that does the sending, with everything that implies.

It answers in that chat too: write what you want in plain words and it searches your trackers, forward it a .torrent file and it puts it on, and a finished film arrives with its poster when Movie Agent has its keys.

What Meta allows, plainly

A business number may message a person freely for 24 hours after that person writes to it. After that only pre-approved template messages go through, until the person writes again. That is Meta's rule, not ours, and it is why the hosted bot asks you to send a pairing code from your own phone instead of simply taking your number. Meta's pricing page also says it starts charging for these messages again on 1 October 2026 — the add-on, which sends from your own account, is outside all of that.

Did you know

QTS itself can use the same route. Control Panel → Notification Center → SMS → add a custom SMSC service, point it at the URL the panel shows you, and every system notification QNAP would have sent as a text message arrives on WhatsApp instead. The phone number QTS insists on filling in is ignored — the token decides who gets the message.

Installation

Recommended — from App Center. Add this site's repository once; after that this package installs and updates from App Center like any other app. App Center never offers an update to a package installed by hand; the panel still says when a new build is out.

  1. App Center → ⚙ Settings → App Repository → Add.
  2. Name it QNAP Utilities, paste https://www.qnaputilities.com/repo.xml, Add.
  3. Open QNAP Utilities in the left rail and install Rtorrent 16 WhatsApp.

The repository panel: every package in the feed →

By hand instead: take the build for your architecture below, then App Center → Install Manually.

Download

The hosted bot needs no download — it is part of Rtorrent 16. This add-on is only for running your own.

Rtorrent 16 · Telegram

An unofficial add-on that uses the Telegram API to run your own Telegram bot for Rtorrent 16. Telegram did not make it and does not endorse it. The bot runs on the NAS and logs in to Telegram directly with your bot’s token, without any service of ours in between.

The Telegram page in Rtorrent 16: status, the setup steps, the bot token and API keys, pairing

Setting it up

Create the bot in Telegram with @BotFather, and register an app at my.telegram.org for an api_id and an api_hash. Enter all three on the Telegram page of the Control Center, then press Get a pairing code: six digits, valid for ten minutes and good once, shown as a QR code and as /start <code>. The bot takes orders only from accounts paired this way.

What it does

Installation

Recommended — from App Center. Add this site's repository once; after that this package installs and updates from App Center like any other app. App Center never offers an update to a package installed by hand; the panel still says when a new build is out.

  1. App Center → ⚙ Settings → App Repository → Add.
  2. Name it QNAP Utilities, paste https://www.qnaputilities.com/repo.xml, Add.
  3. Open QNAP Utilities in the left rail and install Rtorrent 16 Telegram.

The repository panel: every package in the feed →

By hand instead: take the build for your architecture below, then App Center → Install Manually.

Download

It needs Rtorrent 16 16.24-05S or newer; on an older one the install stops and says so. Sending films needs 16.24-05U or newer.

Rtorrent 16 · Search

The module that extends Rtorrent 16 with a search: a Search page in the Control Center that asks about a hundred public trackers and your own accounts. Type a title, and the results arrive live from every source that answers, the healthiest first: seeders, leechers, freshness, freeleech and how well the name fits what you typed. Open a row to see the files inside the release before you take it, then press Add: the panel's own add form slides down under the row with the category badges and their guess, or tick several rows and add them all at once.

The Search page in Rtorrent 16: one box for a title, year, resolution or episode, with examples to try

No account anywhere

About a hundred public trackers switch themselves on the moment the add-on starts. Nothing to type, nothing to register. A source that stops answering rests for six hours and comes back on its own; the Trackers page shows every source, its state and its latency, with a switch for each.

Accounts are optional

Some five hundred private and semi-private trackers join through their own login forms, rendered in the panel exactly as each tracker describes them. Passwords stay inside the add-on on the NAS; the panel only ever shows a mask.

What it needs

Rtorrent 16 16.22-02F or newer. About 120 MB on the volume and some 200 MB of RAM while the engine runs (it is Jackett, on the loopback interface only, with its update check off).

Behind Cloudflare

Some trackers put a Cloudflare challenge in front of every page, and a search engine alone cannot get past it. The Rtorrent 16 FlareSolverr add-on beside this one is the package for that: a FlareSolverr with its own Chromium, on this NAS, that solves the challenge and hands the engine the cookie. Install it and the search add-on finds it by itself at the next sync; the Trackers page says how many sources Cloudflare stopped and whether the solver is on. One you run elsewhere can be named in the same place instead.

Installation

Recommended, from App Center. Add this site's repository once; after that this package installs and updates from App Center like any other app. App Center never offers an update to a package installed by hand; the panel still says when a new build is out.

  1. App Center → ⚙ Settings → App Repository → Add.
  2. Name it QNAP Utilities, paste https://www.qnaputilities.com/repo.xml, Add.
  3. Open QNAP Utilities in the left rail and install Rtorrent 16 Search.

The repository panel: every package in the feed →

By hand instead: take the build for your architecture below, then App Center → Install Manually.

Download

The add-on needs Rtorrent 16 on the same NAS; the Search page appears in the panel's bar the moment it is installed. Removing the add-on forgets the tracker accounts; upgrading keeps them.

Rtorrent 16 · Gopeed

Gopeed is a download manager with a web UI and a browser extension for Chrome, Edge and Firefox: a link on any page, one click, and the NAS downloads it. It speaks http, FTP and FTPS, HLS streams, ed2k and BitTorrent. This package runs our own build of Gopeed on the NAS, with one process of ours in front of it.

Gopeed 2 on a computer and a phone: the task list with progress and speeds Gopeed on the NAS: the task list Gopeed on the NAS: searching the task list

Screenshot: Gopeed

Beside Rtorrent 16

When Rtorrent 16 is installed on the same NAS, Gopeed never downloads a torrent itself. A magnet or a .torrent link, from the extension or from Gopeed's own add dialog, becomes a file in Rtorrent 16's watch folder and Rtorrent 16 takes it from there, with its own categories, its own rules and its own panel. Gopeed's list shows those torrents too, with progress, speed and state, and its pause, resume and delete buttons act on Rtorrent 16 (delete removes the torrent, never the files). Everything else Gopeed downloads itself. So does a magnet that one of your debrid services already has cached, when that service is switched on in the debrid extension (below): its files then come from the service as direct downloads. Gopeed's BitTorrent settings stay on screen, greyed out under “Rtorrent16 enabled”. Without Rtorrent 16 the package is plain Gopeed, torrents included.

Debrid and premium hosts

The package installs its own Gopeed extension, Debrid & premium hosts. Switch on an account in its settings and enter the account's API key, and a hoster link, or a magnet the service already has cached, becomes a direct download through TorBox, AllDebrid, Premiumize, Real-Debrid, Debrid-Link or one of the multihoster and premium-host services the extension knows. An upgrade keeps those settings.

The extension

Install the Gopeed browser extension from its store page, open its settings, choose Server, put http://<your NAS>:6040 as the URL and the token from the System Logs as the token. The web login and the token are made on the NAS at the first start; right after the installation a warning in QTS System Logs, shown as a notice on the QTS desktop, carries the address with the NAS's own IP, the login, a short password and the token, so nothing needs SSH. The web UI also takes your Rtorrent 16 login and any account of the NAS itself, so the short password is there only for a NAS without either. The same line sits in /usr/bin/Rtorrent16-Gopeed/var/log/first-run.txt, and /etc/init.d/rtorrent16-gopeed.sh token prints it again; reset-token makes a new one. The web UI on port 6040 asks for that login.

What it needs

QTS 5.2 or QuTS hero 6. About 120 MB on the volume. Downloads go to Download/gopeed on the first share of that name (else Public/gopeed). Gopeed is our build 2.0.0-beta.3+rt16.2: upstream's code as of 25 September 2026 with four patches (FTP and FTPS, adaptive connections, scripts on errors, the greyed-out BitTorrent settings), built without usage analytics; its own settings stay yours, except the four the add-on needs.

Installation

Recommended, from App Center. Add this site's repository once; after that this package installs and updates from App Center like any other app. App Center never offers an update to a package installed by hand; the panel still says when a new build is out.

  1. App Center → ⚙ Settings → App Repository → Add.
  2. Name it QNAP Utilities, paste https://www.qnaputilities.com/repo.xml, Add.
  3. Open QNAP Utilities in the left rail and install Rtorrent 16 Gopeed.

The repository panel: every package in the feed →

By hand instead: take the build for your architecture below, then App Center → Install Manually.

Download

Standalone: no other package required. Upgrading keeps the login, the token and Gopeed's own data; removing the package forgets them.
Gopeed is free software under the GNU GPL version 3. The source of this build, the upstream tree with our patches and build scripts: gopeed-2.0.0-beta.3+rt16.2-source.tar.gz.

Rtorrent 16 · FlareSolverr

A tracker behind Cloudflare shows every visitor a challenge page first, and the search engine, which is not a browser, gets that page instead of results. FlareSolverr is the usual answer: a real Chromium that opens the page, passes the challenge and hands the cookie back, so the engine can ask again as a browser would. Until now it meant Container Station and a docker line. This package is that FlareSolverr as a QPKG, with the Chromium inside it, on this NAS.

Nothing to set up

Install it beside Rtorrent 16 Search and that is all: the solver listens on the loopback interface only, and the search add-on looks for one there at every sync and hands it to the engine by itself. The Trackers page shows FlareSolverr found, and the sources Cloudflare had stopped come back once their six-hour rest ends, or at once with Check now. Removing the package takes them off again, just as quietly.

What is inside

FlareSolverr 3.5.2, upstream's own build, with a Chromium 153 of its own and the driver that matches it; a virtual display (Xvfb) with its keyboard maps, because Cloudflare notices a headless browser and QTS has no display at all; four DejaVu faces so pages have a font to render with. Everything the browser needs and QTS lacks travels in the package. Nothing phones home: the browser opens only the pages the search engine asks for.

What it needs

An x86_64 NAS: upstream builds the bundle for x64 alone, so there is no arm_64 package. Rtorrent 16 Search installed. About 800 MB on the volume; around 100 MB of RAM while it waits, and up to 1.4 GB for the ten seconds or so a challenge is being solved (a real Chromium with its renderer and GPU processes; the cookie is then kept by the engine, so a source is solved once, not per search). A NAS with 4 GB or less will feel that moment.

Installation

Recommended, from App Center. Add this site's repository once; after that this package installs and updates from App Center like any other app. App Center never offers an update to a package installed by hand; the panel still says when a new build is out.

  1. App Center → ⚙ Settings → App Repository → Add.
  2. Name it QNAP Utilities, paste https://www.qnaputilities.com/repo.xml, Add.
  3. Open QNAP Utilities in the left rail and install Rtorrent 16 FlareSolverr.

The repository panel: every package in the feed →

By hand instead: take the build below, then App Center → Install Manually.

Download

The add-on needs Rtorrent 16 Search on the same NAS. Its own shell command, /etc/init.d/rtorrent16-flare.sh test <url>, asks the solver for a page and prints what came back, for when you want to see it work.

Rtorrent 16 · IRC

Private trackers announce new releases on IRC, in a channel you have to be in when the announcement happens. Miss the two seconds and the release is gone. A bouncer is a program that stays in the channel for you: it holds one connection to the network, and your laptop, your phone and Rtorrent 16 autobrr all attach to the bouncer instead of to the tracker.

The IRC page in Rtorrent 16: the bouncer's state, the web client and the first-run login

Why that matters on a tracker

Most private trackers allow one IRC connection per account. Without a bouncer, Rtorrent 16 autobrr uses it and you cannot be in the channel yourself — or you are in it and the bot is not. With one, the channel sees a single user, and both of you are behind it.

What is in the package

soju, the bouncer, on port 6667 for any IRC client and for Rtorrent 16 autobrr, and The Lounge as the web client on 6690 — with an account and a password, already connected to the bouncer; you add your tracker's network. It also appears in the QTS panel at /rtorrent16-irc/, with the NAS's own certificate.

First run creates one login for both, writes it to a file, and puts it in the QNAP system log as a warning that says to change it. The package is standalone: it does not touch Rtorrent 16.

Did you know

soju invents its own protocol extensions in a private namespace and treats them as a testing ground for the IRC standard itself: if one works out, it is proposed for standardisation and other clients start implementing it. IRC was written in 1988, and it is still how the fastest corner of the file-sharing world distributes news, because nothing else is as cheap to run or as quick to arrive.

Installation

Recommended — from App Center. Add this site's repository once; after that this package installs and updates from App Center like any other app. App Center never offers an update to a package installed by hand; the panel still says when a new build is out.

  1. App Center → ⚙ Settings → App Repository → Add.
  2. Name it QNAP Utilities, paste https://www.qnaputilities.com/repo.xml, Add.
  3. Open QNAP Utilities in the left rail and install IRC (soju + The Lounge).

The repository panel: every package in the feed →

By hand instead: take the build for your architecture below, then App Center → Install Manually.

Download

soju is by Simon Ser, AGPL-3.0. Packaged here, not written here.

Rtorrent 16 autobrr

Rtorrent 16 autobrr reads the announce channels and RSS feeds of the trackers you are on, matches every new release against filters you wrote once, and pushes the ones that match into rtorrent — usually within a second or two of the release appearing.

autobrr dashboard: release statistics and recent filter activity The Rtorrent 16 IRC page, with the bouncer address, nick and password autobrr uses

Screenshot: autobrr

Rtorrent 16 autobrr running on a QNAP: filters, indexers and the release feed

Rtorrent 16 autobrr 1.85 on QTS, talking to Rtorrent 16 over the panel's RPC endpoint.

What a filter looks like

"Anything from these three groups, 1080p or 2160p, not HDR, under 20 GB, from these two trackers, and put it in the tv category." Written in a form, not in a configuration file, and a test action shows whether it matches before anything is downloaded.

A little history

Ludvig Lundgren started it in 2021, with inspiration from trackarr, autodl-irssi and flexget — and the aim of doing in one tool what previously took three. autodl-irssi was an irssi script that everyone on a private tracker ran and nobody enjoyed maintaining; autobrr does not so much replace it as read it, since it imports autodl-irssi filters directly.

It ships definitions for over a hundred trackers, each one naming the IRC network, the channel, the nicknames that are allowed to announce, and the patterns that turn a line of chat into a release.

Did you know

For a project built entirely around IRC it would have been strange not to have a channel, so autobrr runs its own IRC server. The reason speed matters is arithmetic: on most private trackers the seeders who arrive first accumulate the ratio that pays for everything downloaded later. A filter that fires two seconds after the announce and one that fires two minutes after it are not the same tool — which is also why autobrr prefers announce channels to RSS.

Installation

Recommended — from App Center. Add this site's repository once; after that this package installs and updates from App Center like any other app. App Center never offers an update to a package installed by hand; the panel still says when a new build is out.

  1. App Center → ⚙ Settings → App Repository → Add.
  2. Name it QNAP Utilities, paste https://www.qnaputilities.com/repo.xml, Add.
  3. Open QNAP Utilities in the left rail and install Rtorrent 16 autobrr.

The repository panel: every package in the feed →

By hand instead: take the build for your architecture below, then App Center → Install Manually.

Download

Rtorrent 16 autobrr packages autobrr by the autobrr team, GPL-2.0 — packaged here, not written here. Needs Rtorrent 16 for the RPC endpoint it pushes to.

slskd · Soulseek

Soulseek is a file-sharing network built around music and the people who collect it. There are no trackers and no torrents: you search, you see who has it, you browse their shared folders, and you queue what you want. It is where a 1997 bootleg with no release anywhere else usually turns out to be.

slskd search results: one user's folder with its files, sizes and bitrates slskd downloads: files in progress and finished

Screenshot: slskd

slskd is Soulseek as a service. It runs headless on the NAS with a web interface, shares the folders you point it at, and keeps its place in the download queues while your computer is off — which matters on a network where a queue position can take hours. The package ships upstream's current canary build (0.26.0.65534, commit 042701b5 of 14 September 2026), taken from upstream's own container image, since a canary is published in no other form; the QPKG version stays 0.26.0.

A little history

Nir Arbel announced Soulseek on an electronic-music mailing list on 8 April 2001, with the note that his username on his own network was plaid and that he had "got all my techno CDs mp3ed and shared to get things started". Twenty-five years later the network is still running and still administered by the same person.

Did you know

Soulseek clients carry licence-enforced identification. The server tells implementations apart by a version number, and the library slskd is built on obliges anyone shipping a client to claim their own range — slskd's is recorded in public as 760 to 7699999. A file-sharing network with a registry of who wrote what is a rarer thing than it sounds.

Installation

Recommended — from App Center. Add this site's repository once; after that this package installs and updates from App Center like any other app. App Center never offers an update to a package installed by hand; the panel still says when a new build is out.

  1. App Center → ⚙ Settings → App Repository → Add.
  2. Name it QNAP Utilities, paste https://www.qnaputilities.com/repo.xml, Add.
  3. Open QNAP Utilities in the left rail and install Soulseek (slskd).

The repository panel: every package in the feed →

By hand instead: take the build for your architecture below, then App Center → Install Manually.

Download

slskd is by JP Dillingham, AGPL-3.0 with additional terms. Packaged unmodified, not written here. Standalone — it needs nothing else on the NAS.

Aria2 · downloads

aria2 downloads files over HTTP(S), FTP, SFTP, BitTorrent and Metalink, many at once and each over several connections, and takes its orders through a JSON-RPC interface. AriaNg is its web interface: the download lists, adding links, torrents and Metalink files, aria2’s settings and its speed graphs.

With the other apps on the NAS

Aria2 runs as the account aria2 in the group arr and downloads into /share/Download/Aria2, or into /share/Public/Aria2 when the NAS has no shared folder Download; dir in aria2.conf names the folder. The folder has the group arr, which can write to it, so Sonarr, Radarr and the other *arr apps can move what Aria2 downloads.

First start

App Center’s Open leads to http://<NAS>:9180/. aria2 does not run until you have chosen its RPC secret, the password that every client sends with each call: the page there asks for it twice, at least 8 characters. The package sets none and writes no generated one. Once you press Start aria2, aria2 starts and AriaNg opens, already connected in this browser.

The page takes the secret from a computer on the NAS’s own network only, and for 60 minutes after the package starts; restart Aria2 in App Center to open it again. System Logs names the port at every start. In another browser AriaNg already points at the NAS’s port 9180 and asks for the secret: AriaNg Settings → RPC → Aria2 RPC Secret Token. Other aria2 clients use http://<NAS>:9180/jsonrpc with the same secret.

The package

aria2 1.37.0 with SFTP through libssh2, and AriaNg 1.3.14, both built from source by the App Builder of Bucket & Code Server IDE. aria2c is a static program: OpenSSL, c-ares, libssh2, SQLite, expat and zlib are inside it, the package’s CA bundle checks HTTPS certificates, and from QTS it loads nothing but glibc. AriaNg is built from its release tag with Node.js; the package carries the built files, not Node.js. A small program of ours, aria2gate, serves AriaNg on port 9180, passes /jsonrpc to aria2c, which listens on 127.0.0.1:9181 only, and starts aria2c once the secret exists; BusyBox 1.38.0 runs it as the account. Settings and the secret are in <install volume>/Aria2/aria2.conf, readable by the account only, next to aria2.session (the unfinished downloads), the DHT tables and log/aria2.log; an upgrade or a removal leaves the folder in place. To change the secret, stop the package, edit rpc-secret= in aria2.conf and start it. What you change in AriaNg’s Aria2 Settings lasts until aria2 restarts; aria2.conf keeps what you write there.

A little history

aria2’s README calls it “the ultra fast download utility”. Its source files say Copyright 2006 Tatsuhiro Tsujikawa, and its AUTHORS file names Ross Smith II for the Windows port. The 1.37.0 packed here was tagged on 15 November 2023. AriaNg’s licence names MaysWind as its author, for the years 2016 to 2026.

Installation

Recommended — from App Center. Add this site’s repository once; after that the package installs and updates from App Center like any other app.

  1. App Center → ⚙ Settings → App Repository → Add.
  2. Name it QNAP Utilities, paste https://www.qnaputilities.com/repo.xml, Add.
  3. Open QNAP Utilities in the left rail and install Aria2.

The repository panel: every package in the feed →

By hand instead: take the build below, then App Center → Install Manually.

What it needs

A QNAP NAS with an x86_64 processor (Intel or AMD) on QTS 6.0 or QuTS hero 6.0 or newer.

Download

Package name Aria2, aria2 1.37.0 and AriaNg 1.3.14. SHA-256 of 1.37.0.2: c87749c189513f09c82f8d2c1d55dc0a61d0a613f3a007229019db27963bd868 (.sha256). aria2 is by aria2’s developers, GPL-2.0-or-later with an exception that allows linking OpenSSL; AriaNg is by MaysWind, MIT; packed here, not written here. The package also carries OpenSSL (Apache-2.0), libssh2 (BSD-3-Clause), c-ares (MIT), expat (MIT), SQLite (public domain), zlib (Zlib), a CA bundle (MPL-2.0), glibc (LGPL-2.1-or-later), the C++ runtime (GPL-3.0 with the GCC Runtime Library Exception), BusyBox (GPL-2.0), the Go runtime of aria2gate (BSD-3-Clause) and the npm packages that AriaNg bundles, each under its own licence; share/licenses/NOTICE in the install folder names each part with its licence and source. Upstream: aria2.github.io · source · release notes · manual · AriaNg.

qBittorrent · torrents

qBittorrent is a BitTorrent client. The package runs qbittorrent-nox, its server without a window, and you work with it in the browser: VueTorrent is the web interface, which also works on a phone, and qBittorrent serves it in place of its own.

VueTorrent, the web interface for qBittorrent: the torrent list and a context menu, dark theme VueTorrent: the same list in the light theme

Screenshot: VueTorrent

With the other apps on the NAS

qBittorrent runs as the account qbittorrent in the group arr and downloads into /share/Download/qBittorrent, or into /share/Public/qBittorrent when the NAS has no shared folder Download; that folder is qBittorrent’s default save path. It has the group arr, which can write to it, so Sonarr, Radarr and the other *arr apps can move what qBittorrent downloads.

First start

App Center’s Open leads to http://<NAS>:9190/. qBittorrent 5 starts its web interface with a temporary password that it prints to its output when none is set. The package does not allow that: qbittorrent-nox starts only once the web interface has a password you chose, so none is generated and none reaches the log. The page there asks for the user name (admin unless you change it; 3 to 64 letters, digits and . _ @ -) and for the password twice, at least 8 characters. Once you press Start qBittorrent, qbittorrent-nox starts and VueTorrent asks you to sign in.

The page takes the user name and password from a computer on the NAS’s own network only, and for 60 minutes after the package starts; restart qBittorrent in App Center to open it again. System Logs names the port at every start. qBittorrent keeps a hash of the password, not the password; VueTorrent’s settings change the password, the downloads folder and the limits.

The package

qBittorrent 5.2.4 on Qt 6.11.2 and libtorrent-rasterbar 2.0.15, with OpenSSL 3.5.8, and VueTorrent 2.36.1, all built from source by the App Builder of Bucket & Code Server IDE. qbittorrent-nox is a static program: Qt without a GUI, libtorrent, OpenSSL and zlib are inside it, the package’s CA bundle checks HTTPS certificates, and from QTS it loads nothing but glibc. VueTorrent is built from its release tag with Node.js; the package carries the built files, not Node.js. A small program of ours, qbtgate, holds the web port until the password exists, then hands it to qbittorrent-nox and stays as its parent; at every start it writes port 9190 into qBittorrent’s settings, so a port changed in VueTorrent is put back; BusyBox 1.38.0 runs it as the account. The profile is in <install volume>/qBittorrent: the settings in qBittorrent/config/qBittorrent.conf, readable by the account only, the torrents’ state in qBittorrent/data/ and the log in log/qbittorrent.log. An upgrade or a removal leaves the folder in place.

A little history

qBittorrent’s README calls it a BitTorrent client programmed in C++ and Qt that uses libtorrent, by Arvid Norberg. Its source files carry Christophe Dumez’s copyright from 2006, and its AUTHORS file names him the original author and Sledgehammer999 the current maintainer. VueTorrent’s README describes it as a WebUI for qBittorrent made with Vue.js.

Installation

Recommended — from App Center. Add this site’s repository once; after that the package installs and updates from App Center like any other app.

  1. App Center → ⚙ Settings → App Repository → Add.
  2. Name it QNAP Utilities, paste https://www.qnaputilities.com/repo.xml, Add.
  3. Open QNAP Utilities in the left rail and install qBittorrent.

The repository panel: every package in the feed →

By hand instead: take the build below, then App Center → Install Manually.

What it needs

A QNAP NAS with an x86_64 processor (Intel or AMD) on QTS 6.0 or QuTS hero 6.0 or newer.

Download

Package name qBittorrent, qBittorrent 5.2.4 and VueTorrent 2.36.1. SHA-256 of 5.2.4.2: 3e02762e8b928978d4e92baf3ffc5b461b52553500fdc1e61c77a760325d5cce (.sha256). qBittorrent is by qBittorrent’s developers, GPL-2.0-or-later with an exception that allows linking OpenSSL; VueTorrent is by VueTorrent’s developers, GPL-3.0-only; packed here, not written here. The package also carries Qt (LGPL-3.0-only, linked statically), libtorrent-rasterbar (BSD-3-Clause), Boost’s headers (BSL-1.0), OpenSSL (Apache-2.0), zlib (Zlib), a CA bundle (MPL-2.0), glibc (LGPL-2.1-or-later), the C++ runtime (GPL-3.0 with the GCC Runtime Library Exception), BusyBox (GPL-2.0), the Go runtime of qbtgate (BSD-3-Clause) and the npm packages that VueTorrent bundles, each under its own licence; share/licenses/NOTICE in the install folder names each part with its licence and source. Upstream: qbittorrent.org · source · release notes · wiki · VueTorrent.

Transmission · torrents

Transmission is a BitTorrent client. The package runs transmission-daemon, its server without a window, and you work with it in the browser: Transmission’s own web interface, which the daemon serves together with its RPC.

With the other apps on the NAS

Transmission runs as the account transmission in the group arr and downloads into /share/Download/Transmission, or into /share/Public/Transmission when the NAS has no shared folder Download, or into downloads/ in its data folder when it has neither. The first start makes the folder with mode 2775: it belongs to the account, its group is arr, which can write to it, and new files keep that group. Sonarr, Radarr and the other *arr apps can move what Transmission downloads. The Transmission client settings of Sonarr, Radarr and Lidarr default to port 9091, the port of this package.

First start

App Center’s Open leads to http://<NAS>:9091/transmission/web/. transmission-daemon’s own defaults have no password and take RPC calls from the NAS itself only; opened to the network without a password, it would serve anyone who reaches port 9091. The package does not allow that: transmission-daemon starts only once its web interface has a password you chose, so none is generated and none is written to a file or to System Logs. The page there asks for the user name (admin unless you change it; 3 to 64 letters, digits and . _ @ -) and for the password twice, at least 8 characters. Once you press Start Transmission, transmission-daemon starts on the same port and the browser asks you to sign in to the web interface.

The page takes the user name and password from a computer on the NAS’s own network only, and for 60 minutes after the package starts; restart Transmission in App Center to open it again. Open it at the NAS’s IP address or its own name: a password sent under any other name is refused, even a name that points at the NAS. System Logs names the port at every start. Transmission keeps a salted hash of the password in config/settings.json, not the password.

The web interface’s settings change the downloads folder, the speed limits and the peer port; peers connect on 51413, TCP and UDP, which the package writes at the first start only. The web port 9091 is fixed: a start sets it back if settings.json holds another. The RPC cannot change the password. To choose a new one, stop Transmission in App Center, take rpc-password out of config/settings.json in the data folder and start it again: the page asks for a new password, for 60 minutes.

The package

Transmission 4.1.3 and its web interface, with libnatpmp 20230423, miniupnpc 2.3.3, libdeflate 1.26, curl 8.22.0, OpenSSL 3.5.8, zlib 1.3.2 and libevent 2.1.13, all built from source by the App Builder of Bucket & Code Server IDE. libnatpmp, miniupnpc, libdeflate, Transmission and its web interface are recipes of the example project itself. transmission-daemon is a static program: the libraries are inside it, the package’s CA bundle checks the HTTPS certificates of trackers and blocklist servers, and from QTS it loads nothing but glibc. transmission-remote, transmission-create, transmission-edit and transmission-show are in the package too. The web interface is built from web/ of the release with esbuild and Sass, every npm package pinned by its hash; the package carries the built files, not Node.js. A small program of ours, trgate, holds port 9091 until the password exists, then starts transmission-daemon on it and stays as its parent; BusyBox 1.38.0 runs it as the account. The data is in <install volume>/Transmission: config/settings.json with the salted password, Transmission’s torrents and resume files in config/, and the log in log/transmission.log. An upgrade or a removal leaves the folder in place.

A little history

Transmission’s README calls it “a fast, easy, and free BitTorrent client” and lists its flavors, among them a headless daemon for servers and routers and a web UI that controls any of the others remotely. Its COPYING file dates the copyright from 2005. Its AUTHORS file names Eric Petit the project’s originator and Josh Elsasser for the daemon and the backend, and lists Charles Kerr, Mike Gelfand and Mitchell Livingston as the maintainers.

Installation

Recommended — from App Center. Add this site’s repository once; after that the package installs and updates from App Center like any other app.

  1. App Center → ⚙ Settings → App Repository → Add.
  2. Name it QNAP Utilities, paste https://www.qnaputilities.com/repo.xml, Add.
  3. Open QNAP Utilities in the left rail and install Transmission.

The repository panel: every package in the feed →

By hand instead: take the build below, then App Center → Install Manually.

What it needs

A QNAP NAS with an x86_64 processor (Intel or AMD) on QTS 6.0 or QuTS hero 6.0 or newer.

Download

Package name Transmission, Transmission 4.1.3. SHA-256 of 4.1.3: 0750f1673b680ce5b9f2684671f599b417c7ac6e55bcf197e6b1014c8dfc71a8 (.sha256). Transmission is by the Transmission Project, GPL-2.0-only or GPL-3.0-only, with an allowance to link OpenSSL, some of its files under MIT, BSD-3-Clause, BSL-1.0, Zlib and MPL-2.0 terms; its web interface is GPL-2.0-only with MIT, Apache-2.0 and CC-BY-4.0 parts; packed here, not written here. The package also carries curl (curl license), OpenSSL (Apache-2.0), zlib (Zlib), libevent (BSD-3-Clause), nghttp2 (MIT), zstd (BSD-3-Clause), c-ares (MIT), libnatpmp (BSD-3-Clause), miniupnpc (BSD-3-Clause), libdeflate (MIT), a CA bundle (MPL-2.0), glibc (LGPL-2.1-or-later), the C++ runtime (GPL-3.0-or-later with the GCC Runtime Library Exception), BusyBox (GPL-2.0-only) and trgate, our own program, under the Bucket & Code Server IDE Freeware Licence 1.0, with the Go runtime inside it (BSD-3-Clause); share/licenses/NOTICE in the install folder names each part with its license and source. Upstream: transmissionbt.com · source · release notes · documentation.

Weblate · translations

Weblate is a translation server you use in the browser. Each component is a set of translation files in a Git repository: translators work on its strings, Weblate checks them against the project’s glossary and its quality checks, keeps a translation memory, and commits the translations back to the repository.

Weblate: a project's languages with their progress Weblate's dashboard of the translations you follow

Screenshot: Weblate

First start

App Center’s Open leads to http://<NAS>:9280/. The page there shows the login, admin, and asks for its password twice, at least 8 characters. No password is generated, and none is written to a file or to System Logs: the package keeps Django’s salted hash of it. Once you press Start Weblate, Weblate starts and the page offers its sign-in: login admin and the password you chose.

The page takes the password from a computer on the NAS’s own network only, until admin has one. Open it at the NAS’s IP address or its own name: a password sent under any other name is refused. System Logs names the port and the login at every start.

Weblate here sends no e-mail, so its Forgot your password? opens the package’s own note instead. For admin, two lines in a shell on the NAS open the setup page again; the note shows them with the data folder’s path. Another account’s password is set by admin in Weblate administration (/admin/, Users, Reset password).

In a jail

Weblate, PostgreSQL, Valkey, Celery and the web server run as the account weblate inside bvs-jail: no capabilities, a network of their own that has only the loopback, and one way out, a forward to Bucket & Code Server IDE’s Git server on the NAS (127.0.0.1:9960, there when its Git and CI modules are on). Weblate fetches and pushes over http from 127.0.0.1 only and reaches no other server. No machine translation: the suggestions come from the translation memory and the matches in other components, and the add-ons that translate or judge by machine are not offered. The package adds the version control backend Forgejo pull request: Weblate pushes a branch and opens a pull request in Bucket & Code’s Forgejo, with the account’s token from forgejo-credentials in the data folder.

The package

Weblate 2026.10 on Python 3.14.7, with PostgreSQL 18.6, Valkey 9.1.2, Git 2.55.0, OpenSSH 10.5p1, Borg 1.4.5, OpenSSL 3.5.8 and curl 8.22.0, built from source by the App Builder of Bucket & Code Server IDE; Weblate and its 212 Python packages are PyPI’s wheels, each pinned by its hash. A small program of ours, wlgate, holds port 9280: the setup page until admin has a password, then Weblate, with the client’s address passed on. The data is in <install volume>/Weblate: the database in pg/, Weblate’s files in data/, its nightly Borg backup in backups/ and the logs in log/. An upgrade or a removal leaves the folder in place.

A little history

Weblate’s README calls it “libre software web-based continuous localization system, used by over 2500 libre projects and companies in more than 165 countries”. Its source files name Michal Čihař as the copyright holder; weblate.org also runs it as a hosted service and sells support.

Installation

Recommended — from App Center. Add this site’s repository once; after that the package installs and updates from App Center like any other app.

  1. App Center → ⚙ Settings → App Repository → Add.
  2. Name it QNAP Utilities, paste https://www.qnaputilities.com/repo.xml, Add.
  3. Open QNAP Utilities in the left rail and install Weblate.

The repository panel: every package in the feed →

By hand instead: take the build below, then App Center → Install Manually.

What it needs

A QNAP NAS with an x86_64 processor (Intel or AMD) on QTS 6.0 or QuTS hero 6.0 or newer. Weblate’s jail may use up to 3 GB of memory.

Download

Package name Weblate, Weblate 2026.10. SHA-256 of 2026.10.1: 13b07a15bbd4c9b640cd6fcbbe4390a1377ffabb7fbd109d8a44b6d2e0552b04 (.sha256). Weblate is by Michal Čihař, GPL-3.0-or-later, some of its files under other licences that its REUSE.toml names; packed here, not written here. The package also carries Python (PSF-2.0), PostgreSQL (PostgreSQL License), Valkey (BSD-3-Clause), Git (GPL-2.0-only), OpenSSH (BSD-2-Clause, BSD-3-Clause, ISC), Borg (BSD-3-Clause), OpenSSL (Apache-2.0), curl (curl license), Weblate’s 212 Python packages each with its own licence, BusyBox (GPL-2.0-only), bubblewrap (LGPL-2.0-or-later), and wlgate, bvs_weblate and bvs-jail, our own, under the Bucket & Code Server IDE Freeware Licence 1.0, with the Go runtime inside wlgate (BSD-3-Clause); licenses/NOTICE in the install folder names each part with its licence and source. Upstream: weblate.org · source · release notes · documentation.

Tolgee · translations

Tolgee is a translation server for the strings of apps, used in the browser. A project holds keys with their translations in many languages. You import and export the usual file formats (JSON, PO, XLIFF, Android and Apple string files among them), translators see the translation memory beside each string, and developers’ tools reach it through its API.

First start

App Center’s Open leads to http://<NAS>:9290/. The page there shows the login, admin, and asks for its password twice, 8 to 50 characters. No password is generated, and none is written to a file or to System Logs: the package hands it to Tolgee’s first start through a named pipe, and Tolgee keeps only its bcrypt hash. Once you press Start Tolgee, Tolgee starts, which takes a minute or two the first time, and the page offers its sign-in: login admin and the password you chose.

The page takes the password from a computer on the NAS’s own network only, until admin has one. Open it at the NAS’s IP address or its own name: a password sent under any other name is refused. System Logs names the port and the login at every start.

Tolgee here sends no e-mail: its sign-in page still shows Forgot your password?, but that link only leads back to the sign-in page. A password you know is changed in Tolgee’s account settings, under Account security. For admin, two lines in a shell on the NAS open the setup page again; http://<NAS>:9290/bvs-gate/password shows them with the data folder’s path. Tolgee has no form where admin sets another account’s password: when its owner has forgotten it, admin removes the account in Administration and invites the person again. Registration is closed, so people join through an invitation link that admin makes.

In a jail

Tolgee and PostgreSQL run as the account tolgee inside bvs-jail: no capabilities and a network of their own that has only the loopback, with no way out. Tolgee reaches no server: no telemetry, no e-mail, no translation service. No machine translation is set up. Tolgee lets an organisation’s owner add an AI provider in its settings, but from the jail such a provider cannot reach its service.

The package

Tolgee 3.226.3, its release jar as Tolgee published it, on Java 25 (Eclipse Temurin’s runtime) with PostgreSQL 18.6 and OpenSSL 3.5.8, put together by the App Builder of Bucket & Code Server IDE; PostgreSQL and its libraries are built from source. A small program of ours, tlgate, holds port 9290: the setup page until admin has a password, then Tolgee, with the client’s address passed on. The data is in <install volume>/Tolgee: the database in pg/, Tolgee’s files in data/ and the logs in log/. An upgrade or a removal leaves the folder in place.

Tolgee’s licences

Most of Tolgee is under the Apache License 2.0. Its ee/ part is under the Tolgee EE License: you may use it for non-commercial purposes only, and its features, the glossary among them, stay off until you add a licence key from Tolgee. The package carries the jar unchanged and both licence texts, in licenses/package/tolgee/ of the install folder.

A little history

Tolgee’s README calls it “an open-source localization platform developers enjoy working with”. Its licence names Tolgee s.r.o. as the copyright holder; tolgee.io also runs Tolgee as a hosted service and sells plans for running it yourself.

Installation

Recommended — from App Center. Add this site’s repository once; after that the package installs and updates from App Center like any other app.

  1. App Center → ⚙ Settings → App Repository → Add.
  2. Name it QNAP Utilities, paste https://www.qnaputilities.com/repo.xml, Add.
  3. Open QNAP Utilities in the left rail and install Tolgee.

The repository panel: every package in the feed →

By hand instead: take the build below, then App Center → Install Manually.

What it needs

A QNAP NAS with an x86_64 processor (Intel or AMD) on QTS 6.0 or QuTS hero 6.0 or newer. Tolgee’s jail may use up to 2.5 GB of memory.

Download

Package name Tolgee, Tolgee 3.226.3. SHA-256 of 3.226.3: eef6eeecb4e53be8bbd8f9dca33c5ce986bf707adfd35e3e6f300805b1d10f6f (.sha256). Tolgee is by Tolgee s.r.o., Apache-2.0 with its ee/ part under the Tolgee EE License v1; packed here, not written here. Tolgee’s name and logo are Tolgee s.r.o.’s, which does not make or endorse this package. The package also carries Java (Eclipse Temurin, GPL-2.0-only with the Classpath Exception), PostgreSQL (PostgreSQL License), OpenSSL (Apache-2.0), zlib (Zlib), LZ4 (BSD-2-Clause), Zstandard (BSD-3-Clause), readline (GPL-3.0-or-later), ncurses (X11), the CA certificates (MPL-2.0), BusyBox (GPL-2.0-only), bubblewrap (LGPL-2.0-or-later), and tlgate, tolgee-start.sh and bvs-jail, our own, under the Bucket & Code Server IDE Freeware Licence 1.0, with the Go runtime inside tlgate (BSD-3-Clause); licenses/NOTICE in the install folder names each part with its licence and source. Upstream: tolgee.io · source · release notes · documentation.

MailServerPro · mail

How to start: Your domain on your NAS: website, DNS and mail from the first day →

MailServerPro: the admin panel's overview Mailboxes of a domain The mail domains The DNS records a mail domain needs

Product page: MailServerPro: a mail server for your QNAP NAS →

MailServerPro is a mail server for a QNAP NAS: Postfix for SMTP; Dovecot with Sieve for IMAP, POP3 and LMTP; Rspamd with Valkey as its store, ClamAV and fail2ban against spam, viruses and password guessing; Roundcube for webmail; CalDAV and CardDAV for calendars and contacts; Z-Push for Exchange ActiveSync; and CryptPad as a web office. An admin panel in nine languages manages domains, mailboxes, aliases, DKIM keys, DNS records, the queue, the logs and the backups. ClamAV stays off until the settings switch it on.

First start

App Center’s Open leads to the admin panel, https://<NAS>:9581/admin/; the plain-HTTP port 9580 redirects there. On a new install the panel has no administrator yet and shows First administrator: an address on your first domain and a password of at least 10 characters, typed twice. The package sets no password and generates none; the password is set in that form and nowhere else.

The form is shown only to a computer on the NAS’s own network (a private or loopback address); from anywhere else the panel says so and shows no form. The administrator is a mailbox too and signs in to webmail at https://<NAS>:9581/ with the same password. Calendars and contacts are under /dav/ on the same address.

The admin panel

It speaks English, Polish, German, French, Italian, Dutch, Swedish, Japanese and Traditional Chinese: until a language is picked in its status bar, it takes the first of the browser’s languages it has, else English. Its theme is dark, light or the system’s. Each domain has a page of its own, with its DNS records, its DKIM key, its catch-all, its switch and its deletion. A domain or a mailbox is deleted only after its name is typed.

Settings are lists and number fields. A value that mailctl’s own check refuses is left as it was, with a notice naming the field, and the other fields are saved.

With the other apps on the NAS

A domain’s page lists the DNS records to publish: MX, SPF, DKIM, DMARC, MTA-STS, TLS-RPT, autoconfig and SRV records, and the certificate’s TLSA record. For TurboDNS, MailServerPro.sh dns-records DOMAIN prints the records the mail server owns (DKIM, MTA-STS, TLS-RPT and TLSA) as JSON in the shape TurboDNS takes; WebPortico’s DNS dialog reads them and sends them on. The MX, SPF, DMARC and SRV records come from TurboDNS’s hosting template. The server must be running.

The package

MailServerPro 0.5.7 is built from source by the App Builder of Bucket & Code Server IDE: Postfix 3.11.7, Dovecot 2.4.5 with Pigeonhole, Rspamd 4.2.0, Valkey 9.1.2, Unbound 1.26.1, fail2ban 1.1.1, ClamAV 1.5.4, nginx 1.30.5, PHP 8.4.27, Roundcube 1.7.4, Z-Push 2.7.6, Node.js 24.22.1 with CryptPad 2026.5.1, BusyBox 1.38.0, OpenSSL 3.5.8 and SQLite. The daemons run as accounts of their own.

A control program, mailctl, writes each daemon’s configuration at every start. Everything that changes is in the data folder, <install volume>/MailServerPro: mail, queue, accounts, settings, certificates, keys, logs and backups; an upgrade or a removal leaves it in place. A self-signed certificate is made at the first start; the settings can take the NAS’s own certificate or an imported one instead. The server makes a backup of every mailbox daily.

A little history

Valkey’s README says it was forked from the open source Redis project right before Redis moved to its source-available licenses.

Installation

Recommended — from App Center. Add this site’s repository once; after that the package installs and updates from App Center like any other app.

  1. App Center → ⚙ Settings → App Repository → Add.
  2. Name it QNAP Utilities, paste https://www.qnaputilities.com/repo.xml, Add.
  3. Open QNAP Utilities in the left rail and install MailServerPro.

The repository panel: every package in the feed →

By hand instead: take the build below, then App Center → Install Manually.

What it needs

A QNAP NAS with an x86_64 processor (Intel or AMD) on QTS 6.0 or QuTS hero 6.0 or newer.

The server listens on the standard mail ports (25, 587, 465, 143, 993, 110, 995 and 4190) and on 9580 to 9583 for the web side; QTS keeps 80 and 443. Other servers fetch MTA-STS policies from https://mta-sts.<domain>/ and mail programs fetch Thunderbird’s autoconfiguration from https://autoconfig.<domain>/, both on port 443: forward that port to 9581 on the router, or send those names to https://127.0.0.1:9581 with a WebPortico proxy site or QTS’s reverse proxy.

The web office is at https://<HOSTNAME>:9582/, where HOSTNAME is the host name in Settings; it must resolve to the NAS. Registration is closed until the administrator opens it on the panel’s Office page. With the self-signed certificate a browser must accept it once on 9582 and once on 9583, or the editors stay blank.

Download

Package name MailServerPro. SHA-256 of 0.6.10: 948101c0c4fd5d521c64d1241b345daf7ffa5360623f30167ea49b5870d58bbd (.sha256). MailServerPro is made with Bucket & Code Server IDE; it packs the programs of their own developers, each under its own license: Postfix (IPL-1.0 or EPL-2.0), Dovecot (LGPL-2.1-only and MIT) with Pigeonhole (LGPL-2.1-only), Rspamd (Apache-2.0), Valkey (BSD-3-Clause), Unbound (BSD-3-Clause), fail2ban (GPL-2.0-or-later), ClamAV (GPL-2.0-only), nginx (BSD-2-Clause), PHP (PHP-3.01), Roundcube (GPL-3.0-or-later), Z-Push (AGPL-3.0-only), Node.js (MIT and others), CryptPad (AGPL-3.0-or-later), BusyBox (GPL-2.0-only), OpenSSL (Apache-2.0), SQLite (public domain) and further libraries. The recipe of each part in the App Builder names its license and its source archive. Links: Postfix · Dovecot · Rspamd · Valkey · Roundcube · CryptPad.

WebPortico · websites

How to start: Your domain on your NAS: website, DNS and mail from the first day →

WebPortico's Front server and ports page with the takeover of ports 80 and 443 The list of sites with their PHP version and certificate The Add site wizard: the DNS step at Cloudflare with a checked API token A site's PHP settings

Product page: WebPortico: web hosting on your QNAP NAS →

WebPortico runs websites on a QNAP NAS. It is a web server stack: nginx in front of every site, Apache httpd behind it for the sites set to use it, PHP 8.1 to 8.5, MariaDB, Percona Server, PostgreSQL, memcached and Valkey, with a panel in nine languages that adds, changes and removes the sites.

First start

App Center’s Open leads to the panel, https://<NAS>:9541/; the plain-HTTP port 9540 redirects there. On a new install the panel shows First sign-in: a password of at least 10 characters, typed twice. The package sets no password and generates none, and the panel stores only a hash of the one you set.

The page takes the password only from a computer on the NAS’s own network (a private, loopback or link-local address) and for 60 minutes after the panel starts; until someone sets it, the first person on the network who opens the panel in that hour chooses it. Restart WebPortico in App Center to open it again. A session lasts 8 hours, and 10 failed sign-ins from one address lock that address out for 15 minutes.

Sites

A site is a domain with its aliases, a kind (static files, PHP, or a proxy to a service on the NAS or on the local network, a container included, with websockets), a web server (nginx or Apache httpd) and, if it needs one, a database. A proxy target is an address in a private range, not a hostname. Each site has an account of its own, ws-<ID>, which owns its folder and runs its PHP, so one site’s PHP cannot read another site’s files. The folder is in a QTS shared folder or in WebPortico’s data folder, and its public/ is the document root.

A PHP site runs its own PHP-FPM master, and its PHP tab holds the version (8.1 to 8.5), the time zone, limits, errors, sessions and security, OPcache and the JIT, APCu, the extensions, more php.ini lines and the PHP workers (the pool). A php.ini line is checked against the directives that the version’s own PHP lists; a name that loads code, runs a command, names a file or holds a password is refused. The pool has the process manager (on demand, dynamic or static), the number of processes (on demand with 5 by default), the idle time, the requests per process, a request time limit and a log of slow requests, which the Logs tab shows. A crash or a busy PHP on one site leaves the others running, and a change of one site’s PHP settings restarts that site’s PHP only. A master that exits is started again and stays down after five exits within a minute; logs/php8.N-ID.log says so.

Each site can run scheduled tasks as its own account with its own PHP: a PHP file, a command or the site’s own address, every minute or on any cron schedule. The site’s page shows each run’s result and output, and MailServerPro mails a report when a task starts failing.

Every PHP site has its own Valkey (it speaks Redis’s protocol) and its own memcached, each on a socket in a folder that only that site can open, so neither needs a password or a network port; the site’s Cache tab shows both sockets. Each keeps up to 64 MB, and a restart empties both. Every PHP version has imagick, with ImageMagick reading and writing JPEG, PNG, WebP, GIF and AVIF and reading HEIC. Its policy refuses the formats that read other files or run programs, such as SVG and MSL.

Apache sites’ .htaccess files can also use Digest authentication, groups from a group file, Substitute to rewrite text in a page, and the RATE_LIMIT filter to cap a download’s speed.

A PHP site can also have PECL extensions of its own: its PHP tab builds one as the site’s own account, with no network, in Bucket & Code Server IDE’s builder environment, and only that site’s PHP loads it.

WebPortico can take over the NAS’s web server role in one click, and a fresh install asks once: QTS’s administration moves from port 443 to 44443 and its Web Server from 80 to 8880, each step checked before the next, QTS’s sites come in behind WebPortico, and one click on the Front server and ports page gives 80 and 443 back.

A guided tour leads from standard ports and TurboDNS to your first site, then suggests sharing the DNS server address through the router’s DHCP after checking the DNS configuration.

A PHP or static site that nginx serves has a Cache tab. nginx compresses text answers with Brotli and zstd as well as gzip. A PHP site can turn on a page cache, off by default: visitors with a sign-in cookie always get a fresh page, the X-Cache header says HIT, MISS, STALE, UPDATING or BYPASS, and Purge the cache empties it. Static files can be kept by browsers for 1, 7, 30 or 365 days. nginx takes a request body up to the site’s largest request (the PHP tab’s post_max_size) and answers 413 above it; a proxy site has no body limit at the front.

Add site is a domain wizard: Domain, DNS, Registrar, Website, Database (for a PHP site), Certificate and Review. DNS asks who answers for the zone (TurboDNS on this NAS; the servers of the registrar or a DNS provider; or Cloudflare or OVHcloud, from the zone TurboDNS keeps on this NAS) and which public addresses this NAS has. Registrar lists what to enter where the domain was bought, each value with a copy button, with the router’s forwards and the state of the front under it. The Review’s Preview changes shows the site’s plan and TurboDNS’s plan together, and one apply sends both. The certificate comes from Let’s Encrypt (HTTP-01, where the front serves the file on port 80, or DNS-01 through TurboDNS or Cloudflare; WebPortico renews it when 30 days or less are left), or it is an uploaded one, the NAS’s own or a self-signed one.

After the apply, the site’s Overview has the card Finish setting up <name>: Site active, Records in TurboDNS, At the registrar, Domain check, Certificate and Finish. Check now reads the parent zone’s name servers, this NAS’s TurboDNS, three public resolvers and the front, and says that it cannot see whether ports 53, 80 and 443 reach the NAS from the internet; the Certificate row asks Let’s Encrypt for the certificate. Records in TurboDNS is done once TurboDNS’s plan for the domain finds nothing to change, from the wizard’s dry run, from the row’s Send records or from a repeated send alike, and then reads In TurboDNS since <time>; a site whose records are in the zone already gets it from the dry run.

Every change is a draft first. The dry run renders the whole web tier into a scratch folder, runs nginx -t, httpd -t and php-fpm -t on it and shows the files added, changed and removed with their diffs. The apply carries out exactly that plan, keeps a snapshot of the live files first, reloads gracefully and puts the snapshot back if a step fails. Deleting a site needs its name typed; its folder and databases stay.

For a proxy site, App on this NAS lists the installed apps WebPortico has a template for: Rtorrent 16 and its add-ons, Radarr, Sonarr, Prowlarr, Lidarr, Bazarr, Seerr, Tautulli, qBittorrent, Transmission, TunerHub, Weblate, Tolgee, Bucket & Code Server IDE, Plex Media Server and Jellyfin. Picking one fills in the target with the port the app’s package uses and turns the websocket switch on for apps that need websockets. The front then sends the app X-Forwarded-Host and X-Real-IP, gives an app with long requests up to an hour to answer, and streams media and events without buffering for the apps that send them. A setting only the app itself can change, such as an *arr app’s URL Base, is shown in one line under the choice.

Default site

A request for a name no site has, such as the NAS’s address or its name, goes to the default site: QTS’s Web shared folder when the NAS has one WebPortico can use, otherwise a start page in WebPortico’s data folder. Apache httpd serves it, so the folder’s .htaccess files work, except Options lines, which httpd ignores. Its PHP runs under an account of its own. After the install or the upgrade it is on as a draft: the next dry run and apply put it live. It answers on the front’s ports: 80 once the front has moved there on the Front server and ports page, otherwise 9542. While QTS’s Web Server holds port 80, its page in WebPortico says what to switch off in QTS. It never serves other sites’ folders inside the Web folder, files and folders whose names start with a dot (except .well-known), or QTS’s @ folders, and it shows no folder listing. WebPortico does not change the folder’s permissions. Folders of the Web shared folder that are links to other shared folders or volumes work as they did with QTS’s Web Server, PHP included.

Over HTTPS it answers with the NAS’s own certificate, the one QTS uses for its own pages; while that is QNAP’s self-signed certificate, browsers show a warning. A TLS request for a site without TLS is refused.

WebPortico rotates its own logs: a log is rotated at 10 MiB or after a week, five copies are kept compressed with gzip, and nginx and httpd open their logs again without dropping a request.

Databases

A site gets a MariaDB, Percona Server or PostgreSQL database and user on the Databases page or on its Database tab. Percona Server 8.4 is set up when the first Percona database is made and listens on 127.0.0.1:9555 and on a socket; a NAS that never uses it never starts it. The Databases page has a card for MariaDB and one for Percona Server, with eight settings (the buffer pool, connections, the largest packet, the redo log, temporary tables, the table cache, the idle time, the slow-query time) and more my.cnf lines, checked against the server’s own option list. A change is a draft; the apply restarts the server, so its databases do not answer for a few seconds.

With the other apps on the NAS

When TurboDNS runs on the NAS, the wizard’s DNS step offers it the zone, and the apply sends the records. Without MailServerPro they carry no mail records: a new zone gets the name servers ns and ns1, both this NAS unless you name a second name server, and the A and AAAA records of the site’s names, of ns and of ns1; a zone TurboDNS already serves keeps its own name servers. With MailServerPro installed, the zone gets TurboDNS’s hosting template with the NAS’s public addresses that you confirm, the A and AAAA records of the site’s own names (the template covers the domain, www, ns, ns1 and the mail names, so a second site such as shop.example.com gets its own) and MailServerPro’s DKIM, MTA-STS, TLS-RPT and TLSA records. Nothing is written to TurboDNS before the apply, and the Review shows every record first.

The DNS step’s third answer, Cloudflare or OVHcloud, from the zone TurboDNS keeps on this NAS, gives TurboDNS the same records as the first answer, and a DNS provider answers for the domain. TurboDNS pushes the zone through the provider’s API, and only when you ask: open the zone in TurboDNS, its Cloudflare and OVH tab, Review the changes, then Push the changes. The Registrar step then lists no name servers, glue records or port 53: the registrar keeps the provider’s name servers, and the zone needs no port 53 forward on the router. The domain check then passes on the public resolvers and the front, with the rows Name servers at the registrar and Glue records skipped.

With Bucket & Code Server IDE installed, a site’s Files tab opens its folder in the editor.

Without a public address

A NAS behind CGNAT, or behind a router that forwards no ports, can serve chosen sites on the internet through a Cloudflare Tunnel. The card Reach the sites from the internet through Cloudflare on the Front and ports page takes an API token of your Cloudflare account and a zone whose name servers are Cloudflare’s. WebPortico then makes a tunnel of its own and runs cloudflared, which connects out to Cloudflare. Each applied site gets a switch that gives its names in the zone a proxied CNAME to the tunnel; WebPortico refuses a name that already has an A, AAAA or CNAME record it did not make. Turning the tunnel off deletes the records WebPortico made and the tunnel. Cloudflare ends TLS and sees the traffic, and on its free plan one request can upload at most 100 MB.

The package

WebPortico 0.15.0 is built from source by the App Builder of Bucket & Code Server IDE: nginx 1.30.5, Apache httpd 2.4.68, PHP 8.1.34, 8.2.35, 8.3.36, 8.4.27 and 8.5.12 with PHP-FPM, MariaDB 12.3.3, Percona Server 8.4.11-11 (a second App Builder app in the same package), PostgreSQL 18.6, memcached 1.6.45, Valkey 9.1.2, FFmpeg 9.0.2, ImageMagick 7.1.2-32 (libheif 1.23.6, libde265 1.1.3, libaom 3.15.3), imagick 3.8.1, lego 4.35.2 and cloudflared 2026.10.1. Node.js 24.22.1, Grafana 13.2.4 and OpenSearch 3.8.0 are optional services behind a proxy site; Grafana’s web files and OpenSearch’s jars, with a Java runtime cut down from the vendor’s, are the releases’, not built here. PHP 8.1 is past its end of life, and php.net has no fix in it for CVE-2026-109618 and CVE-2026-109619; move a site on 8.1 to a newer branch.

The panel is a Go program with its page embedded; it runs as an account of its own without root rights, and a root agent does what needs root and takes names and ids, no file content. The daemons run as accounts of their own, added at the first start and kept when the package is removed. Everything that changes is in the data folder, <install volume>/WebPortico; an upgrade or a removal leaves it in place. To move it by hand: stop WebPortico, move the folder (leave no copy at the old path), write the new path into etc/data-dir in the package’s install folder, start. The start takes the sites’ accounts back and renders the servers’ files for the new folder, so the sites answer without an apply.

Installation

Recommended — from App Center. Add this site’s repository once; after that the package installs and updates from App Center like any other app.

  1. App Center → ⚙ Settings → App Repository → Add.
  2. Name it QNAP Utilities, paste https://www.qnaputilities.com/repo.xml, Add.
  3. Open QNAP Utilities in the left rail and install WebPortico.

The repository panel: every package in the feed →

By hand instead: take the build below, then App Center → Install Manually.

What it needs

A QNAP NAS with an x86_64 processor (Intel or AMD) on QTS 6.0 or QuTS hero 6.0 or newer.

The panel is on port 9541 (HTTPS; 9540 redirects there), the front (nginx) on 9542 (HTTP) and 9543 (HTTPS, and UDP for HTTP/3 when nginx has it), and httpd on 127.0.0.1:9544 behind it. The databases, caches and optional services listen on 127.0.0.1 only. The front moves to ports 80 and 443 only when you click it on the Front server and ports page, which lists the steps in QTS that free those ports and what each breaks; WebPortico never changes QTS’s settings itself.

On QuTS hero, a shared folder with Advanced Folder Permissions cannot hold sites: the apply stops, names the folder and asks again. WebPortico 0.15.0 was tried on QTS 6.1.0 and QuTS hero 6.1.0.

Download

Package name WebPortico. SHA-256 of 0.36.0: 63c8eb9e4c98cc01b5d8a7b46e6ee7395fadf0ca9c780768f829df13d51c8f7d (.sha256). WebPortico is made with Bucket & Code Server IDE. Its own code (the panel, webctl and the scripts) is freeware under the Bucket & Code Server IDE Freeware Licence 1.0, in the package as share/licenses/webportico/LICENSE; it packs the programs of their own developers, each under its own license: nginx (BSD-2-Clause), Apache httpd (Apache-2.0), PHP (PHP-3.01), MariaDB (GPL-2.0-only), Percona Server (GPL-2.0-only), PostgreSQL (PostgreSQL), memcached (BSD-3-Clause), Valkey (BSD-3-Clause), FFmpeg (LGPL-2.1-or-later), ImageMagick (ImageMagick), libheif (LGPL-3.0-or-later), libde265 (LGPL-3.0-or-later), libaom (BSD-2-Clause), imagick (PHP-3.01), lego (MIT), cloudflared (Apache-2.0), Node.js (MIT and others), Grafana (AGPL-3.0-only), OpenSearch (Apache-2.0), BusyBox (GPL-2.0-only), OpenSSL (Apache-2.0), SQLite (public domain) and further libraries. The recipe of each part in the App Builder names its license and its source archive. Links: nginx · Apache httpd · PHP · MariaDB · Percona Server · PostgreSQL · Valkey · FFmpeg · lego · cloudflared.

Rtorrent 16 Sonarr · TV series

Sonarr follows the series you add. It reads your indexers’ feeds for new episodes, picks the release that fits the quality profile you set, sends it to a download client and moves the finished file into the series folder under the name you chose. It lists the episodes your library lacks and searches for them, and replaces a file when a better quality comes out.

Rtorrent 16's Connect another app card: the host, port, URL path and user Sonarr enters for its rTorrent download client

With the other apps on the NAS

Indexers come from Prowlarr, which adds them to Sonarr once Sonarr is one of its apps. Downloads go to Rtorrent 16 or another client: in Sonarr, Settings → Download Clients → rTorrent, with the host, port, URL Path (RPC2) and user that Rtorrent 16’s panel lists under Settings → Media servers → Connect another app. Unpackerr extracts releases that arrive as archives, Recyclarr keeps the quality settings in step with the TRaSH guides, Bazarr fetches subtitles, and Seerr passes on the series people ask for.

First start

App Center’s Open leads to http://<NAS>:8989/, Sonarr’s own port. At the first visit Sonarr asks for an authentication method, a user name and a password, and keeps them in its own database; the package sets no password. Sonarr runs as the account sonarr in the group arr, which needs read and write access to the series folders and to the folder where downloads finish.

The package

Sonarr 4.0.20.3014 as its developers release it for Linux, with the .NET runtime inside their build. The package adds ICU, which QTS lacks, so that release names with accented letters, such as Pokémon or ŻYWIOŁAK, match their series. OpenSSL, zlib and SQLite are our own builds, the C++ runtime is Ubuntu 24.04’s, and from QTS the app loads nothing but glibc. Settings, the API key, the database, logs and backups are in <install volume>/Sonarr, for example /share/CACHEDEV1_DATA/Sonarr, which an upgrade or a removal leaves in place. Sonarr’s own updater is off: a new version comes as a new package in App Center.

A little history

Sonarr was called NzbDrone until 21 October 2014, when its developers announced the new name on their forum: picked from more than 800 suggestions, and taken from sonar. They had asked for a name “with a bit less nzb”, since torrent support had arrived. The source still names its projects NzbDrone.Core, NzbDrone.Common and so on, and Radarr, Lidarr and Prowlarr, built on the same code, carry those names too.

Installation

Recommended — from App Center. Add this site’s repository once; after that the package installs and updates from App Center like any other app.

  1. App Center → ⚙ Settings → App Repository → Add.
  2. Name it QNAP Utilities, paste https://www.qnaputilities.com/repo.xml, Add.
  3. Open QNAP Utilities in the left rail and install Rtorrent 16 Sonarr.

The repository panel: every package in the feed →

By hand instead: take the build below, then App Center → Install Manually.

What it needs

A QNAP NAS with an x86_64 processor (Intel or AMD) on QTS 6.0 or QuTS hero 6.0 or newer.

Download

Package name Sonarr, Sonarr 4.0.20.3014. SHA-256 of 4.0.20.3: cfcca2ffd37ddbbe55f119c0028d673cd11e5c322f4dff20209e36843c0d4b0c (.sha256). Sonarr is by Sonarr’s developers, GPL-3.0; packed here, not written here. The package also carries the .NET runtime of their build (MIT), ICU (Unicode-3.0), OpenSSL (Apache-2.0), zlib (Zlib), SQLite (public domain), the C++ runtime (GPL-3.0 with the GCC Runtime Library Exception) and BusyBox (GPL-2.0); share/licenses/NOTICE in the install folder names each part with its licence and source. Upstream: sonarr.tv · source · release notes · wiki.

Rtorrent 16 Sonarr 4K · TV series in 4K

Sonarr 4K is a second Sonarr on the same NAS, beside Rtorrent 16 Sonarr, for the 4K copies of your series. Sonarr keeps one file per episode, so a library that holds a 1080p and a 4K copy of a series needs two Sonarr instances: Rtorrent 16 Sonarr follows the 1080p copies and Sonarr 4K the 4K ones, each with its own quality profile, root folders and list.

Sonarr 4K: the library as a table, each title with the 4K quality profile Sonarr 4K: the 4K quality profile, upgraded until Bluray-2160p Sonarr 4K: the quality profiles, 4K first

With Seerr and Rtorrent 16

In Seerr, Settings → Services → Add Sonarr Server with the port 8990 and 4K Server and Default 4K Server ticked. Seerr then offers Request in 4K beside Request, sends those requests here and shows a title’s 4K status apart from its 1080p one. Downloads go to Rtorrent 16: in Sonarr 4K, Settings → Download Clients → rTorrent, with the fields of Rtorrent 16’s Connect another app card and the category sonarr4k. Movie Agent files each finished download; a Rtorrent 16 that knows Sonarr 4K (16.27-10Q and newer) also tells it where the series went. Indexers come from Prowlarr once Sonarr 4K is one of its apps.

First start

App Center’s Open leads to http://<NAS>:8990/. Before Sonarr’s first start the package writes that port and the name Sonarr 4K into its settings, since Sonarr’s own port 8989 belongs to Rtorrent 16 Sonarr. At the first visit Sonarr asks for an authentication method, a user name and a password, and keeps them in its own database; the package sets no password. Sonarr 4K runs as the account sonarr4k in the group arr, which needs read and write access to the 4K folders and to the folder where downloads finish.

The package

The same Sonarr 4.0.20.3014, runtime and libraries as Rtorrent 16 Sonarr 4.0.20.3: Sonarr as its developers release it for Linux, with the .NET runtime inside their build and ICU added by the package. OpenSSL, zlib and SQLite are our own builds, the C++ runtime is Ubuntu 24.04’s, and from QTS the app loads nothing but glibc. Settings, the API key, the database, logs and backups are in <install volume>/Sonarr4K, which an upgrade or a removal leaves in place. Sonarr’s own updater is off: a new version comes as a new package in App Center.

Installation

Recommended — from App Center. Add this site’s repository once; after that the package installs and updates from App Center like any other app.

  1. App Center → ⚙ Settings → App Repository → Add.
  2. Name it QNAP Utilities, paste https://www.qnaputilities.com/repo.xml, Add.
  3. Open QNAP Utilities in the left rail and install Rtorrent 16 Sonarr 4K.

The repository panel: every package in the feed →

By hand instead: take the build below, then App Center → Install Manually.

What it needs

A QNAP NAS with an x86_64 processor (Intel or AMD) on QTS 6.0 or QuTS hero 6.0 or newer.

Download

Package name Sonarr4K, Sonarr 4.0.20.3014. SHA-256 of 4.0.20.3: b10c0448a9aaabd0e63615f09e2a6dfa68e7b2197d96b67ded6324cc15287429 (.sha256). Sonarr is by Sonarr’s developers, GPL-3.0; packed here, not written here. The package also carries the .NET runtime of their build (MIT), ICU (Unicode-3.0), OpenSSL (Apache-2.0), zlib (Zlib), SQLite (public domain), the C++ runtime (GPL-3.0 with the GCC Runtime Library Exception) and BusyBox (GPL-2.0); share/licenses/NOTICE in the install folder names each part with its licence and source. Upstream: sonarr.tv · source · release notes · wiki.

Rtorrent 16 Radarr · films

Radarr does for films what Sonarr does for series. It watches your indexers for the films you add, picks the release that fits your quality profile, sends it to a download client and moves the finished file into the film’s folder under the name you chose, and it replaces a file when a better quality comes out. It keeps one file per film: a 4K copy and a 1080p copy of the same film take two Radarr instances. This package runs one, Rtorrent 16 Radarr 4K the second.

Radarr's download client form, filled in for Rtorrent 16 Radarr's root folders: the film folders of the library

With the other apps on the NAS

Indexers come from Prowlarr, which adds them to Radarr once Radarr is one of its apps. Downloads go to Rtorrent 16 or another client: in Radarr, Settings → Download Clients → rTorrent, with the host, port, URL Path (RPC2) and user that Rtorrent 16’s panel lists under Settings → Media servers → Connect another app. Unpackerr extracts releases that arrive as archives, Recyclarr keeps the quality settings in step with the TRaSH guides, Bazarr fetches subtitles, and Seerr passes on the films people ask for.

First start

App Center’s Open leads to http://<NAS>:7878/, Radarr’s own port. At the first visit Radarr asks for an authentication method, a user name and a password, and keeps them in its own database; the package sets no password. Radarr runs as the account radarr in the group arr, which needs read and write access to the film folders and to the folder where downloads finish.

The package

Radarr 6.4.4.10685 as its developers release it for Linux, with the .NET runtime inside their build. The package adds ICU, the Unicode library .NET uses on Linux, which QTS lacks. OpenSSL and zlib are our own builds, the C++ runtime is Ubuntu 24.04’s, SQLite comes inside Radarr’s own build, and from QTS the app loads nothing but glibc. Settings, the API key, the database, logs and backups are in <install volume>/Radarr, which an upgrade or a removal leaves in place. Radarr’s own updater is off: a new version comes as a new package in App Center.

A little history

Radarr is a fork of Sonarr, and its source still carries Sonarr’s NzbDrone project names. That is also why it keeps every film in a folder of its own, as Sonarr keeps a series: Radarr’s FAQ calls a flat folder of films highly unlikely ever to be supported, for the changes it would take in the code.

Installation

Recommended — from App Center. Add this site’s repository once; after that the package installs and updates from App Center like any other app.

  1. App Center → ⚙ Settings → App Repository → Add.
  2. Name it QNAP Utilities, paste https://www.qnaputilities.com/repo.xml, Add.
  3. Open QNAP Utilities in the left rail and install Rtorrent 16 Radarr.

The repository panel: every package in the feed →

By hand instead: take the build below, then App Center → Install Manually.

What it needs

A QNAP NAS with an x86_64 processor (Intel or AMD) on QTS 6.0 or QuTS hero 6.0 or newer.

Download

Package name Radarr, Radarr 6.4.4.10685. SHA-256 of 6.4.4.3: 36c577a9af92ef089cd8fb8447f0ac3b014637538f5eba6948e6519d0179c037 (.sha256). Radarr is by Radarr’s developers, GPL-3.0; packed here, not written here. The package also carries the .NET runtime of their build (MIT), ICU (Unicode-3.0), OpenSSL (Apache-2.0), zlib (Zlib), the C++ runtime (GPL-3.0 with the GCC Runtime Library Exception) and BusyBox (GPL-2.0); share/licenses/NOTICE in the install folder names each part with its licence and source. Upstream: radarr.video · source · release notes · wiki.

Rtorrent 16 Radarr 4K · films in 4K

Radarr 4K is a second Radarr on the same NAS, beside Rtorrent 16 Radarr, for the 4K copies of your films. Radarr keeps one file per film, so a library that holds a 1080p and a 4K copy of a film needs two Radarr instances: Rtorrent 16 Radarr follows the 1080p copies and Radarr 4K the 4K ones, each with its own quality profile, root folders and list.

Radarr 4K: the library as a table, each title with the 4K quality profile Radarr 4K: the 4K quality profile, upgraded until Bluray-2160p Radarr 4K: the quality profiles, 4K first

With Seerr and Rtorrent 16

In Seerr, Settings → Services → Add Radarr Server with the port 7879 and 4K Server and Default 4K Server ticked. Seerr then offers Request in 4K beside Request, sends those requests here and shows a title’s 4K status apart from its 1080p one. Downloads go to Rtorrent 16: in Radarr 4K, Settings → Download Clients → rTorrent, with the fields of Rtorrent 16’s Connect another app card and the category radarr4k. Movie Agent files each finished download; a Rtorrent 16 that knows Radarr 4K (16.27-10Q and newer) also tells it where the film went. Indexers come from Prowlarr once Radarr 4K is one of its apps.

First start

App Center’s Open leads to http://<NAS>:7879/. Before Radarr’s first start the package writes that port and the name Radarr 4K into its settings, since Radarr’s own port 7878 belongs to Rtorrent 16 Radarr. At the first visit Radarr asks for an authentication method, a user name and a password, and keeps them in its own database; the package sets no password. Radarr 4K runs as the account radarr4k in the group arr, which needs read and write access to the 4K folders and to the folder where downloads finish.

The package

The same Radarr 6.4.4.10685, runtime and libraries as Rtorrent 16 Radarr 6.4.4.3: Radarr as its developers release it for Linux, with the .NET runtime inside their build and ICU added by the package. OpenSSL and zlib are our own builds, the C++ runtime is Ubuntu 24.04’s, SQLite comes inside Radarr’s own build, and from QTS the app loads nothing but glibc. Settings, the API key, the database, logs and backups are in <install volume>/Radarr4K, which an upgrade or a removal leaves in place. Radarr’s own updater is off: a new version comes as a new package in App Center.

Installation

Recommended — from App Center. Add this site’s repository once; after that the package installs and updates from App Center like any other app.

  1. App Center → ⚙ Settings → App Repository → Add.
  2. Name it QNAP Utilities, paste https://www.qnaputilities.com/repo.xml, Add.
  3. Open QNAP Utilities in the left rail and install Rtorrent 16 Radarr 4K.

The repository panel: every package in the feed →

By hand instead: take the build below, then App Center → Install Manually.

What it needs

A QNAP NAS with an x86_64 processor (Intel or AMD) on QTS 6.0 or QuTS hero 6.0 or newer.

Download

Package name Radarr4K, Radarr 6.4.4.10685. SHA-256 of 6.4.4.3: b993f2a8f205b96e448ad4b9d417ba975610fad4e90072c3cc385d3a71191a6f (.sha256). Radarr is by Radarr’s developers, GPL-3.0; packed here, not written here. The package also carries the .NET runtime of their build (MIT), ICU (Unicode-3.0), OpenSSL (Apache-2.0), zlib (Zlib), the C++ runtime (GPL-3.0 with the GCC Runtime Library Exception) and BusyBox (GPL-2.0); share/licenses/NOTICE in the install folder names each part with its licence and source. Upstream: radarr.video · source · release notes · wiki.

Lidarr · music

Lidarr follows artists. It watches your indexers for the albums of the artists you add, sends the release that fits your quality profile to a download client and files the finished tracks into your music folders under the names you chose, and it replaces files when a better quality comes out. It finds artists and albums through MusicBrainz, and knows only the artists MusicBrainz knows.

With the other apps on the NAS

Indexers come from Prowlarr, which adds them to Lidarr once Lidarr is one of its apps. Downloads go to Rtorrent 16 or another client: in Lidarr, Settings → Download Clients → rTorrent, with the host, port, URL Path (RPC2) and user that Rtorrent 16’s panel lists under Settings → Media servers → Connect another app. Unpackerr extracts releases that arrive as archives.

First start

App Center’s Open leads to http://<NAS>:8686/, Lidarr’s own port. At the first visit Lidarr asks for an authentication method, a user name and a password, and keeps them in its own database; the package sets no password. Lidarr runs as the account lidarr in the group arr, which needs read and write access to the music folders and to the folder where downloads finish.

The package

Lidarr 3.1.0.4875 as its developers release it for Linux, with the .NET runtime inside their build. The package adds ICU, the Unicode library .NET uses on Linux, which QTS lacks. OpenSSL and zlib are our own builds, the C++ runtime is Ubuntu 24.04’s, SQLite comes inside Lidarr’s own build, and from QTS the app loads nothing but glibc. Settings, the API key, the database, logs and backups are in <install volume>/Lidarr, which an upgrade or a removal leaves in place. Lidarr’s own updater is off: a new version comes as a new package in App Center.

A little history

Lidarr describes itself on GitHub as “looks and smells like Sonarr but made for music”. It is built on Sonarr’s code, and its source carries the same NzbDrone project names.

Installation

Recommended — from App Center. Add this site’s repository once; after that the package installs and updates from App Center like any other app.

  1. App Center → ⚙ Settings → App Repository → Add.
  2. Name it QNAP Utilities, paste https://www.qnaputilities.com/repo.xml, Add.
  3. Open QNAP Utilities in the left rail and install Lidarr.

The repository panel: every package in the feed →

By hand instead: take the build below, then App Center → Install Manually.

What it needs

A QNAP NAS with an x86_64 processor (Intel or AMD) on QTS 6.0 or QuTS hero 6.0 or newer.

Download

Package name Lidarr. SHA-256 of 3.1.6.5079: 89b2d96585f7df8259a49b267ee124f16a8a0a0edf94a8a144d86e21a24ecf9b (.sha256). Lidarr is by Lidarr’s developers, GPL-3.0; packed here, not written here. The package also carries the .NET runtime of their build (MIT), ICU (Unicode-3.0), OpenSSL (Apache-2.0), zlib (Zlib), the C++ runtime (GPL-3.0 with the GCC Runtime Library Exception) and BusyBox (GPL-2.0); share/licenses/NOTICE in the install folder names each part with its licence and source. Upstream: lidarr.audio · source · release notes · wiki.

Bazarr · subtitles

Bazarr finds and downloads subtitles for the series of Sonarr and the films of Radarr, in the languages you choose for each, and keeps them next to the video files. It searches again for the ones still missing and replaces a subtitle when a better one turns up. It does not scan the disk: it manages only what Sonarr and Radarr have in their libraries.

Bazarr: a series' episodes with their existing and missing subtitles

Screenshot: Bazarr

With the other apps on the NAS

In Bazarr, Settings → Sonarr and Settings → Radarr, with each app’s address (localhost and port 8989 or 7878 on the same NAS) and API key from its Settings → General. Bazarr runs as the account bazarr in the group arr: it writes the subtitles into the media folders, so it needs write access there, and it can change the files Sonarr and Radarr write.

First start

App Center’s Open leads to http://<NAS>:6767/, Bazarr’s own port. Bazarr opens without a sign-in: set one under Settings → General → Security. The package sets no password.

The package

Bazarr 1.6.2 as its developers release it, run on the Python 3.13 the package carries, with the compiled modules it needs (lxml, numpy, Pillow, webrtcvad) from PyPI. Python carries its own OpenSSL; the zlib and C++ runtime that numpy and Pillow need are in the package, zlib of our own build and the C++ runtime Ubuntu 24.04’s, and from QTS Bazarr loads nothing but glibc. Two programs come with it: 7-Zip, for subtitles packed as RAR, and FFmpeg’s ffprobe, built here, which Bazarr uses to read the subtitle tracks inside the video files. Its log shows one error at every start, about an unrar it cannot download into the package’s folder; it then uses 7-Zip. Settings, the API key, the database, logs and backups are in <install volume>/Bazarr, which an upgrade or a removal leaves in place. Bazarr’s own updater is off: a new version comes as a new package in App Center.

A little history

Bazarr has been on GitHub since April 2017, and its README describes its interface as based on Sonarr’s.

Installation

Recommended — from App Center. Add this site’s repository once; after that the package installs and updates from App Center like any other app.

  1. App Center → ⚙ Settings → App Repository → Add.
  2. Name it QNAP Utilities, paste https://www.qnaputilities.com/repo.xml, Add.
  3. Open QNAP Utilities in the left rail and install Bazarr.

The repository panel: every package in the feed →

By hand instead: take the build below, then App Center → Install Manually.

What it needs

A QNAP NAS with an x86_64 processor (Intel or AMD) on QTS 6.0 or QuTS hero 6.0 or newer, and Sonarr or Radarr.

Download

Package name Bazarr. SHA-256 of 1.6.2.3: 5846551aa36909028d0cfd8b3c7f6fe1cc32e0588e7f76c2b972db1e0266f821 (.sha256). Bazarr is by Bazarr’s developers, GPL-3.0; packed here, not written here. The package also carries Python (PSF-2.0), 7-Zip (LGPL-2.1, with the unRAR restriction), FFmpeg’s ffprobe (LGPL-2.1), zlib (Zlib), the C++ runtime (GPL-3.0 with the GCC Runtime Library Exception), BusyBox (GPL-2.0) and the Python modules Bazarr depends on, each under its own licence; share/licenses/NOTICE in the install folder names each part with its licence and source. Upstream: bazarr.media · source · release notes · wiki.

Rtorrent 16 Prowlarr · indexers

Prowlarr keeps your indexers, Usenet indexers and torrent trackers alike, in one place and gives them to Sonarr, Radarr and Lidarr: an indexer added in Prowlarr appears in every app it syncs to, so none is set up twice. It also searches the indexers itself and can send a release straight to a download client.

Prowlarr adds Radarr as an app: the two server addresses and Radarr's API key Prowlarr's sync level for an app: full sync keeps its indexers in step

With the other apps on the NAS

In Prowlarr, Settings → Apps → + → Sonarr, Radarr or Lidarr, with the app’s API key from its Settings → General. On one NAS the suggested addresses are right (http://localhost:9696 for Prowlarr, http://localhost:8989 for Sonarr). Prowlarr saves an app only after it has reached it with that key, and from then on keeps the app’s indexer list in step with its own.

First start

App Center’s Open leads to http://<NAS>:9696/, Prowlarr’s own port. At the first visit Prowlarr asks for an authentication method, a user name and a password, and keeps them in its own database; the package sets no password. Prowlarr runs as the account prowlarr in the group arr.

The package

Prowlarr 2.6.5.5623 as its developers release it for Linux, with the .NET runtime inside their build. The package adds ICU, the Unicode library .NET uses on Linux, which QTS lacks. OpenSSL and zlib are our own builds, the C++ runtime is Ubuntu 24.04’s, SQLite comes inside Prowlarr’s own build, and from QTS the app loads nothing but glibc. Settings, the API key, the database, logs and backups are in <install volume>/Prowlarr, which an upgrade or a removal leaves in place. Prowlarr’s own updater is off: a new version comes as a new package in App Center.

A little history

Prowlarr is built on the same code as Sonarr and Radarr. Its tracker definitions are Cardigann YML files, which a script in Prowlarr’s Indexers repository syncs every day from Jackett’s definitions, with some differences; Prowlarr’s README counts over 500 trackers.

Installation

Recommended — from App Center. Add this site’s repository once; after that the package installs and updates from App Center like any other app.

  1. App Center → ⚙ Settings → App Repository → Add.
  2. Name it QNAP Utilities, paste https://www.qnaputilities.com/repo.xml, Add.
  3. Open QNAP Utilities in the left rail and install Rtorrent 16 Prowlarr.

The repository panel: every package in the feed →

By hand instead: take the build below, then App Center → Install Manually.

What it needs

A QNAP NAS with an x86_64 processor (Intel or AMD) on QTS 6.0 or QuTS hero 6.0 or newer.

Download

Package name Prowlarr. SHA-256 of 2.7.0.5723: 4967667c3242178b717cabed72fe9384fc5686021a67e087bf4e10ffbaf19333 (.sha256). Prowlarr is by Prowlarr’s developers, GPL-3.0; packed here, not written here. The package also carries the .NET runtime of their build (MIT), ICU (Unicode-3.0), OpenSSL (Apache-2.0), zlib (Zlib), the C++ runtime (GPL-3.0 with the GCC Runtime Library Exception) and BusyBox (GPL-2.0); share/licenses/NOTICE in the install folder names each part with its licence and source. Upstream: prowlarr.com · source · release notes · wiki.

Unpackerr · extraction

A release that arrives as RAR, 7z, zip or tar archives stays in the queue of Sonarr, Radarr or Lidarr: they import files, not archives. Unpackerr reads their download queues, extracts each finished download that holds archives so the app can import it, and removes what it extracted once the import is done. Its web page, on port 5656, shows the queue, the history and the logs and holds its settings.

First start

App Center’s Open leads to http://<NAS>:5656/, Unpackerr’s own port. The first start sets a password for the user admin, and the package copies it to QTS’s System Logs as a warning. Sign in with it and change it under Settings → Web server. Then add Sonarr, Radarr and Lidarr under Settings with each app’s address (http://127.0.0.1:8989 for Sonarr on the same NAS) and its API key from its Settings → General; each row has a Test button. Unpackerr keeps its settings in unpackerr.conf in its data folder, <install volume>/Unpackerr (for example /share/CACHEDEV1_DATA/Unpackerr); the file holds the API keys, so only its account may read it.

With the other apps on the NAS

Unpackerr serves Sonarr, Radarr and Lidarr through their APIs, so the download client makes no difference. It runs as the account unpackerr, which needs write access to the folder where downloads finish. It is in the group arr with the apps, and all of them write files their group may change, so the apps can work with what it extracts.

The package

Unpackerr 1.0.1 as its developers release it for Linux: one static program, with no runtime beside it. Its data folder, which an upgrade or a removal leaves in place, holds unpackerr.conf and service.log.

A little history

Unpackerr’s first releases, from 2018, went by the names deluge-unpacker and unpacker-poller and read the transfer list of Deluge. Today it asks the *arr apps instead.

Installation

Recommended — from App Center. Add this site’s repository once; after that the package installs and updates from App Center like any other app.

  1. App Center → ⚙ Settings → App Repository → Add.
  2. Name it QNAP Utilities, paste https://www.qnaputilities.com/repo.xml, Add.
  3. Open QNAP Utilities in the left rail and install Unpackerr.

The repository panel: every package in the feed →

By hand instead: take the build below, then App Center → Install Manually.

What it needs

A QNAP NAS with an x86_64 processor (Intel or AMD) on QTS 6.0 or QuTS hero 6.0 or newer, and Sonarr, Radarr or Lidarr to serve.

Download

Package name Unpackerr. SHA-256 of 1.0.1: f7ceedfbf2cc933814baef4bb795cee1b413e62e4d6e5ec3aa03e00764a752e5 (.sha256). Unpackerr is by Unpackerr’s developers, MIT; packed here, not written here. The package also carries BusyBox (GPL-2.0); share/licenses/NOTICE in the install folder names each part with its licence and source. Upstream: unpackerr.zip · source · release notes · docs.

Recyclarr · TRaSH guides

The TRaSH guides publish recommended quality definitions, quality profiles, custom formats and naming for Sonarr and Radarr. Recyclarr writes the parts you choose into your Sonarr and Radarr through their APIs, from one YAML file, and keeps them in step when the guides change. This package runs it once a day, at 05:41, from QTS’s crontab. It has no web page and listens on no port.

Its settings: recyclarr.yml

The first start runs recyclarr config create, which fetches the guides and writes a starter recyclarr.yml into the data folder, <install volume>/Recyclarr (for example /share/CACHEDEV1_DATA/Recyclarr); until the file is filled in, the daily sync ends with an error in service.log beside it. Over SSH as admin, give each instance its base_url (http://localhost:8989 for Sonarr on the same NAS) and api_key (the app’s Settings → General), and choose the guide’s templates, which recyclarr.dev describes. Then run /etc/init.d/Recyclarr.sh sync once and read the result in service.log.

With the other apps on the NAS

Recyclarr changes the settings of Sonarr (version 4 or newer) and Radarr, and nothing else. It runs as the account recyclarr; stopping the package takes its line out of the crontab, and starting it puts the line back.

The package

Recyclarr 8.8.1 as its developers release it for Linux: one program with the .NET runtime inside. It fetches the guides with git, which QTS lacks, so the package carries git from GitHub Desktop’s portable build. git’s HTTPS helper runs on our own builds of curl, OpenSSL, zlib, zstd, nghttp2 and c-ares, the program on Ubuntu 24.04’s C++ runtime, and from QTS nothing but glibc is loaded. The data folder, which an upgrade or a removal leaves in place, holds recyclarr.yml, the copy of the guides and the logs.

A little history

Recyclarr began as Trash Updater: its GitHub repository was rcdailey/trash-updater, an address GitHub still forwards. Version 1.0, of 14 April 2021, was a full rewrite in C# of what had been a Python script.

Installation

Recommended — from App Center. Add this site’s repository once; after that the package installs and updates from App Center like any other app.

  1. App Center → ⚙ Settings → App Repository → Add.
  2. Name it QNAP Utilities, paste https://www.qnaputilities.com/repo.xml, Add.
  3. Open QNAP Utilities in the left rail and install Recyclarr.

The repository panel: every package in the feed →

By hand instead: take the build below, then App Center → Install Manually.

What it needs

A QNAP NAS with an x86_64 processor (Intel or AMD) on QTS 6.0 or QuTS hero 6.0 or newer, Sonarr or Radarr to set up, and access to GitHub, where the guides are.

Download

Package name Recyclarr. SHA-256 of 8.8.1: c4e2b56fd934644384a63ad6d10c52974cea34f53999e9f794f0b1629f4a97e2 (.sha256). Recyclarr is by Recyclarr’s developers, MIT; packed here, not written here. The package also carries the .NET runtime of their build (MIT), git (GPL-2.0), curl (curl), OpenSSL (Apache-2.0), zlib (Zlib), zstd (BSD-3-Clause), nghttp2 and c-ares (MIT), the C++ runtime (GPL-3.0 with the GCC Runtime Library Exception) and BusyBox (GPL-2.0); share/licenses/NOTICE in the install folder names each part with its licence and source. Upstream: recyclarr.dev · source · release notes · TRaSH guides.

WhatsApp notifications

Three steps. Open Notifications in the Control Center → press pair → send the eight-character code to the bot from your phone. That is the whole setup.

The Notifications page in the Control Center with the WhatsApp pairing card

The pairing card sits at the top of Notifications, with a QR code for the phone.

Notification types

Download finished, download failed, disk space low, the package started or stopped, a certificate renewed or about to expire, and anything else you switch on. Each event can go to WhatsApp, to another service, or to both.

Whose number, whose data

The NAS holds a token. The service holds your number against that token and nothing else — no message history, no torrent names beyond the one being delivered. Sending STOP to the bot deletes the pairing at once, and so does unpairing from the panel.

The token is deliberately weak: it can ask for a pairing code, and it can send a message to the number that paired with it — it cannot name a recipient, so it can never reach anyone else's phone. No Meta credential is in the package or on the NAS; those stay on the service. That is why the package can be handed to anyone: every install pairs itself, and holds nothing that would let it bother a stranger.

The 24-hour rule, and what it costs

Meta allows a business number to send freely for 24 hours after the person writes to it, and only pre-approved template messages outside that window. Only you can open or reset that timer — nothing the NAS sends extends it. In practice: write to the bot, and for the next day everything arrives as an ordinary message.

Worth knowing before you build a habit on it: user-initiated service messages have been free since November 2024, and Meta's own pricing page says charging returns on 1 October 2026, per message. The add-on below, which uses your own WhatsApp account instead of Meta's API, is not affected by that.

QTS itself, on the same route

Control Panel → Notification Center → Service Account and Device Pairing → SMS → add an SMSC service → Custom, and paste the URL the panel gives you. Every QTS notification that would have been a text message arrives on WhatsApp instead — disk failures, RAID rebuilds, firmware updates, the lot.

The bot, and its own page

The number is +48 690 760 663 — run by QNAP Club Polska. It is a WhatsApp Business number, so it will not show up in your contacts: the panel gives you a link that opens the chat. Its page explains the pairing, what a token can and cannot do, the QTS trick and what is stored.

The bot's page · po polsku · Privacy · Terms · Delete my data

The other notification services

Rtorrent 16 sends through shoutrrr, so a destination is one URL. Paste it, press test, and the message arrives while you are still looking at the page.

Every destination has its own event list, so the phone can get "download finished" while a webhook gets everything.

Bucket & Code Server IDE

Everything it does, in the panel’s own windows: the Bucket & Code Server IDE page → · the user guide, in nine languages → · first steps, from App Center to a first app →

Bucket & Code Server IDE: the overview of the modules VS Code in the browser, running on the NAS Git repositories in Forgejo The App Builder: how a program is linked into a QPKG

The developer workshop for a QNAP NAS: Git with Forgejo (issues, pull requests, releases, LFS), a CI runner on the NAS, Subversion and versioned WebDAV buckets, VS Code in the browser for every developer, an App Builder that compiles programs from 561 recipes into apps and QPKGs (four link modes, an ELF analyzer with one-click fixes), a kernel workshop for modules of the running kernel, a project wizard and a Project view (build, test deploy, publish, versions), your own App Center repository, publishing on your own domain through a Cloudflare Tunnel, daily backups, 72 examples, a user guide and panel in nine languages.

Installation

Recommended — from App Center. Add this site’s repository once; after that the package installs and updates from App Center like any other app.

  1. App Center → ⚙ Settings → App Repository → Add.
  2. Name it QNAP Utilities, paste https://www.qnaputilities.com/repo.xml, Add.
  3. Open QNAP Utilities in the left rail and install Bucket & Code Server IDE.

The repository panel: every package in the feed →

By hand instead: take the build below, then App Center → Install Manually.

What it needs

A QNAP NAS with an x86_64 processor (Intel or AMD) on QTS 6.0 or QuTS hero 6.0 or newer. Its panel opens on port 9950 (HTTP) and 9951 (HTTPS), and the first sign-in sets the administrator’s password.

Download

Package name bucketvs. SHA-256 of 1.0.0-83: b66a17d9f020eda270d715d4ed566d43af106842ab8795034be508c7f9c34c6c (.sha256). In this site’s App Center feed under Developer Tools, so App Center installs and updates it; the link above is the same file.

Example packages

Packages made with the Bucket & Code Server IDE’s App Builder: recipes compiled from source into a prefix and exported as QPKGs. Each is also one of the panel’s Editor projects, so you can open it in the editor, change its recipe list and build your own.

From App Center

They are in this site’s App Center feed, each under its own name. Add the repository once (the repository panel) and they install and update like any other app.

How to start with TurboDNS: Your domain on your NAS: website, DNS and mail from the first day →

Product pages: TurboShell → · TurboStat → · TurboX →

Download

Package names TurboDNS, TurboShell, TurboStat and TurboX. The programs of TurboShell, TurboStat and TurboX are on the PATH of an SSH login on the NAS. QTS 6.0 or QuTS hero 6.0 or newer, x86_64.

Roland Aira P-6 SoundBridge

A web app the NAS serves for the owner of a Roland AIRA P-6: browse sound banks kept on any share, audition and edit samples (trim, fades, pitch, bar-fit), arrange the 8 banks × 6 pads, and write the result as IMPORT/BANK_x/PAD_n, each WAV with its pad settings file (PRM), straight onto the P-6’s USB drive from the browser. A drawn P-6 panel with a step sequencer floats over the app; rhythms cut from Ableton projects go to the unit as ready patterns (RESTORE); a chop pad holds several sounds on one pad, one per key from C4.

SoundBridge: the sample editor, the step sequencer and the P-6's six pads

Sound banks

No banks ship with the package. Drop .m3u sound banks into an Aira folder on any share (Public, Web…) and the app finds them. Ready-made banks: the Internet Archive, user Rtorrent16.

What it needs

A QNAP NAS on QTS 5.2 or QuTS hero, x86_64 or arm_64; the app opens on https port 6061. Free and open source; not affiliated with Roland. QNAP is a trademark of QNAP Systems, Inc.

Download

Package name AiraP6SoundBridge. In this site’s App Center feed under Entertainment, so App Center installs and updates it; the links above are the same files.

SoundComposer for Roland AIRA Compact

A web app the NAS serves for the Roland AIRA Compact S-1 and T-8, the sibling of SoundBridge. Pick a pattern from the library and play it, edit it on the piano roll or the drum grid, choose an S-1 or T-8 sound, and let the app prepare the PRM and ZIP files that the device loads through USB RESTORE. Connected over Web MIDI, it plays the notes on the device; saving a pattern on the device itself still goes through RESTORE or the device’s own REC. Polish and English.

SoundComposer: the pattern library and the piano roll of a bass part

What it needs

A QNAP NAS with an x86_64 CPU on QTS 5.0 or later, or QuTS hero. The app opens at https://<NAS>:8766/ with the certificate QTS itself uses (a Let’s Encrypt one when QTS has it), which is what Web MIDI needs; plain http://<NAS>:8765/ plays and prepares files but has no Web MIDI. It has no sign-in of its own, so keep both ports on your local network. Free of charge. Not affiliated with Roland. QNAP is a trademark of QNAP Systems, Inc.

Download

Package name SoundComposer. In this site’s App Center feed under Entertainment, so App Center installs and updates it; the link above is the same file.

Rtorrent 16 Seerr · media requests

Seerr lets the people who use your Plex, Jellyfin or Emby server ask for films and series, on a web page that also works on a phone. A request you approve, or one from a user whose requests you let through, goes to Radarr for a film and to Sonarr for a series; Seerr scans the media server’s libraries, so it shows what is already there.

Seerr's first start: choose Jellyfin, Plex or Emby Seerr's Radarr server settings

With the other apps on the NAS

Seerr hands requests to Radarr and Sonarr, each with its address (http://localhost:7878 and http://localhost:8989 on the same NAS) and API key from its Settings → General. The media server can run on this NAS or on another machine Seerr can reach.

First start

App Center’s Open leads to http://<NAS>:5055/, Seerr’s own port, which the package gives it. Seerr’s setup asks you to sign in with your Plex, Jellyfin or Emby account and to connect the media server, Radarr and Sonarr; the package sets no password.

The package

Seerr 3.5.0, built by the package from the source of its release, since Seerr’s developers publish container images only, and run on the Node.js 22 the package carries. Node.js has its own OpenSSL and zlib built in, the C++ runtime beside it is Ubuntu 24.04’s, and from QTS Seerr loads nothing but glibc. It runs as the account seerr; settings, the API key, the database and logs are in the data folder, which an upgrade or a removal leaves in place. A new version comes as a new package in App Center.

A little history

On 10 February 2026 the Overseerr and Jellyseerr teams announced that they were merging into one team, Seerr, with one code base: Overseerr had served Plex, Jellyseerr had added Jellyfin and Emby, and Seerr carries both.

Installation

Recommended — from App Center. Add this site’s repository once; after that the package installs and updates from App Center like any other app.

  1. App Center → ⚙ Settings → App Repository → Add.
  2. Name it QNAP Utilities, paste https://www.qnaputilities.com/repo.xml, Add.
  3. Open QNAP Utilities in the left rail and install Rtorrent 16 Seerr.

The repository panel: every package in the feed →

By hand instead: take the build below, then App Center → Install Manually.

What it needs

A QNAP NAS with an x86_64 processor (Intel or AMD) on QTS 6.0 or QuTS hero 6.0 or newer, and a Plex, Jellyfin or Emby server.

Download

Package name Seerr. SHA-256 of 3.5.2: fe03ca31524ce188986792f564969a43ccfec2292704643d0b4d187d491c30dd (.sha256). Seerr is by the Seerr team, MIT; built and packed here, not written here. The package also carries Node.js (MIT), the C++ runtime (GPL-3.0 with the GCC Runtime Library Exception), libvips through sharp (LGPL-3.0), the sqlite3 binding (BSD-3-Clause), BusyBox (GPL-2.0) and the npm packages Seerr depends on, each under its own licence; share/licenses/NOTICE in the install folder names each part with its licence and source. Upstream: docs.seerr.dev · source · release notes.

Tautulli · Plex statistics

Tautulli watches a Plex Media Server: what is playing now, who played what, when and on which device, with statistics, graphs, a searchable history, and notifications for playback and for newly added media. It reads Plex’s own interfaces; nothing is installed on the Plex side.

First start

App Center’s Open leads to http://<NAS>:8181/, Tautulli’s own port. The first start sets a password for the user tautulli, and the package copies it to QTS’s System Logs as a warning. Sign in with it; the setup wizard then asks for your Plex account and server. Change the password under Settings → Web Interface. Plex Media Server can run on this NAS or on another machine Tautulli can reach.

The package

Tautulli 2.19.1 as its developers release it, as source with the modules it needs, run on the Python 3.13 the package carries. It runs as the account tautulli; settings, the API key, the database, logs, backups and the image cache are in <install volume>/Tautulli, which an upgrade or a removal leaves in place. Tautulli still says when a newer release exists, but its own Update button cannot write into the package’s folder: the newer version comes as a new package in App Center.

A little history

Tautulli was called PlexPy until version 2.0: its changelog begins with PlexPy v1.0 of 11 August 2015, and the 2.0 beta of 18 December 2017 warns that going back to PlexPy v1 will not work. Its README names its roots: code from Headphones and PlexWatchWeb.

Installation

Recommended — from App Center. Add this site’s repository once; after that the package installs and updates from App Center like any other app.

  1. App Center → ⚙ Settings → App Repository → Add.
  2. Name it QNAP Utilities, paste https://www.qnaputilities.com/repo.xml, Add.
  3. Open QNAP Utilities in the left rail and install Tautulli.

The repository panel: every package in the feed →

By hand instead: take the build below, then App Center → Install Manually.

What it needs

A QNAP NAS with an x86_64 processor (Intel or AMD) on QTS 6.0 or QuTS hero 6.0 or newer, and a Plex Media Server.

Download

Package name Tautulli. SHA-256 of 2.19.1: 91fe4b39e1b0af9bafecfc052584e3f4d0c1e949cf5d3838310d0a9171043689 (.sha256). Tautulli is by Tautulli’s developers, GPL-3.0; packed here, not written here. The package also carries Python (PSF-2.0) and BusyBox (GPL-2.0); share/licenses/NOTICE in the install folder names each part with its licence and source. Upstream: tautulli.com · source · release notes · wiki.

TunerHub · live TV for Plex, Emby and Jellyfin

TunerHub is Dispatcharr for your QNAP NAS, built from Dispatcharr’s source: your IPTV playlists, TV guides and video on demand in one channel list. It joins M3U playlists and Xtream Codes accounts, matches each channel with its guide, and hands the lot to Plex, Emby and Jellyfin as an HDHomeRun tuner. Its DVR records programmes to the NAS, one by one or by series.

Dispatcharr's TV guide: channels and their programmes Dispatcharr's channels and streams Dispatcharr's video-on-demand library Dispatcharr's stats: an active stream and its client

Screenshot: Dispatcharr

First start

App Center’s Open leads to http://<NAS>:9191/. The page asks you to make the first account: a user name and a password you choose. It takes them from a computer on the NAS’s own network, at the NAS’s address or its own name, within 60 minutes after TunerHub starts; restart TunerHub in App Center to open it again. The package generates no password and writes none to a file or to System Logs.

Plex, Emby and Jellyfin

Add a tuner of the kind HDHomeRun at http://<NAS>:9191/hdhr and the guide (XMLTV) at http://<NAS>:9191/output/epg; TunerHub’s Channels page shows both addresses to copy. Type the tuner’s address into the media server: it does not find the tuner by searching the network.

The package

The package holds Dispatcharr 0.32.0, unchanged. Python 3.14, PostgreSQL 18, Valkey 9, nginx, uWSGI and FFmpeg 9 with HTTPS are compiled from source; Dispatcharr’s Python and JavaScript packages come from PyPI and npm, and Vite builds its web interface. It runs as the account tunerhub, and only nginx on port 9191 faces the network. The database, logos, playlists, guides, backups and logs are in <install volume>/TunerHub, the recordings in Multimedia/TunerHub (Public/TunerHub on a NAS without the shared folder Multimedia), where Plex, Emby and Jellyfin can read them; an upgrade or a removal leaves both in place. Over SSH, while TunerHub runs, tunerhub manage changepassword <user> sets a new password.

Left out

The optional machine-learning step of guide matching (TunerHub matches guides by name without it), VLC as a stream profile, Comskip and hardware transcoding. FFmpeg and Streamlink are in the package for their stream profiles, next to Dispatcharr’s built-in proxy.

Installation

Recommended — from App Center. Add this site’s repository once; after that the package installs and updates from App Center like any other app.

  1. App Center → ⚙ Settings → App Repository → Add.
  2. Name it QNAP Utilities, paste https://www.qnaputilities.com/repo.xml, Add.
  3. Open QNAP Utilities in the left rail and install TunerHub.

The repository panel: every package in the feed →

By hand instead: take the build below, then App Center → Install Manually.

What it needs

A QNAP NAS with an x86_64 processor (Intel or AMD) on QTS 6.0 or QuTS hero 6.0 or newer, and IPTV playlists of your own.

Download

Package name TunerHub. SHA-256 of 0.32.0.1: 09d000b761cec0447dfae798698c9b1759441e348f9099c4042a577f5ed4d27a (.sha256). Dispatcharr is by the Dispatcharr project, AGPL-3.0; packed here, not written here. Dispatcharr is a trademark of the Dispatcharr project, which does not make or endorse this package. Its complete source: Dispatcharr-0.32.0.tar.gz. The package also carries Python, PostgreSQL, Valkey, nginx, FFmpeg and BusyBox; share/licenses/NOTICE in the install folder names each part with its licence and source. Upstream: source · documentation.

AFFiNE · docs, whiteboards and databases for a team

AFFiNE puts docs, whiteboards and databases (tables and boards) in one workspace that a team edits together in the browser, and everyone sees the changes as they happen. This package runs AFFiNE’s server and its web app on your QNAP NAS, so the workspaces and the files in them stay on the NAS.

AFFiNE: a doc in the web app, with the workspace's docs on the left AFFiNE: the same doc as a whiteboard, with a mind map and the drawing tools AFFiNE: the list of all docs in a workspace AFFiNE's setup page: the first administrator's name, email address and password

Screenshot: AFFiNE

First start

App Center’s Open leads to http://<NAS>:9310/. AFFiNE’s own setup page asks for the first administrator: a name, an email address and a password you choose. It takes them from a computer on the NAS’s own network, at the NAS’s address or its own name, within 60 minutes after AFFiNE starts; restart AFFiNE in App Center to open it again. The package generates no password and writes none to a file or to System Logs. The email address does not have to receive mail: the package sends none.

Your team

The web app first opens a demo workspace that is kept only in that browser. In the workspace menu, Enable Cloud moves it to the NAS, and a workspace on the NAS is one your team can share.

The administrator makes an account for each person in AFFiNE’s admin panel (http://<NAS>:9310/admin), gives them the password and adds them to a workspace. Steps that need email, such as a password reset or an invitation by email, reach no one.

Behind a website address

A site of a web server on the NAS (WebPortico or another) can stand in front of AFFiNE when it passes WebSockets through, which the live sync needs. AFFiNE’s links name the NAS’s address and port 9310 until you change them: over SSH, affine url https://notes.example.com with the site’s address, then restart AFFiNE in App Center. After that, sign in at the site’s address.

The package

AFFiNE 0.27.4, its server and web app as its makers build them, unchanged, on Node.js 22 from nodejs.org. PostgreSQL 18 with pgvector, Valkey 9 and nginx are compiled from source. It runs as the account affine, and only nginx on port 9310 faces the network. The database, the uploaded files and the server’s signing key are in <install volume>/AFFiNE; an upgrade or a removal leaves the folder in place. Over SSH, while AFFiNE runs, affine psql opens its database. On a test NAS it used about 320 to 380 MB of memory after one person’s session.

Left out

The AI features, which need an outside AI service and its key; the search indexer, which upstream’s own setup also leaves off; email. AFFiNE’s phone and desktop apps are not tried against this package yet: use the browser.

Installation

Recommended — from App Center. Add this site’s repository once; after that the package installs and updates from App Center like any other app.

  1. App Center → ⚙ Settings → App Repository → Add.
  2. Name it QNAP Utilities, paste https://www.qnaputilities.com/repo.xml, Add.
  3. Open QNAP Utilities in the left rail and install AFFiNE.

The repository panel: every package in the feed →

By hand instead: take the build below, then App Center → Install Manually.

What it needs

A QNAP NAS with an x86_64 processor (Intel or AMD) on QTS 6.0 or QuTS hero 6.0 or newer.

Download

Package name AFFiNE. SHA-256 of 0.27.4: f94feb1a4d2b8c74050ca78a96964aef4d5f08b5e1af638926002d0e0de711f7 (.sha256). AFFiNE is by Toeverything; packed here, not written here. Its web app and most of its code are under the MIT licence, and its server’s Community Edition is under the Mozilla Public License 2.0; the three licence texts are in share/licenses/affine/ in the install folder. AFFiNE is a trademark of Toeverything, which does not make or endorse this package. The package also carries Node.js, PostgreSQL, pgvector, Valkey, nginx and BusyBox; share/licenses/NOTICE names each part with its licence and source. Upstream: source · documentation.

Important Safety Note!

Safety

Repository Security & Trust

Both QNAPUtilities and MyQNAP.org repositories are fully trusted sources. Every application distributed through our channels is strictly tested, including ClamAV scans.

Warning: This level of security does not apply to other third-party repositories of unknown origin on the internet. Even if an unknown repository uses a purchased signing key, the risk of malicious activity remains. Always verify the source. By installing packages from our repositories, you agree to the following terms.

Add the MyQNAP.org repository

SafetyMyQNAP.org [Main] Community Repo

Add the MyQNAP.org community repository to App Center once, and App Center installs and updates its packages.

NameMyQNAP URLhttps://www.myqnap.org/repo.xml
  1. Open App Center on the NAS.
  2. Click the gear to open its settings.
  3. Open App Repository, then Add.
  4. Name MyQNAP, URL https://www.myqnap.org/repo.xml, then Add.
  5. Close the settings.
  6. Open MyQNAP in App Center’s left rail: its apps are there.

Screenshots: MyQNAP.org, from its Install the REPO page.

Important Safety Note!

Team Members

Sign-in for the team. Team accounts are not open yet: nothing typed here leaves this page.