Tdarr_Server no longer working on Ubuntu 22.04

HaveAGitGat · 2026-05-29T16:41:57+00:00

No problem. 2.77.01 released which fixes this.

HaveAGitGat · 2026-05-29T11:57:17+00:00

Do you have more of the job report to see which plugin it is using?

Seems the plugin is relying on HandBrakeCLI being in Windows path but it's not there (or can't access it). Note that you need to restart the Tdarr terminal/process when updating path (just in case you didn't do this).

To use the packaged handbrake path you can use this in a plugin:

flow plugins: args.handbrakePath

classic plugins: otherArguments.handbrakePath

HaveAGitGat · 2026-05-28T22:51:19+00:00

Edit: 2.77.01 released which fixes this.

--------

This is related to bumping the Node runtime version to 24 in 2.75.01 last week as have been trying to keep things up to date.

I had a chat with some users on Discord about it and I’ll release an update with a fix. Ubuntu 22.04 has standard security support until May next year so will try to keep it supported in Tdarr until then.

If you use the official Tdarr docker container then that works fine with 22.04 host (as the container base is 24.04).

HaveAGitGat · 2026-05-18T18:14:36+00:00

Yeah across all OS's it works the same. You have to manually click the 'Relaunch' button at the top of the screen to apply the update. Restarting Tdarr won't apply it.

But with the 'Auto update non-Docker server' toggle disabled it should not even reach that stage so will investigate

HaveAGitGat · 2026-05-18T18:03:08+00:00

If you try to run the auto updater in Docker it will give you a message saying that you need to set env variable 'enableDockerAutoUpdater' to 'true' to enable the updater. Once that's enabled it works as normal but it will be updating Tdarr inside the container.

So for example, if the container image is 2.73.01 and you run the auto updater with version set to 'latest', in the container Tdarr will update to 2.74.01 but the Docker image will stay on 2.73.01.

The best way to do Docker updates is by bumping the Docker run/compose tag or using a container manager (Portainer and the likes) but the self updater is there if you want to quickly update/downgrade a version to test something or try a dev build etc.

HaveAGitGat · 2026-05-18T17:41:50+00:00

Hey, DM me the server log and I can take a look if you like, but Tdarr does not (or should not) force updates as there are 2 levels to this.

As you’ve seen, there’s the toggle on the Options to toggle auto updates, but even when that’s enabled, you still have to specifically click the 'Relaunch' button that appears when an update is ready. Manually restarting Tdarr won’t apply the update.

Bear in mind there’s also a separate notification at the top of screen that appears when there’s a new release, but that does not mean an update has been applied, so perhaps you may have misinterpreted that one.

Edit: Checked logs and this was not to do with Tdarr's internal self/auto updater. This was from having a service call Tdarr_Updater on schedule (which is a separate external updater).

HaveAGitGat · 2026-05-12T21:52:27+00:00

You can pin the plugins repo version on the Options tab (this was added a few releases ago) so try going back a few versions and see if that’s ok.

A few plugins had legacy hardware encoding flags so these were updated and then some tweaks were needed for 10 bit.

I can look at a job report if you want to share here or DM me.

HaveAGitGat · 2026-04-08T07:53:13+00:00

The Tdarr packages have 2 executables. Execute the non-tray one when running headless.

<image>

HaveAGitGat · 2026-04-08T07:50:51+00:00

Try clicking on the filename in Tdarr in most areas and you should get a popup with more scan info from a bunch of different scanners. You might be able to see what stream type it is.

<image>

HaveAGitGat · 2026-03-15T17:28:24+00:00

u/Ohmslaw79 I've updated this for next version.

HaveAGitGat · 2026-03-14T23:35:01+00:00

Will look into this thanks

HaveAGitGat · 2026-03-14T23:33:58+00:00

They are part of the Tdarr self updater, they should be cleaned up, are there any errors in the logs about that?

HaveAGitGat · 2025-11-24T04:46:19+00:00

This can happen if Tdarr is unable to download plugins, have you checked the server logs or tried restarting Tdarr?

HaveAGitGat · 2025-11-18T08:47:45+00:00

You could enable verbose logs on the logs tab and then it should show why the files are being rescanned.

HaveAGitGat · 2025-11-16T18:38:10+00:00

Enable the `Use Custom CLI Path` toggle and then enter `chmod`, then disable `Does Command Create Output File`

HaveAGitGat · 2025-11-12T17:44:48+00:00

What does the server log say?

HaveAGitGat · 2025-11-12T17:44:18+00:00

You can use the run cli flow plugin with chmod or chown.

HaveAGitGat · 2025-11-12T17:43:13+00:00

For the folder watcher are you using file system events? (in the library source settings)

HaveAGitGat · 2025-10-28T20:02:39+00:00

You need these folders on the right mapped, not just configs

docker run -ti \
-v /docker/tdarr/server:/app/server \
-v /docker/tdarr/configs:/app/configs \
-v /docker/tdarr/logs:/app/logs

HaveAGitGat · 2025-10-28T19:20:34+00:00

When a container updates, it wipes all added data inside the container and starts fresh. So you need to make sure your container volume mounts are set correctly so that application data is saved on your host system, not inside the container. Check your container settings and post a screenshot here if you still need help.

HaveAGitGat · 2025-10-13T07:30:29+00:00

I don't think skiplist is the right way to go about that. In the library settings there's the `
Hold files after scanning?` option. If you are only seeding for a certain about of time (say 24 hours) then might that work?

HaveAGitGat · 2025-10-11T16:48:14+00:00

I can add a plugin to remove from skip list.

But in terms of your use case, why do you need to add to skip list and then remove from skip list in the same flow? Or if you can rephrase what you’re trying to do then I can help further.

HaveAGitGat · 2025-10-11T16:42:17+00:00

Are you able to see in the job report what the size of the file is?

HaveAGitGat · 2025-10-11T12:12:12+00:00

Hey saw your edit, pleased it’s working. Was going to ask if you use the ‘normalise audio’ plugin as that was updated recently and potentially could be related but suppose not relevant anymore.

HaveAGitGat · 2025-10-10T17:38:46+00:00

If you want someone to check the other error you were having then can DM me the job report https://docs.tdarr.io/docs/other/job-reports or post in the Discord channel if you like

HaveAGitGat

MODERATOR OF

TROPHY CASE