On this page
Tdarr: Problems
Find what is wrong with Tdarr, then follow the numbered answer.
The chart in words
Start: Tdarr is not working as it should
- Then: What does its tab say?
- Did not start: 1. Start it again
- Not supported: 2. Update it or update Starboard
- Active, but something is wrong: What is wrong?
- Its page does not open: 3. Open its page
- Tdarr is not connected yet: 4. Connect Tdarr
- Nothing is converting: 5. Check what Tdarr does and when
- Not active, and bringing in Tdarr failed: 6. Bring in your Tdarr again
1 Start it again
Its tab says Did not start when Tdarr did not start, or stopped answering.
- On Tdarr's tab, read the message under its state: it says why it stopped.
- Select Try again.
- If it stopped soon after an update, select Roll back to and the version you had. Read Updates.
- Still failing: go to System, then Logs, and find its name.
If your old Tdarr in the main install is still running, it may hold port 8265. The plug-in then takes the next free port, so Starboard's own Tdarr page may not find it until the old one is removed.
2 Update it or update Starboard
Your Starboard's plug-in API is outside what this version of Tdarr works with, so Starboard stopped it.
- Select Check for an update on its tab.
- If there is none, update Starboard. Read Update Starboard.
3 Open its page
Tdarr's page is on your home network, at this computer's address and the port Starboard chose for it: 8265 when it is free, otherwise the next free port.
- Check Tdarr's tab says Active. Starboard gives it a port only once it is active.
- Under Its web page, read the address, then select Open Tdarr.
- Open it from a device on your home network. It does not open from away from home.
- If it still does not open, deactivate it, activate it again and wait a minute for Tdarr to start.
4 Connect Tdarr
The Settings section on its tab says Tdarr is not connected yet until Tdarr has a key Starboard keeps.
- Select Connect Tdarr. Tdarr restarts once, and Starboard waits for it.
- If it says Tdarr did not answer after restarting. Check it is running in Apps, then try again., check Tdarr's tab says Active.
- Select Connect Tdarr again.
5 Check what Tdarr does and when
On its tab, under Settings:
- Under What Tdarr does, check it is Save space. Check files only changes nothing, and Off does nothing.
- Under Libraries, check Films, Series or both are ticked.
- Under When, In quiet hours converts only in Starboard's download hours, or 01:00 to 06:00 when they are not set. Choose Any time to start on new files straight away.
Save space keeps a new file only when it is smaller, so some files stay as they are.
6 Bring in your Tdarr again
Bring in the Tdarr you already have… says why it stopped. Your Tdarr is not changed when the copy fails.
- Deactivate Tdarr first, so nothing writes to its folder while the copy is made: select Deactivate, then try again.
- Starboard found no Tdarr on this computer (no container called tdarr): the main install has no Tdarr to copy. Set the plug-in up as a new Tdarr instead. Read Install.
- Tdarr keeps /app/server in a Docker volume, which Starboard cannot copy. Copy it by hand: copy those folders into the plug-in's folder in Starboard's data,
data/plugins/tdarr, yourself. - Tdarr has none of the folders this plug-in copies: there is nothing to bring in. Set it up as a new Tdarr.
- Starboard could not stop Tdarr for the copy, or The copy did not finish: read the rest of the message, then try again. Go to System, then Logs, for more.
If the plug-in had made folders of its own already, Starboard puts them beside the copy, named before-copy with the date and time, and deletes nothing.
Report a problem
If none of these helps, tell its maker, with what its tab says: the plug-ins' issues on GitHub.
Find out more
This page on GitHub, where the help is written.