2024-11-21, 04:48 PM
(2024-11-21, 03:59 PM)TheDreadPirate Wrote: Before proceeding, you SHOULD be providing a host path for /config and /cache. That is where your permanent Jellyfin data resides and you should not let Docker/TrueNAS automatically manage it. I have seen users unknowingly run a command that wiped out their Jellyfin data. And I'm thinking that is what TrueNAS is warning about right now.
Pull your data out of the paths that TrueNAS specific, put them in a folder that YOU manage, and then define those paths in the container config.
As it turned out, my having a specific ACL set for the host paths option (which if I'm not mistaken accounts for the /config and /cache folders) seems to have been causing some sort of conflict in the system. I deselected having a specific ACL set and associated the host paths option with my TrueNAS "apps" group, which has all the rights that Jellyfin needed. That allowed me to update Jellyfin and to set the GPU allocation setting. I restarted Jellyfin and now everything works flawlessly. Transcoding works with no problem at all from outside my network (watched a few Looney Tunes cartoons on my phone at work LOL) on all various codecs.
Happy to report that thanks to you pointing me in the right direction, my issue looks to have been resolved.