How to Run an Authorised Torrent Server

Authorised use only

Use torrents only for content you own, are explicitly authorised to access or that is public domain or openly licensed. Good examples include Linux ISOs, public-domain material, open datasets and legitimate software distribution. A torrent client does not change copyright or permission rules. This guide does not provide piracy instructions.

Hardware and prerequisites

Use a supported Linux base machine with known storage, power and network facts. Plan space for incomplete and complete downloads, a restricted service account and a local-only management path. You do not need to expose a Web UI or add a VPN to download authorised content.

Install qBittorrent-nox or Transmission

Assume Ubuntu or Debian and use distribution packages or the project’s current official instructions:

sudo apt update
sudo apt install qbittorrent-nox
sudo useradd --system --home /var/lib/qbittorrent --shell /usr/sbin/nologin qbittorrent
sudo install -d -o qbittorrent -g qbittorrent /srv/torrents/{incomplete,complete}

Package names and service setup vary by distribution. Check the installed service before enabling it and do not run the client as root.

Folders, permissions and seeding

Keep incomplete and complete folders separate, grant the service account only the storage it needs and monitor free space. Verify the distribution’s checksum where provided. Seed responsibly for legitimate distributions, respect the publisher’s instructions and stop when you no longer have permission or space.

Web UI, firewall and remote management

Set a strong unique Web UI password, bind management to the local network and allow only the required port through the host firewall. Do not expose the Web UI directly to the public internet. If remote management is genuinely needed, use a properly secured private network or documented access gateway. An optional VPN can be used for privacy or network-policy reasons in lawful use; it is not a way to evade authorisation or copyright rules.

Updates and troubleshooting

Keep the OS and client updated. If a download cannot write, inspect directory ownership and the service account. If peers cannot connect, check the local firewall, port settings and whether the content’s publisher permits incoming connections. If the Web UI is unreachable, use the local console and service logs rather than opening it broadly.

Recovery and next steps

Back up client settings and any important downloaded data separately. Rebuild the service on a clean host if its configuration becomes uncertain. Continue with Docker, backups or home-lab basics.

Check the service

systemctl status qbittorrent-nox
journalctl -u qbittorrent-nox --since today
df -h /srv/torrents

Service names vary by distribution. You should see the client running, enough free space, and downloads separated into incomplete and complete directories. Confirm the Web UI works from the LAN with the strong password you set, then test one authorised Linux ISO or open dataset.

Recovery and lawful seeding

Back up client settings and important downloaded data separately. Keep a written record of the service account, folders and firewall rule. Rebuild on a clean host if its configuration becomes uncertain. Seed only when the publisher’s terms permit it, stop when you no longer have permission or space, and never treat a VPN as a substitute for authorisation.

What next?

Continue with Docker, backups or home-lab basics. Build an authorised torrent host when you have a lawful use in mind.

Build an authorised torrent host Run Docker · Plan backups