Repository navigation
JellyFreedom 0.8.0
JellyFreedom now works with Jellyfin 12. Every install made since Jellyfin 12.0 shipped on
2026-09-08 got Jellyfin 12, and on 0.7.6 Jellyfin refused every request it made; upgrading an
existing Jellyfin to 12 did the same. Tested against Jellyfin 10.11.11 and 12.4, and across an
in-place upgrade from one to the other.
Fixed
-
Jellyfin 12 refused JellyFreedom's API key. JellyFreedom sent the key in the legacy
X-Emby-Tokenheader and identified its login call withX-Emby-Authorization. Jellyfin 12
stops reading both —EnableLegacyAuthorizationdefaults tofalse, and an upgrade from
10.11 switches it off — so every call went out unauthenticated: the connection test reported
the key was rejected, library scans did nothing, sessions and user lists came back empty,
accounts imported from Jellyfin could not log in, and.strmfiles were written but never
picked up. Fixed by Marco Trevisan (#47), reported in #46.Every Jellyfin request now carries
Authorization: MediaBrowser Client="JellyFreedom", Device="Orchestrator", DeviceId="jellyfreedom-orchestrator", Version="1.0", Token="…", which
Jellyfin 10.11 accepts too. The login call identifies the client the same way but sends no
token, since there is no key yet. The old headers are no longer sent at all. -
Stopping playback never freed the torrent. The PlaybackStop webhook had three faults, on
every Jellyfin version, and each step gave up without a word in the log:- it looked the item up with
/Items/{id}, which Jellyfin 10.11 and 12 answer with 400 for
an API key with no user; - had that answered, it read the URL inside the
.strmrather than the.strm's path, so
it could never match a library entry; - its "is anyone else still watching?" check compared the webhook's dashed item id with
Jellyfin's undashed ones, so it never matched either, and on any error it answered "no".
The torrent is now dropped when the last viewer stops, and kept while anyone else is
watching, whenever Jellyfin cannot be asked, and while another episode shares it. Each step
that keeps a torrent says why in the log. TorrServer's idle timeout was freeing these
torrents all along, which is why nobody noticed. - it looked the item up with
-
jellyfreedom doctorcalled Jellyfin healthy while it refused every request. It only
checked the one endpoint that needs no key. It now shows Jellyfin's version, checks that
Jellyfin accepts the orchestrator's key, and reports a Jellyfin that is still starting — or
migrating its database after an upgrade — as starting rather than down. -
jellyfreedom --updatewould install an older release. It only checked whether the
downloaded version was different, so a box on a newer build than the latest release — a
nightly, or one built from source — was taken back to that release. It now orders versions
the way the dashboard does, and refuses anything older or anything it cannot place. A nightly
ranks above the release it was built after, so switching from nightly back to stable waits
until stable catches up, as the nightly release notes always said it would.
JELLYFREEDOM_ALLOW_DOWNGRADE=1installs an older release on purpose;JELLYFREEDOM_FORCE=1,
whichrepairuses, still only reinstalls the same version. -
The VPN watchdog could restart TorrServer under a transcode. It defers restarts while
someone is watching, and asked only Jellyfin's sessions. A transcode Jellyfin has lost track
of, after its client disconnected or across a Jellyfin restart, keeps reading the stream with
no session behind it, so it looked like nobody was watching. The orchestrator now counts the
streams it is proxying as well, torrent and web source alike.
Added
sudo jellyfreedom webhooksets up Jellyfin's Webhook plugin for you: the Playback Stop
event on movies and episodes, the payload template and the shared secret. It reads the result
back to confirm Jellyfin kept it, and leaves your other webhooks alone. The dashboard's webhook
card now shows the template too, which it had left out although every call fails without it.tests/jellyfin/test_jellyfin_compat.sh, for contributors: runs the Jellyfin client and the
webhook path against throwaway Jellyfin servers of any version, as an ordinary user, and
measures which Jellyfin tasks open the.strmURLs — the requests that, on a real install,
each resolve a torrent through the VPN. On 10.11.11 and 12.4 only playback does.
Upgrading
- On Jellyfin 12, if you turned
EnableLegacyAuthorizationback on to keep 0.7.6 working,
turn it off again after updating. - The webhook needs a payload template, which the setup instructions never mentioned; without
one, Jellyfin sends a body the orchestrator rejects. If you set the webhook up by hand, run
sudo jellyfreedom webhookonce after updating: it fixes your destination and leaves your
other webhooks alone. See first-run.md §8.
Install
curl -fsSL https://github.com/MoonTheRipper/JellyFreedom/releases/latest/download/get.sh | sudo bashVerify downloads against SHA256SUMS:
sha256sum -c SHA256SUMS --ignore-missingArtifacts are signed with build provenance — verify with:
gh attestation verify jellyfreedom-0.8.0-linux-amd64.tar.gz --repo MoonTheRipper/JellyFreedom