Auto-Updates
This page is about Tdarr's internal Server and Node auto-updater, available in version 2.56.01 and above.
Tdarr's internal auto-updater is separate from the standalone Tdarr_Updater executable. The auto-update settings on the Options tab only control the internal Server and Node updater; they do not configure, enable, disable, or schedule Tdarr_Updater.
To use Tdarr_Updater, run the Tdarr_Updater executable directly. For native installs, its target versions are controlled by configs/Tdarr_Updater_Config.json, such as the requiredVersion setting.
As Docker images/containers are designed to be immutable (fixed), you need to set env enableDockerAutoUpdater=true to enable the auto-updater.
For Servers and Nodes running in Docker, it's recommended to use container managers such as Portainer, Watchtower or Ouroboros to auto-update rather than using the internal auto-updater, as the internal auto-updater won't apply any container-specific dependency or config changes
If running multiple Nodes on the same machine, make sure they have been created in a different directory, else 2 Nodes trying to auto-update at the same time may cause file conflicts. For example:
C:/Users/Bob/Documents/Tdarr1/Tdarr_Node/Tdarr_Node.exe
C:/Users/Bob/Documents/Tdarr2/Tdarr_Node/Tdarr_Node.exe
The internal auto-updater can also downgrade Server and Node versions by selecting an older version.
The internal auto-updater may take some time to complete and any errors will be shown in the corresponding log for that module, i.e. ./logs/Tdarr_Server_Log.txt for Tdarr Server and ./logs/Tdarr_Node_Log.txt for Tdarr_Node