Jellyfin Forum
Unable to determine image dimensions for X: InternalError - Printable Version

+- Jellyfin Forum (https://forum.jellyfin.org)
+-- Forum: Support (https://forum.jellyfin.org/f-support)
+--- Forum: Troubleshooting (https://forum.jellyfin.org/f-troubleshooting)
+---- Forum: Media Scanning & Identification (https://forum.jellyfin.org/f-media-scanning-identification)
+---- Thread: Unable to determine image dimensions for X: InternalError (/t-unable-to-determine-image-dimensions-for-x-internalerror)



Unable to determine image dimensions for X: InternalError - lkmhaqer - 2025-06-05

Hello,

     I am running into an error, it only seems to happen when the library scans/initially imports the media. The bug appears to be the primary poster image for a movie is missing. Looking at the logs I see a few lines that stick out:

Code:
[16:42:46] [ERR] [173] Jellyfin.Drawing.Skia.SkiaEncoder: Unable to determine image dimensions for /media/downloads/movies/The.Guest.2014.1080p.BluRay.x264/The.Guest.2014.1080p.BluRay.x264.jpg: InternalError
[16:42:46] [ERR] [166] Microsoft.AspNetCore.Server.Kestrel: Connection id "0HND364REK35T", Request id "0HND364REK35T:00000002": An unhandled exception was thrown by the application. System.InvalidOperationException: Response Content-Length mismatch: too few bytes written (25 of 893053).



    If I go back and manually upload this same image, in the UI, it appears in the library without issues. This happens on my 10.10.7 version of jellyfin, I have another instance using this same media library that does not appear to have the bug. This non-bugged instance is running version 10.10.3. Let me know if I can provide any other details. I see also there is some reference to this issue on the last post of this thread:

https://forum.jellyfin.org/t-photo-library-scan

/lkmhaqer


RE: Unable to determine image dimensions for X: InternalError - theguymadmax - 2025-06-05

What server version are you on?


RE: Unable to determine image dimensions for X: InternalError - lkmhaqer - 2025-06-06

I have two versions running, I see the issue with 10.10.7, but not in 10.10.3.