How to update jellyfin which was installed via UI

Apps and Virtualization
1

I am running TrueNAS-13.0-U6.1 with jellyfin 10.8.13 which was installed via the UI and runs in its own jail.

Now I have to update jellyfin since my clients do not support the api of this version anymore.

I thought the best way is to use the “update” button on the plugins page but after some researching it seems that this is not the best option.

So my question is… what is the recommended way to update?

2

Did you install via custom jail or plugin? Because plugins are no longer maintained and basically dead.
If it’s a custom jail you’d first have to update your truenas to 13.3 so you can update your jails to a supported version.
Since core is basically eol and won’t get any major updates anymore even the update to 13.3 is only a bandaid until the max jail version you can run on it is no longer supported.
If you want to have a longerm solution your best option would be to migrate over to the community ediotion (previously scale) and rebuild your jellyfin jail as a docker app or, if you dont want to be dependend on the apps maintainer for updates, you can deploy it in a custom app with your own docker-compose file.

3

oh man…

this is prob. a stupid question but how can I find out if I installed it via custom jail or plugin.

I assume migrating to the community edition and rebuild all my jails ( I have all those sonar, radarr etc stuff) is not an easy task…

4

What programs are you running in jails?
If its the *arrs, jellyfin and something like qbittorrent, they’re all available as docker apps, all you have to add is storage paths.
You could setup a scale vm on your core box and try it out before migrating for real.

Did you create a custom jail and then used pkg inside the jail to manually install the programs you’re using or did you got to plugins and istalled them from the list of available plugins?

5

ah ok then I installed it via the plugins…

Well I have this:

+-----+--------------+-------+--------------+---------------+
| JID |     NAME     | STATE |   RELEASE    |      IP4      |
+=====+==============+=======+==============+===============+
| 11  | jellyfin     | up    | 13.2-RELEASE | DHCP          |
+-----+--------------+-------+--------------+---------------+
| 9   | prowlarr     | up    | 13.2-RELEASE | 192.168.1.232 |
+-----+--------------+-------+--------------+---------------+
| 8   | radarr       | up    | 13.2-RELEASE | 192.168.1.233 |
+-----+--------------+-------+--------------+---------------+
| 7   | sonarr       | up    | 13.2-RELEASE | 192.168.1.231 |
+-----+--------------+-------+--------------+---------------+
| 6   | transmission | up    | 13.2-RELEASE | 192.168.1.230 |
+-----+--------------+-------+--------------+---------------+

and transmission jail also runs a vpn.

So I assume with “migration” to the community edition you mean - backing up all the jail data - doing a fresh install of the community edition and then add all those docker apps and trying to restore them?

Couln’t I just add a custom jail and install there a fresh jellyfin with the latest version?

6

you can try. But again somehwere in the near future even that custom jail won’t be able to update anymore. For that, the base version of bsd would have to be upgraded. But 13.3 is the last update core recieved and you’d eventually have to migrate to scale anyway.

7

Well I guess I will have to move to the community edition at some point.

Are there any “guides” or something which could help me to migrate from core to the community edition? Especially on how to move the jails and their setup?