![]() |
New Jellyfin Server/Web release: 10.10.7 - Printable Version +- Jellyfin Forum (https://forum.jellyfin.org) +-- Forum: Announcements (https://forum.jellyfin.org/f-announcements) +--- Forum: Project Announcements (https://forum.jellyfin.org/f-project-announcements) +--- Thread: New Jellyfin Server/Web release: 10.10.7 (/t-new-jellyfin-server-web-release-10-10-7) |
New Jellyfin Server/Web release: 10.10.7 - ReleaseBot - 2025-04-05 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 - UPGRADING IS IMPORTANT. Important Note: 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. As always, please ensure you stop your Jellyfin server and take a full backup before upgrading! You can find the full changelogs on the GitHub releases for the server repository and the web repository. Release prepared with <3 by @joshuaboniface, the rest of the Jellyfin team, and contributors like you. Happy watching! RE: New Jellyfin Server/Web release: 10.10.7 - Tim - 2025-04-05 Great work everyone! RE: New Jellyfin Server/Web release: 10.10.7 - kandykarter - 2025-04-05 Before I take the plunge, the trusted proxies section: Does it require ip addresses, or the subdomain like jellyfin.example.com, or what? RE: New Jellyfin Server/Web release: 10.10.7 - TheDreadPirate - 2025-04-05 (2025-04-05, 08:01 PM)kandykarter Wrote: Before I take the plunge, the trusted proxies section: Does it require ip addresses, or the subdomain like jellyfin.example.com, or what? You use the IP address of the host running the reverse proxy. RE: New Jellyfin Server/Web release: 10.10.7 - jessielw - 2025-04-05 Good work everyone! RE: New Jellyfin Server/Web release: 10.10.7 - TheDreadPirate - 2025-04-05 @kandykarter - Clarification. You can use the HOSTNAME of the reverse proxy as well. You can also use CIDRs. But you do NOT put your DOMAIN name in the known proxies field. RE: New Jellyfin Server/Web release: 10.10.7 - Host-in-the-Shell - 2025-04-05 Upgraded without issue after updating the known proxies section; all went smooth without any troubles. Thanks for the great work, keep it up! RE: New Jellyfin Server/Web release: 10.10.7 - frostywite - 2025-04-05 Updated from .6 to .7 running behind Nginx proxy. Curious to read the GHSA. Is this an issue if the Jellyfin Server and proxy are on the same machine or more if someone is running a separate proxy server? RE: New Jellyfin Server/Web release: 10.10.7 - jpbaril - 2025-04-05 (2025-04-05, 08:56 PM)TheDreadPirate Wrote: You can also use CIDRs. I think this should also be clarified in Jellyfin's admin networking 'known proxies' field description. RE: New Jellyfin Server/Web release: 10.10.7 - AlexKalopsia - 2025-04-05 Can someone explain what needs to be done in order to set trusted proxies when using JF behind nginx reverse proxy? |