rnica Posted Monday at 10:41 PM Posted Monday at 10:41 PM 18 hours ago, TwoStroke said: Was really hoping that this update, including automatic GPU detection, would resolve the Plex Intel GPU issues that have plagued HexOS since the beginning. No luck 😞 Still seeing the same issues. Jan 05, 2026 13:47:09.614 [139751593986872] DEBUG - [Req#cdc/Transcode] Codecs: testing hevc (decoder) with hwdevice vaapi Jan 05, 2026 13:47:09.614 [139751593986872] DEBUG - [Req#cdc/Transcode] Codecs: hardware transcoding: testing API vaapi for device '/dev/dri/renderD128' (Intel Raptor Lake-S GT1 [UHD Graphics 770]) Jan 05, 2026 13:47:09.614 [139751593986872] ERROR - [Req#cdc/Transcode] [FFMPEG] - Failed to initialise VAAPI connection: -1 (unknown libva error). Jan 05, 2026 13:47:09.614 [139751593986872] DEBUG - [Req#cdc/Transcode] Codecs: hardware transcoding: opening hw device failed - probably not supported by this system, error: I/O error Jan 05, 2026 13:47:09.614 [139751593986872] DEBUG - [Req#cdc/Transcode] Could not create hardware context for hevc Back to uninstalling Plex and waiting for the next round of updates! Is this with the HEXOS version of plex or the TrueNAS version with the "Plex Configuration Storage" Type on a ixVolume ?
TwoStroke Posted Tuesday at 01:07 AM Posted Tuesday at 01:07 AM (edited) 2 hours ago, rnica said: Is this with the HEXOS version of plex or the TrueNAS version with the "Plex Configuration Storage" Type on a ixVolume ? This is with the HexOS curated version of Plex. As far as I know, from previous threads, the TrueNAS Version configured using an ixVolume works because it has to do with a permissions error in the config. I just have Plex running on a different server and refuse to migrate it until the HexOS one-click app works as it should. Edited Tuesday at 01:08 AM by TwoStroke
rnica Posted Tuesday at 02:37 AM Posted Tuesday at 02:37 AM 1 hour ago, TwoStroke said: This is with the HexOS curated version of Plex. As far as I know, from previous threads, the TrueNAS Version configured using an ixVolume works because it has to do with a permissions error in the config. I just have Plex running on a different server and refuse to migrate it until the HexOS one-click app works as it should. Thank you, wanted to make sure it was the same problem.
Serpents_Smile Posted yesterday at 09:34 AM Posted yesterday at 09:34 AM Are there plans to add other MFA possibilities than Google Authenticator? I'd really rather not have to use that app.
YONI Posted 18 hours ago Posted 18 hours ago My experience has been pretty bad. I can’t access the NAS from the Dashboard after the TrueNAS 25.10 update, only through the TrueNAS web interface. I tried restarting the NAS and reconnecting the RJ cable, but it still doesn’t detect it. It just says: “This server is not available.” Has anyone else experienced this?
rnica Posted 13 hours ago Posted 13 hours ago 4 hours ago, YONI said: My experience has been pretty bad. I can’t access the NAS from the Dashboard after the TrueNAS 25.10 update, only through the TrueNAS web interface. I tried restarting the NAS and reconnecting the RJ cable, but it still doesn’t detect it. It just says: “This server is not available.” Has anyone else experienced this? I've heard that the hexos website caches info. Have you tired clear cache by use Ctrl+R, CTRL+SHIFT+R or CTRL+F5 ?
Todd Miller Posted 13 hours ago Posted 13 hours ago Additionally (though it was a lot more common earlier last year), there was a problem where the web UI would just stop listening sometimes. I reported this several times and it has really gotten better but I still hold out hope the local UI will fix this completely. I don't have any actual proof of this but rather just the same fact that TrueNAS web interface still always connected. I think my record for server not available was over a three day weekend but bright and early monday morning I was connected again without doing anything.. Sorry that isn't very helpful but at least for me the connection always returned, just never as fast as I would have liked. And it was never addressed as to if these were planned datacenter outages or if someone just tripped on a cord. Yes Eshtek, I know that cord tripping thing isn't likely but if you never explain what's happening you leave the door wide open feo me to make up my own explanation.
Recommended Posts