-
Notifications
You must be signed in to change notification settings - Fork 0
Remote Access
Ways to reach your Tori server from outside your home network.
Forward your router's external port to your Tori machine's local IP and port (default 43211). Your ISP-assigned public IP becomes your access point — a dynamic DNS service (e.g. DuckDNS, No-IP) is recommended since home IPs often change.
Downsides: exposes your server directly to the internet; requires your computer to stay on and connected; some ISPs block inbound ports or use CGNAT (no public IP at all).
Install Tailscale (or similar) on both your Tori host and any device connecting to it. Devices get a private mesh IP that works from anywhere, with no ports exposed to the public internet.
Best for: personal use across your own devices, without wanting a public URL.
Run Tori entirely on a rented VPS (e.g. a small Ubuntu instance) instead of your home machine. This gives you a stable public IP, no dependence on your home network/ISP, and true 24/7 uptime.
- Provision a Linux VPS (2 vCPU / 4GB RAM / 40GB disk is a reasonable baseline).
- Build or upload the
toriLinux binary and run it as asystemdservice so it survives reboots. - Set
host = '0.0.0.0'inconfig.toml(see Configuration). - Point Tori Denshi/Tenji at the VPS's public IP and port.
- Set a server password (Settings → General) since this instance is reachable by anyone who finds the IP.
- Optionally put it behind a domain + HTTPS (e.g. via Caddy or nginx + Let's Encrypt) instead of raw
http://ip:port.
Note: since your media library and/or torrent activity happens on the VPS itself, this only makes sense if you're not relying on files stored on your own computer — see Desktop Streaming Setup for a debrid/torrent-based setup that doesn't need local storage.
- Set a server password
- Keep Tori updated to the latest release
- Don't expose your torrent client's Web UI (qBittorrent, etc) publicly — only the Tori server port needs to be reachable