No transcoding while streaming over internet?

[TheDreadPirate]

I don't use TrueNAS, so IDK. But that is the official image. But it also depends if TrueNAS tacks on a bunch of environment variables that could change how it behaves.

Are you able to list out all the environment variables used with the container?

[Spook50]

I don't use TrueNAS, so IDK.  But that is the official image.  But it also depends if TrueNAS tacks on a bunch of environment variables that could change how it behaves.

Are you able to list out all the environment variables used with the container?

My Jellyfin configuration shows no additional environment variables, though I'll have to do some homework to find out what default variables TrueNAS puts on it, since I'm trying to "re learn" what little Linux knowledge I had since last playing with any Linux distro ten years ago (which was on Ubuntu, and IIRC TrueNAS is Debian based).

[Spook50]

Fiddled around a bit more today finally (in other words, dug myself in deeper); and for some reason now I get no transcoding of any type at all, even within my own network. Here's the section that details the failure when I tried to play a 1080p H265 cartoon from the browser on my laptop.

ffmpeg version 6.0.1-Jellyfin Copyright © 2000-2023 the FFmpeg developers
  built with gcc 12 (Debian 12.2.0-14)
  configuration: --prefix=/usr/lib/jellyfin-ffmpeg --target-os=linux --extra-version=Jellyfin --disable-doc --disable-ffplay --disable-ptx-compression --disable-static --disable-libxcb --disable-sdl2 --disable-xlib --enable-lto --enable-gpl --enable-version3 --enable-shared --enable-gmp --enable-gnutls --enable-chromaprint --enable-opencl --enable-libdrm --enable-libxml2 --enable-libass --enable-libfreetype --enable-libfribidi --enable-libfontconfig --enable-libbluray --enable-libmp3lame --enable-libopus --enable-libtheora --enable-libvorbis --enable-libopenmpt --enable-libdav1d --enable-libsvtav1 --enable-libwebp --enable-libvpx --enable-libx264 --enable-libx265 --enable-libzvbi --enable-libzimg --enable-libfdk-aac --arch=amd64 --enable-libshaderc --enable-libplacebo --enable-vulkan --enable-vaapi --enable-amf --enable-libvpl --enable-ffnvcodec --enable-cuda --enable-cuda-llvm --enable-cuvid --enable-nvdec --enable-nvenc
  libavutil      58.  2.100 / 58.  2.100
  libavcodec    60.  3.100 / 60.  3.100
  libavformat    60.  3.100 / 60.  3.100
  libavdevice    60.  1.100 / 60.  1.100
  libavfilter    9.  3.100 /  9.  3.100
  libswscale      7.  1.100 /  7.  1.100
  libswresample  4. 10.100 /  4. 10.100
  libpostproc    57.  1.100 / 57.  1.100
[AVHWDeviceContext @ 0x561e0e5d0180] No VA display found for any default device.
Device creation failed: -22.
Failed to set value 'vaapi=va:,kernel_driver=i915,driver=iHD' for option 'init_hw_device': Invalid argument
Error parsing global options: Invalid argument

[Fate]

it probably can't access the igpu, have you passed it through?

I'm not sure if 8700 still works with qsv or if its only support via vaapi... can you test vaapi?

[TheDreadPirate]

The 8700 still works with QSV. In this case, I'm guessing that the GPU wasn't passed in.

[Spook50]

The 8700 still works with QSV.  In this case, I'm guessing that the GPU wasn't passed in.

I'm betting you're correct, as I don't recall performing any task related to passing in the GPU while installing & configuring TrueNAS or Jellyfin. I'm assuming that's not automated in any way so I'll do some homework tonight to see how to do it.

Very much learning as I go on this so the help has been much appreciated.

[Spook50]

Please correct me if I'm mistaken, but the GPU passthrough for TrueNAS (as far as Jellyfin is concerned) is the highlighted gpu.intel.com/i915 setting here (screenshot linked), correct?

https://drive.google.com/file/d/1YXTJ3Bh...sp=sharing

If yes, there's where I made my mistake, as I left it set to 0 when I installed Jellyfin.

Unfortunately, when I attempt to change it, TrueNAS does not apply the change; instead giving my this error message:

[EFAULT] Failed to apply ACLs to the following paths: 1) /mnt/dansnas/ix-applications/releases/jellyfin/volumes/ix_volumes/config: [EPERM] /mnt/dansnas/ix-applications/releases/jellyfin/volumes/ix_volumes/config: path contains existing data and force was not specified

Here's where it gets a little maddening though. In the Jellyfin configuration menu, there are no options I can see that pertain to the cache or config folders, much less any that have the FORCE option available. The FORCE checkbox on the top of my screenshot pertains to applying an ACL to the mount path and the host path.

Edit: I also get the same error when attempting to update Jellyfin as well. It would seem I may have screwed up in my ACL settings perhaps?

[TheDreadPirate]

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.

[Spook50]

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.