Jellyfin 10.11.0 Update Summary and Compatibility Notes

Jellyfin 10.11.0 introduces a major migration to Entity Framework Core, new performance optimizations, and several breaking changes that require attention before upgrading.


Upgrade Requirements

  • Upgrade first to Jellyfin 10.10.7.
  • Create a full backup of configuration, database, and metadata.
  • The EF Core migration can take hours on large libraries.
  • A new Startup UI now displays migration progress.
  • The server requires at least 2 GB of free disk space — startup will abort otherwise.

Interrupting the migration may corrupt the database. Let it complete.


Major Changes

  • EF Core migration — modern ORM backend, faster development, PostgreSQL-ready.
  • ARM32 removed — only ARM64 OS supported.
  • Internal TLS/SSL deprecated — use a reverse proxy (nginx, caddy, traefik).
  • Built-in backup/restore tools added.
  • Aggressive caching for improved performance (higher RAM usage).
  • Enhanced search, Favorites page, HEVC + Firefox playback support.
  • FFmpeg 7.1, HDR tone-mapping, and AV1 decoding.
  • Deprecated API methods will be removed in 10.12.0.

Full changelog: GitHub → v10.11.0
Official post: Jellyfin Blog


Tvdb Plugin Compatibility Issue

On my setup — Jellyfin running inside a Debian 12 LXC on Proxmox VE — the upgrade initially failed with the following error:

[ERR] Kestrel failed to start! Invalid address or port bind...
System.MissingMethodException: ILocalizationManager.GetCountries()
   at Jellyfin.Plugin.Tvdb.TvdbClientManager..ctor(...)

In my case, the issue was caused by an outdated TheTVDB plugin. Version 20 is required for Jellyfin 10.11.0, but it cannot be installed on earlier Jellyfin versions.

What worked for me:

  1. Restored the backup.
  2. Uninstalled the TheTVDB plugin (older version).
  3. Updated Jellyfin again via apt upgrade.
  4. After removing the plugin, the migration and startup completed successfully.

Summary

  • Backup and upgrade to 10.10.7 first.
  • Uninstall TheTVDB (v20 required for 10.11.0).
  • Let the migration finish without interruption.
  • Use reverse proxies for TLS instead of internal SSL.
  • ARM32 hardware is no longer supported.