Settings

Settings is at the bottom of the panel sidebar. Each subsection below lists what it controls. Most have a detailed page of their own; Torrent and Notifications are described in full here.

What you'll learn

Where each setting lives, what the defaults are, and which page explains it in detail.

Storage

Settings → Storage decides where downloads live and how much space the watch cache may take:

• how the downloads disk is used: kept torrents, cache, library, other files and free space;
• Cache limit and Keep free. Until you change them, defaults based on the disk size apply;
• Deleted automatically: the torrents the cache removes first;
• Library: how much the library takes and whether kept files are hard-linked or copied;
• Folders: the downloads and library folders, and moving existing data to a new folder.

See Storage.

Torrent

Settings → Torrent controls speed, the download queue, seeding and the engine's network. Each card shows its default and saves on its own.

Speed

• Download speed, in MB/s. Limits downloads and torrents added in the panel. Watching ignores the limit, so video doesn't stutter. Empty means no limit, the default.
• Upload speed, in MB/s. Limits everything the engine uploads to peers, including while watching. On a slow connection, uploads can fill it up and make video stutter. Empty means no limit, the default.

Queue and seeding

• Download queue. How many downloads run at once: 3 by default, from 0 to 100. The rest wait, but you can already watch them. 0 means no queue: everything downloads at once.

• Seeding after download. What happens to files you downloaded in full:

  • Always seed, the default;
  • Until a ratio: uploaded divided by size, from 0.1 to 100. 2 means upload twice what you downloaded;
  • For a while: in hours or days, counted from when the download finished, from 1 hour to 10 years;
  • Don't seed.

  While a download is in progress or someone watches it, it always seeds. A single download can have its own rule in its card, see Downloads.

• Seed what you watched. With Seed watched torrents on (the default), torrents you only watched stay in the cache and seed until the cache removes them. Turn it off if uploads get in the way.

Connections

• Connections. How many peers at once: Per torrent 50 by default (1 to 1000), Total 200 (0 to 10,000; 0 means no overall limit). Many connections are hard on a weak router or NAS. A torrent being watched always gets the full per-torrent limit.

• Incoming connections. The port peers connect to, from 1024 to 65,535. By default it's the ENGINE_PEER_PORT variable or, without it, a random port chosen once. If the port is open on the router, you get more peers. In Docker, publish the same port in docker-compose.yml: the card warns when they differ. See Configuration.

  Open the port on the router with UPnP lets the router open the port itself. It's off by default: not every router does this safely.

• Peer discovery. Where the engine looks for peers besides trackers: DHT, a shared peer network without trackers, and PEX, where peers share the addresses of other peers. Both are on by default. Private trackers require them off. Without DHT, watching takes longer to find peers, and magnet links without trackers won't open.

• Encryption of connections with peers. Prefer (the default) encrypts when the peer supports it and keeps the most peers. Require allows encrypted connections only: fewer peers, and playback starts slower.

Engine restart

The engine reads the port, UPnP, peer discovery and encryption when it starts. Their cards are marked After restart, and after you save one, the page says Changes are waiting for an engine restart. Select Restart engine: playback on every device pauses for a few seconds and resumes on its own, and downloads continue. The dialog says how many torrents are being watched right now. While downloads are being moved to another folder, the restart is unavailable until the move finishes.

All other torrent settings apply right away.

Following

Settings → Following: how often the new releases feed is read, how many targeted searches run per hour, and the rules new follows get. See Following.

Backups

Settings → Backups: the backup schedule, the backup folder, password protection, the list of backups with restore and download, and moving data between servers. See Backup and move.

Network

Settings → Network decides how the server reaches TMDB, indexers and managers: directly or through your SOCKS5 or HTTP proxy, with the system DNS or DNS over HTTPS.

• Availability: the hosts the server talks to, checked from the server, not from your browser;
• Default DNS: the DNS for hosts without their own route;
• Routes: which hosts go through a proxy or another DNS.

See Network.

Metadata

Settings → Metadata decides where the catalog takes titles, posters and descriptions from.

• TMDB key. Choose the key the catalog uses: the server's own one, which is the Environment key from TMDB_ACCESS_TOKEN if it is set and the App key built into the image otherwise, or Your key from your TMDB account. Check tests it. See TMDB key.
• IMDb ratings. Off by default. With Show IMDb ratings on, the server downloads the official IMDb ratings dataset once a day and keeps it locally, and the showcase shows the IMDb rating next to TMDB. The dataset is for personal and non-commercial use: turning it on means you accept the IMDb terms. Update now downloads it right away.

