v2.4.12.1

v2.4.12.1 — Diagnostic prerelease (NOT in catalog)

One-off prerelease for issue #35 follow-up reported by @FsxShader2012 — external login + 2FA succeeds at the challenge page but the post-verify navigation to /web/ lands on Jellyfin Web's "Server not available" screen instead of the dashboard. Could not repro on my own Cloudflare + nginx setup; this is the speculative fix.

Fix

challenge.html now clears sessionStorage.__tfa_pending at the top of its inline script. The flag is set by inject.js on the previous page to short-circuit the post-login dashboard API barrage during the redirect window — but the challenge page does not load inject.js, so the inject.js-side clear-on-Verify-success never fires for users who complete 2FA through this page. The flag persists, and when the post-verify navigation re-mounts inject.js on /web/, every Jellyfin Web API call gets short-circuited locally — surfacing as "Server not available" because the apiclient interprets persistent non-2xx as the server being unreachable.

Clearing the flag at the top of challenge.html means it's gone before window.location.href = '/web/index.html' fires, so the post-2FA dashboard load is unblocked.

Secondary fix — release.yml 4-part tag truncation

Tag derivation was TAG="v${VERSION%.*}" which stripped the last .N segment unconditionally, mangling 4-part prereleases (2.4.10.1 → v2.4.10). This is exactly why v2.4.10.1's artifacts overwrote v2.4.10 stable's release page. Fixed to TAG="v${VERSION%.0}" — strip trailing .0 only. Verified by this very release publishing to v2.4.12.1 instead of v2.4.12.

Same install steps as v2.4.10.1

NOT going into the catalog (manifest.json). To test, download the .zip from this release page and replace your existing /config/plugins/Jellyfin Security_*/TwoFactorAuth/ contents (rename or remove the old plugin directory first to avoid the HibpService DI conflict on boot). Restart Jellyfin. If the dashboard now loads after external 2FA, this becomes the basis for a v2.4.13.0 stable release.

If the symptom persists please paste any browser devtools console errors and a screenshot of the network panel right after the "Server not available" screen surfaces — that'll pin the actual cause.