Summary: The latest Jellyfin release, version 10.10.7, enhances security and functionality for self-hosting enthusiasts. This update includes crucial bug fixes and configuration adjustments to ensure an optimal streaming experience. Back up your server and stay informed with our comprehensive guide below.
Latest Jellyfin Release: Version 10.10.7
We are excited to introduce the stable release of Jellyfin, version 10.10.7! This minor update focuses on enhancing your self-hosting experience by tackling various bugs and implementing essential security fixes. As a dedicated self-hosting media server solution, Jellyfin aims to improve stream quality and user engagement.
Always remember to stop your Jellyfin server and create a full backup before proceeding with the upgrade!
For further discussions about this release, visit our official forum here.
Key Considerations for Self-Hosters
- Users with configurations behind a reverse proxy that do not explicitly set trusted proxies must take note: this configuration will no longer work after the upgrade. Since this was never officially supported, please ensure that your setup complies with the new requirements. Refer to the updated documentation for further insights.
Changelog Highlights
🔒 Security Enhancements
Note: GitHub Security Advisories (GHSAs) will be released seven (7) days post this update.
📈 General Modifications
- Addressed a regression in “Search for missing metadata” that prevented the correct handling of casts with multiple roles [PR #13720], by @Lampan-git.
- Implemented cloning of fallback audio tags instead of utilizing ATL.Track.set [PR #13694], by @gnattu.
- Backported API enum changes from 10.11 [PR #13835], by @nielsvanvelzen for future-proofing.
- Enhanced support for a broader range of rating formats [PR #13639], by @IDisposable.
- Resolved a stack overflow issue in MediaSourceCount [PR #12907], by @JPVenson.
- Upgraded LrcParser to version 2025.228.1 [PR #13659], by @congerh.
- Incorporated Role and SortOrder in MergePeople to rectify issues with “Search for missing metadata” [PR #13618], by @Lampan-git.
- Ensured correct deletion of children from cache upon a parent’s deletion [PR #13601], by @Bond-009.
- Fixed an issue that caused year-only values to overwrite PremierDate [PR #13598], by @IDisposable.
- Modified Windows handling to wait for ffmpeg to exit before attempting to delete the concat file [PR #13593], by @Bond-009.
- Improved 4K movie filtering in collections [PR #13594], by @theguymadmax.
- Removed empty ParentIndexNumber workaround [PR #13611], by @Shadowghost.
- Updated dependency z440.atl.core to 6.20.0 [PR #13845], by @Shadowghost.
Conclusion
With Jellyfin version 10.10.7, users can expect a more seamless self-hosting experience. The meticulous focus on bug fixing and security fortifications ensures that your media streaming maintains optimal quality and performance. Always take the time to back up your configurations and familiarize yourself with the updated requirements for a hassle-free upgrade.
FAQs
1. How do I back up my Jellyfin server before upgrading?
To back up your server, you can copy the configuration folders and database files to a secure location. This ensures that you can restore your settings and media if anything goes wrong during the upgrade.
2. What happens if I don’t upgrade my Jellyfin server?
Failing to upgrade could leave your server vulnerable to security risks and may also prevent you from enjoying the latest features and optimizations, significantly affecting your user experience.
3. Can I customize my Jellyfin server’s configuration?
Yes, Jellyfin allows extensive customization options for users familiar with self-hosting. You can adjust settings to optimize performance based on your specific hardware and streaming needs.