Playback

Settings → Playback shows how the server transcodes video a device can't play by itself.

• Hardware acceleration. Whether a GPU was found and passed the test encode on startup, and what it decodes. Turn off Transcode on the GPU if the GPU produces artifacts: the CPU encodes instead. Check again repeats the test.
• CPU and HDR. Up to which resolution the CPU keeps up, measured on startup, and how HDR video is converted for screens without HDR. Larger video is scaled down.

See Hardware transcoding.

Notifications

Settings → Notifications sends server events to Telegram, a webhook, ntfy, Gotify, email or apprise-api, so you learn about them when the panel is closed. The bell in the panel always gets every event, with or without channels.

Add a channel

1. Select Add channel and choose where to send messages:

   Channel	What to enter
   Telegram	Create a bot with BotFather in Telegram and paste its Bot token. Send /start to the bot, then select Find chat to pick the Chat, or enter a chat ID or the @name of a public channel.
   Webhook	The Webhook address. Discord and Slack addresses are recognized; any other address gets Torsher JSON. Set Format by hand if needed, and an optional Authorization header. Keep the address private: it works as a key.
   ntfy	The Server (https://ntfy.sh by default), a Topic that is hard to guess, and an optional Access token. Subscribe to the same topic in the ntfy app. On a public server, anyone who knows the topic can read it.
   Gotify	Your Gotify Server and the Application token of an application created in Gotify.
   Email	The SMTP server and Port of any SMTP server, the Encryption (STARTTLS on port 587 by default), a username and password if the server needs them, and the From and To addresses.
   Apprise API	The address of your own apprise-api server, and either a Configuration key saved in it or Service URLs. It reaches the services apprise-api supports.

2. Under Events, choose what the channel gets:

   Group	What it covers	On for a new channel
   Server problems	The same problems as Needs attention: engine, storage, indexers, network, TMDB	Yes
   Updates	A new Torsher version is available	Yes
   Finished downloads	Files you chose to download are fully downloaded	No
   New devices	A TV was connected with a code	No
   Following	New episodes in the library, and episodes with no releases for a long time	Yes

   Under Server problems, two more options, off by default: Warnings too, not only errors and Tell when a problem is resolved.

3. Choose the Message language, which doesn't depend on the panel language, and check the Panel address used for links in messages.

4. Select Send test to check the settings before saving, then Save.

The list of channels

Each channel shows its kind, its event groups, and when it last sent a message or why the last one wasn't delivered. The switch turns a channel off without deleting it. Its menu has Edit, Send test and Delete.

Tokens and passwords are stored encrypted and aren't shown again. When you edit a channel, a saved secret shows as Saved: leave it empty to keep it. If you change the channel's server address, enter the secret again.

If a test fails

Message	What to check
The service rejected the token or password	The token or password.
The chat, topic or address wasn't found	The chat, topic or address. For Telegram, send /start to the bot first.
The service limited messages: try again later	Wait and try again.
The service didn't respond: check the address and the network route	The address, and whether the server reaches it. A route in Network may be needed.
The service rejected the message	The settings of the receiving service.
The settings are incomplete or a saved key can't be read: enter it again	Fill in the missing fields, or enter the saved secret again.

Account

Settings → Account holds the server owner account. There is only one: the household watches through profiles, see Profiles and devices.

• Name. How the panel calls you, at least 2 characters.
• Email. Used only to sign in: the server sends no email. Changing it needs your current password.
• Password. Enter the current password and a new one of at least 8 characters, twice.

After you change the email or the password, all other browsers and devices are signed out of the panel. Forgot the password? See Reset the password.

The panel language and theme are in the account menu at the bottom of the sidebar.

About

Settings → About shows the server version and commit, the license, a link to the source code, and the TMDB attribution. It opens without signing in too, from the sign-in page.

Under Updates:

• Check for updates: once a day the server checks the project's releases on GitHub. The request carries no data about you or the server. When off, the server never contacts GitHub.
• Channel: Stable or Beta.
• Check now.

See Update and roll back. Add the version and commit to a bug report, see Logs and diagnostics.

Next

• Troubleshooting.
• Backup and move.