Mika<p>I... actually managed to do this and it was somewhat messy to get through with it, but I did it. My 'stoppers' initially were simply needing to update some of the <a href="https://sakurajima.social/tags/Jellyfin" rel="nofollow noopener noreferrer" target="_blank">#Jellyfin</a>'s <code>xml</code> configs for any wrong/old paths/values, and lastly, the <a href="https://sakurajima.social/tags/SQLite" rel="nofollow noopener noreferrer" target="_blank">#SQLite</a> DBs themselves which had old paths as well - most of which were easy to fix as they're <code>text</code> values, but some were (JSON) <code>blob</code>s, using the same extension on <a href="https://sakurajima.social/tags/VSCode" rel="nofollow noopener noreferrer" target="_blank">#VSCode</a>, this wasn't that hard to do either by simply exporting the blob, editing the blob's JSON text value, and reimporting the blob to the column. Oh, I also had to update <code>meta.json</code><span> files of all plugins I've installed to point to the new path to their logos.<br><br>Now my Jellyfin </span><a href="https://sakurajima.social/tags/LinuxServer" rel="nofollow noopener noreferrer" target="_blank">#LinuxServer</a>.io container sitting in an unprivileged (<a href="https://sakurajima.social/tags/Debian" rel="nofollow noopener noreferrer" target="_blank">#Debian</a> <a href="https://sakurajima.social/tags/Linux" rel="nofollow noopener noreferrer" target="_blank">#Linux</a>) <a href="https://sakurajima.social/tags/LXC" rel="nofollow noopener noreferrer" target="_blank">#LXC</a> container on <a href="https://sakurajima.social/tags/Proxmox" rel="nofollow noopener noreferrer" target="_blank">#Proxmox</a> is set up with hardware transcoding using the <a href="https://sakurajima.social/tags/AMD" rel="nofollow noopener noreferrer" target="_blank">#AMD</a> Ryzen 5 5600G onboard iGPU (cos I'm getting impatient in waiting for my <a href="https://sakurajima.social/tags/Intel" rel="nofollow noopener noreferrer" target="_blank">#Intel</a> <a href="https://sakurajima.social/tags/ArcA380" rel="nofollow noopener noreferrer" target="_blank">#ArcA380</a> to arrive). I'll update my <a href="https://sakurajima.social/tags/ErsatzTV" rel="nofollow noopener noreferrer" target="_blank">#ErsatzTV</a> container to do the same. Everything's perfect now, 'cept, I still wouldn't recommend users to stream Jellyfin on the web or a web-based client using transcoding, cos while the transcoding itself is perfect, Jellyfin seems to have an issue (that I never got on <a href="https://sakurajima.social/tags/Plex" rel="nofollow noopener noreferrer" target="_blank">#Plex</a><span>) whereby the subtitle would desync pretty consistently if not direct playing - with external or embedded subs, regardless. Dk if that can ever be fixed though, considering the issue has been up since 2023 with no fix whatsoever.<br><br>There's also a separate issue I'm having where Jellyfin does not seem to support discovering/serving media files that are contained in a symlink directory (even though there were some people on their forums reporting in the past that it should) - I've reported it last week, but it's not going anywhere for now. Regardless though, I'm absolutely loving Jellyfin despite some of its rough edges, and my users are loving it too. I think I've considered myself 'migrated' from Plex to Jellyfin, but I'll still keep Plex around as backup for these 2 cases/issues I've mentioned, for now.<br><br></span>🔗 <a href="https://github.com/jellyfin/jellyfin-web/issues/4346" rel="nofollow noopener noreferrer" target="_blank">https://github.com/jellyfin/jellyfin-web/issues/4346</a><span><br><br></span>🔗 <a href="https://github.com/jellyfin/jellyfin/issues/13858" rel="nofollow noopener noreferrer" target="_blank">https://github.com/jellyfin/jellyfin/issues/13858</a><span><br><br>RE: </span><a href="https://sakurajima.social/notes/a6j9bhrbtq" rel="nofollow noopener noreferrer" target="_blank">https://sakurajima.social/notes/a6j9bhrbtq</a></p>