immich
immich copied to clipboard
[BUG] Content-Type doesn't match Reply body
The bug
Immich is working well but I'm seeing a lot of traces like this in the log:
[Nest] 409 - 12/10/2023, 5:01:07 PM ERROR [AssetService] Cannot create read stream for asset ec90291d-6d88-44ed-b3a4-ffedc27469f8
getAssetThumbnail
[Nest] 409 - 12/10/2023, 5:01:07 PM WARN [ExpressAdapter] Content-Type doesn't match Reply body, you might need a custom ExceptionFilter for non-JSON responses
The OS that Immich Server is running on
Ubuntu
Version of Immich Server
v1.90.2
Version of Immich Mobile App
v1.90.2
Platform with the issue
- [X] Server
- [ ] Web
- [ ] Mobile
Your docker-compose.yml content
.
Your .env content
.
Reproduction steps
.
Additional information
No response
Bump. Seeing the same on my setup. Seems to have been introduced with 1.90.2.
Fixed in #5595 - you guys can ignore this error
This does not appear to be fixed. Received this error just today.
#metoo
Fixed in #5595 - you guys can ignore this error Does this mean that the warning is still there, but we can ignore it, or that it doesn't suppose to appear?
Error is still present in v1.97.0
Have the same message in the logs in v1.95.1. It appears always when I click on "Albums" in the left navigation.
I got this error when the browser progress bar hangs here:
I am also still receiving this error. It happens when I try to change location for many photos at once (somewhere over 100 photos)
Having this error too I don't know what is.
Dont know if this is a duplicate (as video playback is not mentioned here in this one), but I have created another issue with the same log output, as this issue seems stale, and I provided all relevant info. New issue: https://github.com/immich-app/immich/issues/9351
No need to create a new issue, just request this one to be reopened.
I am not sure if it is the same issue though, as I get that error only on video playback which is not mentioned here.
Anyway, if we can solve it here (with the info in that other issue) that is great too.
error comes from here: https://github.com/nestjs/nest/blob/6dc96d396b80d1b6e383948a8d297504e61aa671/packages/platform-express/adapters/express-adapter.ts#L111
In my nginx access logs I can correlate this log with 499 status code (custom nginx status code for "client closed request").
Related URLs generating this log:
-
/api/asset/thumbnail/{id}?format=WEBP
-
/api/asset/file/{id}?isThumb=true&isWeb=false
The warning seems logic as those URL are returning binary content of images.
This was fixed (again) in #10013.