Highlights
- Jellyfin 12 compatibility hardening: cached image proxy requests now normalize older lowercase
api_keyimage URLs to Jellyfin's currentApiKeyquery parameter. - Server Test now validates the saved API key against Jellyfin's authenticated
/System/Infoendpoint instead of public info. - Server Test now returns faster, clearer messages when the configured Jellyfin URL cannot be reached from where Pixelfin is running, especially inside Docker.
- Backwards compatibility is preserved for Jellyfin 10.11 by keeping the existing modern and legacy token headers.
Docker Images
Published multi-architecture images for linux/amd64 and linux/arm64:
ghcr.io/nothing2obvi/pixelfin:v1.0.7ghcr.io/nothing2obvi/pixelfin:latest
Notes
If Test reports that Pixelfin cannot reach Jellyfin, that is usually a Docker/network reachability issue with the configured Server URL, not necessarily a bad API key or Jellyfin 12 incompatibility.