ERR AssetUpload -
When doing an initial upload to Immich of a backup I have running with icloudpd I am getting this error on one of my assets. What can I do to determine what is causing this? After this fails the process just hangs and nothing further gets uploaded.
2025-04-16 13:03:18 ERR upload error file=iCloud:2023/04/21/IMG_6736.MOV error=AssetUpload, POST, https://<myserver.com>/api/assets, 499
2025-04-16 13:03:18 ERR AssetUpload, POST, https://<myserver.com>/api/assets, 499
I guess Immich-go has closed the connection with the server after min with no response. You can extend the timeout with the option
--client-timeout=20min
immich-go just stays open and does nothing until I ctrl-c it. with --on-server-errors=continue then it continues to the next item immediately and works just fine. It does seem to be this specific asset that fails everytime...not sure why.
Could you try to change the client timeout to 20 min? Check the GitHub page for the exact syntax.
Tried with 20min client timeout and same thing. It just gets stuck on this file and never proceeds.
2025-04-18 12:52:15 INF server has same asset file=iCloud:2023/09/11/FullSizeRender-1607195.HEIC reason=An asset with the same name:"FullSizeRender.heic", date:"2023-09-11 10:42:01" and size:1.5 MB exists on the │
│server. No need to upload. │
│2025-04-18 12:54:14 ERR upload error file=iCloud:2023/04/21/IMG_6736.MOV error=AssetUpload, POST, https://<myserver.com>/api/assets, 499 │
│ │
│ │
│2025-04-18 12:54:14 ERR AssetUpload, POST, https://<myserver.com>/api/assets, 499
This is the last output and nothing else has happened since. It's been over an hour since this ERR.
The http error 499 is maybe issued by an NGINX. Immich-go has closed the connection because of the expiration of the timeout. Nothing has happened after this event. Maybe the server has crashed and is refusing all connection.
You could do the following
- increase the timeout
- launch immich-go with the
--api-traceflag - change the immich server's log level
and share all the logs with me.
I had the same error. For me it got solved by changing the timeout of my reverse proxy. See more info here: https://immich.app/docs/administration/reverse-proxy