Failed ‘up’ action for ‘jellyfin’ and Tailscale app - how tofix

Apps and Virtualization
1

Both JellyFin and Tailscale apps were working fine and then there was an update for both and now neither will launch. I dont understand this log, confused as to what happened with the update. Please Help

[2025/12/21 01:04:37] (ERROR) app_lifecycle.compose_action():56 - Failed ‘up’ action for ‘jellyfin’ app: jellyfin Pulling \n permissions Pulling \n jellyfin Error Get “h-ttps://registry-1.docker.io/v2/”: dial tcp: lookup registry-1.docker.-io on [::1]:53: read udp [::1]:49031->[::1]:53: read: connection refused\n permissions Error context canceled\nError response from daemon: Get “h-ttps://registry-1.docker.io/v2/”: dial tcp: lookup registry-1.docker.-io on [::1]:53: read udp [::1]:49031->[::1]:53: read: connection refused\n
[2025/12/21 01:04:39] (ERROR) app_lifecycle.compose_action():56 - Failed ‘up’ action for ‘tailscale’ app: tailscale Pulling \n tailscale Error Get “h-ttps://ghcr.io/v2/”: dial tcp: lookup ghcr.-io on [::1]:53: read udp [::1]:36164->[::1]:53: read: connection refused\nError response from daemon: Get “h-ttps://ghcr.io/v2/”: dial tcp: lookup ghcr.-io on [::1]:53: read udp [::1]:36164->[::1]:53: read: connection refused\n
[2025/12/21 01:04:52] (ERROR) app_lifecycle.compose_action():56 - Failed ‘up’ action for ‘tailscale’ app: tailscale Pulling \n tailscale Error Get “h-ttps://ghcr.io/v2/”: dial tcp: lookup ghcr.-io on [::1]:53: read udp [::1]:50906->[::1]:53: read: connection refused\nError response from daemon: Get “h-ttps://ghcr.io/v2/”: dial tcp: lookup ghcr.-io on [::1]:53: read udp [::1]:50906->[::1]:53: read: connection refused\n
[2025/12/21 01:05:02] (ERROR) app_lifecycle.compose_action():56 - Failed ‘up’ action for ‘jellyfin’ app: jellyfin Pulling \n jellyfin Error Get “h-ttps://registry-1.docker.io/v2/”: dial tcp: lookup registry-1.docker.-io on [::1]:53: read udp [::1]:46350->[::1]:53: read: connection refused\nError response from daemon: Get “h-ttps://registry-1.docker.io/v2/”: dial tcp: lookup registry-1.docker.-io on [::1]:53: read udp [::1]:46350->[::1]:53: read: connection refused\n
[2025/12/21 01:06:09] (ERROR) app_lifecycle.compose_action():56 - Failed ‘up’ action for ‘jellyfin’ app: jellyfin Pulling \n jellyfin Error Get “h-ttps://registry-1.docker.io/v2/”: dial tcp: lookup registry-1.docker.-io on [::1]:53: read udp [::1]:36574->[::1]:53: read: connection refused\nError response from daemon: Get “h-ttps://registry-1.docker.io/v2/”: dial tcp: lookup registry-1.docker.-io on [::1]:53: read udp [::1]:36574->[::1]:53: read: connection refused\n
[2025/12/21 01:06:43] (ERROR) app_lifecycle.compose_action():56 - Failed ‘up’ action for ‘jellyfin’ app: jellyfin Pulling \n jellyfin Error Get “h-ttps://registry-1.docker.io/v2/”: dial tcp: lookup registry-1.docker.-io on [::1]:53: read udp [::1]:60358->[::1]:53: read: connection refused\nError response from daemon: Get “h-ttps://registry-1.docker.io/v2/”: dial tcp: lookup registry-1.docker.-io on [::1]:53: read udp [::1]:60358->[::1]:53: read: connection refused\n
[2025/12/21 01:09:38] (ERROR) app_lifecycle.compose_action():56 - Failed ‘up’ action for ‘jellyfin’ app: jellyfin Pulling \n jellyfin Error Get “h-ttps://registry-1.docker.io/v2/”: dial tcp: lookup registry-1.docker.-io on [::1]:53: read udp [::1]:49903->[::1]:53: read: connection refused\nError response from daemon: Get “h-ttps://registry-1.docker.io/v2/”: dial tcp: lookup registry-1.docker.-io on [::1]:53: read udp [::1]:49903->[::1]:53: read: connection refused\n
[2025/12/21 01:09:42] (ERROR) app_lifecycle.compose_action():56 - Failed ‘up’ action for ‘tailscale’ app: tailscale Pulling \n tailscale Error Get “h-ttps://ghcr.io/v2/”: dial tcp: lookup ghcr.-io on [::1]:53: read udp [::1]:36015->[::1]:53: read: connection refused\nError response from daemon: Get “h-ttps://ghcr.io/v2/”: dial tcp: lookup ghcr.-io on [::1]:53: read udp [::1]:36015->[::1]:53: read: connection refused\n
[2025/12/21 01:12:40] (ERROR) app_lifecycle.compose_action():56 - Failed ‘up’ action for ‘jellyfin’ app: jellyfin Pulling \n jellyfin Error Get “h-ttps://registry-1.docker.io/v2/”: dial tcp: lookup registry-1.docker.-io on [::1]:53: read udp [::1]:41200->[::1]:53: read: connection refused\nError response from daemon: Get “h-ttps://registry-1.docker.io/v2/”: dial tcp: lookup registry-1.docker.-io on [::1]:53: read udp [::1]:41200->[::1]:53: read: connection refused\n
[2025/12/21 01:19:57] (ERROR) app_lifecycle.compose_action():56 - Failed ‘up’ action for ‘jellyfin’ app: jellyfin Pulling \n jellyfin Error Get “h-ttps://registry-1.docker.io/v2/”: dial tcp: lookup registry-1.docker.-io on [::1]:53: read udp [::1]:58661->[::1]:53: read: connection refused\nError response from daemon: Get “h-ttps://registry-1.docker.io/v2/”: dial tcp: lookup registry-1.docker.-io on [::1]:53: read udp [::1]:58661->[::1]:53: read: connection refused\n
[2025/12/21 18:54:38] (ERROR) app_lifecycle.compose_action():56 - Failed ‘up’ action for ‘jellyfin’ app: jellyfin Pulling \n jellyfin Error Get “h-ttps://registry-1.docker.io/v2/”: dial tcp: lookup registry-1.docker.-io on [::1]:53: read udp [::1]:55284->[::1]:53: read: connection refused\nError response from daemon: Get “h-ttps://registry-1.docker.io/v2/”: dial tcp: lookup registry-1.docker.-io on [::1]:53: read udp [::1]:55284->[::1]:53: read: connection refused\n
[2025/12/21 18:54:50] (ERROR) app_lifecycle.compose_action():56 - Failed ‘up’ action for ‘tailscale’ app: tailscale Pulling \n tailscale Error Get “h-ttps://ghcr.io/v2/”: dial tcp: lookup ghcr.-io on [::1]:53: read udp [::1]:45841->[::1]:53: read: connection refused\nError response from daemon: Get “h-ttps://ghcr.io/v2/”: dial tcp: lookup ghcr.-io on [::1]:53: read udp [::1]:45841->[::1]:53: read: connection refused\n

