I uninstalled the plugin and am getting an error attempting to reinstall see below missing user jellyfinserver?

[pasha-19]

Error: (PlugnName) had a failure Exception: RuntimeError Message: Last 10 lines: Traceback (most recent call last): File "/usr/local/bin/jellyfin_updater", line 138, in < module > InstallOrUpdate() File "/usr/local/bin/jellyfin_updater", line 132, in InstallOrUpdate InstallService() File "/usr/local/bin/jellyfin_updater", line 106, in InstallService raise Exception('Failed to get GitHub url...') Exception: Failed to get GitHub url... pw: user `jellyfinserver' does not exist Partial plugin destroyed

If it matters in the original install I changed user jellyfinserver to jellyfin when I assigned a password; I hope that did not break the reinstall.

[Thefrank]

@pasha-19 Are you using TrueNAS? If yes...

Changing the username likely didn't help but

I think the main issue is that the plugin tries to download a package from this repo and not use the official FreeBSD ports mirror. This was fine until jellyfin was added to the ports system. It is much easier and safer to pkg install ... than to have a script grab a random pkg from a random repo.

I do not produce a pkg anymore and the plugin will need to be updated to reflect that.

CC @spz2k9 for updating plugin, also ffmpeg 6.0 is in ports and might resolve some hardware issues.

[spz2k9]

Oh didn't know the pkg wasn't produced anymore. I'll check to update the plugin to take the pkg from the repo since it's been updated in the quarterly. I should be able to do a patch by the weekend.

[pasha-19]

Yes, TrueNAS Core fully updated.

I also created a user and group using UID and GID 710 in TrueNAS Core proper to set security in the main pool that seemed to suffice across the mount point for the jail. I deleted that user and group and am attempting to install again. From what you say it will fail and I will wait for an update this weekend. Update; it failed as expected. Thanks for the quick response.

For the sake of clarity (this may be normal meaning I did not know any better and learned something) the old plugin when I installed it used UID/GID 710 for jellyfinserver, if i remember correctly; the newly installed plugin uses UID/GID 868 for jellyfin in the jail. This time during the initial web configuration I left jellyfinserver the default with no password (temporarily). I then, after logging in, created jellyfin as a separate administrator. I tried to disable jellyfinserver inside jellyfin web interface logged on as jellyfin but when that did not appear to work I added a password to jellyfinserver. The moral of this story appears to be to check using the jail's shell option to determine what the UID and GID are associated with jellyfin and which are used recursively from /var/db/????. In the old install I believe that was /var/db/jellyfinserver and in the new install in my case is /var/db/jellyfin.

[regimeG]

Does this mean the community plugin in TrueNAS can not be updated by just clicking "update"? My installation seams to be broken as well after updating a few minutes ago. I can't get any connection to my Jellyfin Server. Can you please guide me to get a proper installation?
Thanks in advance!

[Thefrank]

I have add the pkg from the pkg mirror to the repo release. This should (hopefully) solve the issue until the TrueNAS plugin is updated to use FreeBSD pkg mirror instead of this repo

EDIT: this is actually jellyfin-10.8.10_1.pkg but named jellyfin-10.8.10.pkg to hopefully prevent the script from getting confused

[regimeG]

Thank you very much! I updated again and the installation went through flawless. But I still can't reach the Server. Do you have any suggestions?

[spz2k9]

Normally the admin web page should be available in the plugin section. Can you verify if the link of that page is valid?

[regimeG]

Yes, the IP address displayed is the same as the IP address in the router reserved specifically for Jellyfin. The router also shows the server as active. Nevertheless, Firefox cannot establish a connection. It was the same with the last update and I had to reinstall everything. I would like to avoid that this time if possible.

Thanks for the support ;-)

[spz2k9]

@Thefrank I just updated the install script and removed the updater script so the packages all comes from the Repo now.

[spz2k9]

@regimeG That's weird... maybe it's a problem with the commands in the old install script. Can you open a terminal in this jail and do a 'top' command to see if the jellyfin server process is running ?

[regimeG]

There are just a few processes visible for me. I can identify "top" of course, "syslogd", "csh", "login", "cron" and three times "dhclient".

[regimeG]

@Thefrank I just updated the install script and removed the updater script so the packages all comes from the Repo now.

Should I run the update again?

[spz2k9]

I don't think the update will fix this problem since update only update the pkg installed from the official repo... I've sent a pull request for this like 5 mins ago... but it won't be included in TrueNas until the next release (probably in two weeks) and that's if someone from TrueNas Team merge my pull request.

The fix without recreating the jail would be to run thoses commands :

pw group mod video -m jellyfin

sysrc -f /etc/rc.conf jellyfin_enable="YES"

service jellyfin start 2>/dev/null

[regimeG]

Should the commands being executed directly in the shell from the jail or in the global shell of TrueNAS?

[spz2k9]

They have to be executed inside the jail... it can be done with a shell connected to the jail.... or in the jail UI there's a shell option to open a shell for that jail.

[regimeG]

Ok, after inserting the first command the following comes back: pw: user 'jellyfin' does not exist

[spz2k9]

oh okay... so you'll need to run this one first :

pkg install -y jellyfin

[regimeG]

Just to be sure. In addition to the installed community plugin?

[spz2k9]

Well you'll have both package the files should overrites themselves, but if you want to uninstall the community package first you'd do :

pkg remove -y jellyfinserver

Then install the official package and then the 3 other commands.

[regimeG]

Ok, all done.

[spz2k9]

Good, if everything went as planned... it should work now.

[regimeG]

There is a note that "allow_mlock=1" is important for using in a jail. Is it important or can we ignore it?

[spz2k9]

That's only usefull when creating the jail... since the jail is already created you'll only need the commands to configure and start the service.

[spz2k9]

I've reran the install and I now understand it's this message :

If you are running this in a jail please set "allow_mlock=1" or similar for this jail otherwise the program will fail to start.

You can ignore all those messages, thoses commands have already been ran at jail creation.

[regimeG]

Ok, thank you so much for your patience! At least I can connect to the server but have to reconfigure everything again. I'll do it again and lets hope that the next update will be done without that issue ;-)
Glad to have Jellyfin for my NAS!

[spz2k9]

No probl. Normally the update button from TrueNas UI should update correctly when the pull request on the plugin will be merge in TrueNas. It will be in the next TrueNas update if I've made the fix in time.

[regimeG]

How can I support your effort around Jellyfin and TrueNAS coming together?

[spz2k9]

It's all good... the plugin had been approved in the past, I don't think they'll mind getting an update... it's just a mater of time before they approve the update.

[pasha-19]

I took a chance; I am successfully reinstalled (reconfiguration starts tomorrow).

Thanks