I am too stupid to upgrade my installed Jellyfin instance (TrueNAS Core)

[regimeG]

In the past, I always had trouble updating my installed Jellyfin instance. In the end, I always had to reconfigure everything.

Last time I was only able to install my Jellyfin server via this link (fetch https://raw.githubusercontent.com/spz2k9/iocage-plugin-jellyfin/master/jellyfin.json
iocage fetch -P ./jellyfin.json --name jellyfin
rm ./jellyfin.json) from this thread (https://github.com/spz2k9/iocage-plugin-jellyfin). I then uninstalled the official community plugin.

Now I see that Jellyfin 10.8.13 has been released here, but I'm too dumb to update my version.

Can you please help me to update my version without losing my configuration?

I am really lost. Many thanks in advance!

[Thefrank]

That looks like it was setup as a plugin jail which should make that easy.
Try iocage update JAILNAME (where JAILNAME is the name of your jail)

[regimeG]

Thanks for the quick reply. I get the following error:
/mnt/Pool1/iocage/jails/jellyfi/jellyfi.json was not found

[Thefrank]

Either remake the missing .json or remake the jail using a URI to the .git of that repo

[regimeG]

I'm afraid I've strayed off the road a bit. What do you suggest is the best way to run your Jellyfin server so that I can easily update it the intended way in the future?

[Thefrank]

If you don't have much experience with it and are using TrueNAS CORE I advise using a "thick" jail with just jellyfin and mounting in anything that you need. A "thin" jail or even a different jail manager (pot, cbsd, bastile, others...) under FreeBSD handle this much better than iocage and TrueNAS CORE. Their plugin system was OK until they killed it.

The "simple but not completely easy" for TrueNAS CORE would be: Create jail that will work for jellyfin; FreeBSD 13.2-Release or higher, mlock enabled, network enabled -> Install just jellyfin via pkg; motoring software is OK here (e.g., Zabbix) -> mount in resources you want jellyfin to use (e.g., "Music") -> Enjoy!... -> update jellyfin either using iocage from the host or pkg upgrade inside the jail.

[regimeG]

Thanks for your support, but I don't think I'm tech savvy enough to safely maintain Jellyfin in this way permanently.

So far I had the following plan:

1. i wanted to install "wget".

->pkg install wget

2. I wanted to navigate to the path.

-> cd /mnt/Pool1/iocage/jails/jellyfi

3. then execute the following command there:

-> wget https://raw.githubusercontent.com/spz2k9/iocage-plugin-jellyfin/master/jellyfin.json

4. then try the update again.

-> iocage update jellyfin

Unfortunately none of this works.

Can you perhaps tell me how I can restore the .jason file?

[Thefrank]

@spz2k9 Please add an INDEX file to your repo or copy the repo and add an INDEX to it. This will allow the creating of a plugin jail directly via iocage fetch -g https://github.com/spz2k9/iocage-plugin-jellyfin/ -n NAMEOFJAIL -P jellyfin

{
        "jellyfin": {
                "MANIFEST": "jellyfin.json",
                "description": "Jellyfin Server for FreeBSD",
                "name": "Jellyfin",
                "official": false,
                "primary_pkg": "jellyfin"
        }
}

Other fields include "icon" for the TrueNAS GUI. TrueNAS is removing "plugins" at some point in the future so it is not needed. iocage will still work.
Result + "Plugins" GUI screenshot

root@iocage:~ # iocage fetch -g https://github.com/spz2k9/iocage-plugin-jellyfin/ --name jelltest -P jellyfin
Plugin: Jellyfin Server
  Official Plugin: False
  Using RELEASE: 13.2-RELEASE
  Using Branch: 13.1-RELEASE
  Post-install Artifact: https://github.com/spz2k9/iocage-plugin-jellyfin.git
  These pkgs will be installed:
    - libva-utils
    - libva-intel-media-driver
    - python39
    - jellyfin

Testing Host DNS response to pkg.FreeBSD.org
Testing jelltest's SRV response to pkg.FreeBSD.org
Testing jelltest's DNSSEC response to pkg.FreeBSD.org

Installing plugin packages:
  - libva-utils... 
  - libva-intel-media-driver... 
  - python39... 
  - jellyfin... 

Fetching artifact... 
Cloning git repository

Branch 13.1-RELEASE does not exist at https://github.com/spz2k9/iocage-plugin-jellyfin.git!
Using "master" branch for plugin, this may not work with your RELEASE

Running post_install.sh
Updating iocage-plugins repository catalogue...
iocage-plugins repository is up to date.
All repositories are up to date.
Checking integrity... done (0 conflicting)
The most recent versions of packages are already installed
jellyfin_enable:  -> YES
Starting jellyfin.

Admin Portal:
http://192.168.0.195:8096

Doc URL:
https://github.com/Thefrank/jellyfin-server-freebsd

[Thefrank]

@regimeG above should be a much smoother solution for the future :)

[regimeG]

First of all, thank you for the great help. Jellyfin has become very, very important to me and I now have a TrueNAS Mini+. Expensive enough that I have no other alternative at the moment. One-click solution via plugin was extremely attractive to me, so I went with TrueNas. I never intended to operate outside of the GUI. So I don't know if I have a repo, where it is or how to deal with it. My system consists of the pure TrueNAS Core and your link to install Jellyfin. ...just so you know what my level of knowledge is.

For now, please let's go through your instructions step by step.

How exactly do I add an index to my repo?

[spz2k9]

@Thefrank adding the INDEX file could be an option... not sure if it would break something on TrueNas end as they're the one that control the INDEX file and none of the other plugins have one.

Also they merged the "new" 13.2 plugin last week so the plugin should be working in the next release if it's not already working.

[regimeG]

So I could switch back to the community plugin? That would of course be the best solution. But would the configuration be adopted? Because I have currently installed Jellyfin via your link (fetch https://raw.githubusercontent.com/spz2k9/iocage-plugin-jellyfin/master/jellyfin.json
iocage fetch -P ./jellyfin.json --name jellyfin
rm ./jellyfin.json)

[Thefrank]

The community plugin will be the best and easiest until iXsystems gets rid of plugins which could be as soon as the next minor release but more likely the next major release.

Most simple: You can export (or just copy out) your settings and import them into the plugin.
Best: If you mounted in a dataset for your configuration/settings/cache just mount that into the new jail.

[regimeG]

What will replace the plug-in system afterwards? How will all the people who use Nextcloud, Plex or Syncthing, for example, continue to run these important services?

[regimeG]

Ok, I'm giving up at this point. Maybe the language barrier is too great for me to express myself clearly, or maybe I just don't understand you.

I can't find an export function for the Jellyfin settings, nor do I understand what you mean by "mount in a dataset". I must really be too stupid.

I just leave everything as it is and hope that the security holes are not exploited for as long as possible.

I have to admit, I'm pretty down after you described the perspective for TrueNAS Core and the plugins. I'll pop in here from time to time and see if there's any news. Maybe it won't be as bad as you fear.

Sorry for the inconvenience and thanks a million for your patience.

[regimeG]

What will replace the plug-in system afterwards? How will all the people who use Nextcloud, Plex or Syncthing, for example, continue to run these important services?

Ok, I found something about it myself.
https://www.truenas.com/blog/the-future-of-truenas-plugins-is-apps/