2

The “h-ttps” part looks like it might be the problem.

Have you tried rolling back to the previous versions?

My guess is that the community app maintainers screwed up, again. They do this a lot. I recommend not using these awful community apps, and just installing Dockge and installing your tailscale and jellyfin apps in there with docker-compose yaml scripts which point to the official project build repositories. You don’t need a middleman for your apps.

3

I put the dashes in all of the links before posting the post because it wouldnt let me post on these forums with links in my post

1 Like
4

Yes I tried rolling back to a previous version and it says that without the app up and running I can’t roll back to previous version

5

dockge or docker?

6

“Dockge”. It’s a web-accessible app that lets you install and manage docker apps using docker-compose scripts. You can also use Portainer, but I think Dockge is much easier to use.

7

Wow. This kinda defeats the purpose of roll-back, doesn’t it? :grinning_face_with_smiling_eyes: Another reason to avoid these community apps if you can. For some strange reason, TrueNAS requires apps to be running to upgrade them (and apparently to roll them back too, didn’t know this before now). This is not a requirement of Docker in any way.

8

Indeed seems to defeat the purpose of rolling back. haha. This is my first foray into home servers and I was able to get truenas, photoprism, jellyfin, and tailscale up and running without too much difficulty. There definitely was some difficulty, but it was solvable with some youtube videos of how to setup these programs.

So your suggestion would be to uninstall jellyfin and tailscale and use dockge to reinstall them? Would you install dockge through the apps menu in truenas?

And then reinstall jellyfin and tailscale? Is there a simple/r way to reinstall those without having to go back through the entire setup, connecting SMB shares to jellyfin and setting all permissions for these apps again?

9

When you joined the forum you should have gotten an automatic message from the forum bot for a tutorial, complete it to bump your trust lvl. Then you can post links. We had Probems with spamm attacks in the past so new users can’t post links…

The error in the log seems to indicate your nas has issues reaching docker.io to pull images.
I would check the network settings of your truenas and if other pcs in your network can reach the address in the error message.

10

Awww. OK so it might have been my fault all along. I guess there is more to the story then. I had my server setup on a desk, not its permanent home (also no static IP) I just moved it to its permanent home and it lost the IP address that everything was connected to and so I could no longer access my apps or the truenas interface until connected to the new IP. I got the IP set back to the old IP with a static IP and may have incorrectly set the default gateway which I assume would cause this problem?

Whats the exact address in the error message?

11

Yes, an incorrect gateway or no/wrong dns servers would explain the issue.

12

OMG Thank You for helping me point you into pointing me in the right direction!!! After I added the static IP it removed the DNS servers so adding thos eback was able to get it up and running

13

Yes, that’s how I did it. The only community apps I have installed are Scrutiny and Dockge. Then everything else is installed/managed in Dockge.

You shouldn’t be using SMB at all for Jellyfin. (You can use it if you wish to connect to those same datasets from a Windows PC.) The docker-compose yaml code for JF will just point to the relevant directories, such as “/mnt/pool/video/movies” or whatever.

If you installed JF with its config data in a separate dataset (something like “/mnt/pool/config/jellyfin”), you should be able to point to that with your docker-compose version, and then you probably won’t need to redo anything at all. However, if you went with the default and let it put the config data in .ix-apps/, I don’t think you can reuse that. The .ix-apps stuff is a very bad idea for many reasons (including it isn’t easy to back up); it’s another good reason to generally avoid the community apps. It might be possible though to create config datasets for JF/TS, then manually copy the data from .ix-apps at the command line.