We are pleased to announce the latest stable release of Jellyfin, version 10.10.7! This minor release brings several bugfixes to improve your Jellyfin experience. THIS IS A SECURITY RELEASE - UPGRADIN
Configurations behind a reverse proxy that did not explicitly configure trusted proxies will not work after this release. This was never a supported configuration, so please ensure you correct your configuration before upgrading. See the updated docs here for more information.
Security
Fix validation of API parameters to FFmpeg [GHSA-2c3c-r7gp-q32m], by @Shadowghost
Fix trusting forward headers if none are configured [GHSA-qcmf-gmhm-rfv9], by @JPVenson
Note: GHSAs will be published seven (7) days after this release.
General Changes
Fix regression where "Search for missing metadata" not handling cast having multiple roles [PR #13720], by @Lampan-git
Clone fallback audio tags instead of use ATL.Track.set [PR #13694], by @gnattu
Backport 10.11 API enum changes [PR #13835], by @nielsvanvelzen
Support more rating formats [PR #13639], by @IDisposable
Fix stackoverflow in MediaSourceCount [PR #12907], by @JPVenson
Upgrade LrcParser to 2025.228.1 [PR #13659], by @congerh
Include Role and SortOrder in MergePeople to fix "Search for missing metadata" [PR #13618], by @Lampan-git
Delete children from cache on parent delete [PR #13601], by @Bond-009
Fix overwrite of PremierDate with a year-only value [PR #13598], by @IDisposable
Wait for ffmpeg to exit on Windows before we try deleting the concat file [PR #13593], by @Bond-009
Fix 4K filtering when grouping movies into collections [PR #13594], by @theguymadmax
Remove empty ParentIndexNumber workaround [PR #13611], by @Shadowghost
Update dependency z440.atl.core to 6.20.0 [PR #13845], by @Shadowghost
updated on mint this weekend; admittedly it's not a big library (mostly just for me and my family) but it was pretty painless. i put in my trusted proxies ahead of time and backed up /etc/jellyfin and /var/lib/jellyfin ahead of time. no problems at all.
My friend who’s been praising Plex for years and making fun of me for using Jellyfin instead just told me the other day he’s thinking about switching. It’s their new subscription fee that finally did it. xD
It's what made me switch this weekend. I didn't know I missed the "Episode ends on (time)" functionality until I got it with Jellyfin, Holy shit that's so nice ❤️
Really looking forward to 10.11 when the EFCore functionality is in place so I can run it with PostgreSQL and actually backup the DB properly and also have proper replication for a hot standby.
As far as I can understand, even with EFCore in 10.11, there still will only sqlite be available as a database backend. There are plans for postgresql and other types but it's a much more distant prospect.
Reference
I was imagining setting up an old laptop as a backup to my main server with PostgreSQL replication for the Jellyfin DB and some sort of file synchronization for media and metadata. I have yet to manually setup PostgreSQL replication outside of a cloud provider where the process is automated, so I was planning it as an interesting learning experience. However, from the post above, it seems I was misinformed about the timeframe of PostgreSQL support in Jellyfin.
Configurations behind a reverse proxy that did not explicitly configure trusted proxies will not work after this release. This was never a supported configuration, so please ensure you correct your configuration before upgrading. See the updated docs here for more information.
Thanks for pointing this out! I probably would have missed this, since I didn't expect such a change for a patch release.
Their documentation mentions:
For jellyfin to know which reverse proxy is trusted, the IP, Hostname or Subnet has to be set in the Known Proxies (under Admin Dashboard -> Networking) setting.
Does this really mean, that the only way to configure this is through the web UI? This is kind of a problem when deploying it, since without the reverse proxy I can't reach the Jellyfin server. Is there no way of doing this outside the web UI, via a config file or something?
Edit: Apparently the configuration for the proxies is stored in Jellyfin's network.xml config file. So it should be possible to do this without manually configuring it via the web UI.
Another edit: It works. Adding <KnownProxies>[proxy ip or hostname]</KnownProxies> in place of the empty <KnownProxies/> key to that config file does the trick.
Fuck no, ain't nobody got time for that! My self hosted stack has 40+ services. I lock them to minor releases (where semvers are used), deploy blind with automation, and fire alerts when breakages occur, which is thankfully rarely.
What you're suggesting works for small, very carefully curated environments. I grew past that years ago and doubly so when I had kids.
Not related to the server, but I was very happily surprised with the latest Roku Jellyfin channel. A complete refresh of everything and it's great to see it.
I can see them doing that, I use a DNS ad-block (Adguardhome) with plenty of filters and last night, I spotted that they were able to inject two ads (standard one to the right of the channels and one at the bottom below the menu for the new Minecraft movie when they changed my background. So, they are finding ways around this stuff. I simply disabled the Sponsored themes. We are on the fence about replacing the TV later this year but not 100% sure just yet. It's been quite buggy randomly rebooting when switching sources and other things.