immich-app/immich
1
0
Fork 0
mirror of https://github.com/immich-app/immich.git synced 2026-02-05 00:30:57 +03:00
Code Issues 11 Packages Projects Releases 10 Wiki Activity

[BUG] Not able to sync all images from iOS to Immich server #736

New Issue
Closed
opened 2026-02-04 22:11:41 +03:00 by OVERLORD · 36 comments
OVERLORD commented 2026-02-04 22:11:41 +03:00
Owner
Copy Link

Originally created by @trustos on GitHub (Mar 7, 2023).

Originally assigned to: @alextran1502 on GitHub.

The bug

Hi there,
First let me say how glad I am that I found Immich! A great product! And as with all great products there is always some polishing to be done.

So I am trying to upload my collection of 11 982 photos + videos from the Immich iOS app to the Immich server. I do have it set up on a subdomain. It all goes very well up until there are 31 images left in the Remainder section.

IMG_473C4303008A-1

So from there the process goes nowhere.

In the Immich server docker logs I can see the following errors appearing, apparently for all the 31 images:
2023-03-07 10:13:40 [Nest] 1 - 03/07/2023, 8:13:40 AM ERROR [ExceptionsHandler] Could not find any entity of type "AssetEntity" matching: { 2023-03-07 10:13:40 "where": { 2023-03-07 10:13:40 "ownerId": "ffb0e981-4be2-442f-8981-5b3f3af8dcdb", 2023-03-07 10:13:40 "checksum": { 2023-03-07 10:13:40 "type": "Buffer", 2023-03-07 10:13:40 "data": [ 2023-03-07 10:13:40 169, 2023-03-07 10:13:40 154, 2023-03-07 10:13:40 99, 2023-03-07 10:13:40 131, 2023-03-07 10:13:40 125, 2023-03-07 10:13:40 67, 2023-03-07 10:13:40 160, 2023-03-07 10:13:40 107, 2023-03-07 10:13:40 151, 2023-03-07 10:13:40 88, 2023-03-07 10:13:40 208, 2023-03-07 10:13:40 40, 2023-03-07 10:13:40 74, 2023-03-07 10:13:40 83, 2023-03-07 10:13:40 37, 2023-03-07 10:13:40 8, 2023-03-07 10:13:40 159, 2023-03-07 10:13:40 159, 2023-03-07 10:13:40 174, 2023-03-07 10:13:40 29 2023-03-07 10:13:40 ] 2023-03-07 10:13:40 } 2023-03-07 10:13:40 }, 2023-03-07 10:13:40 "relations": [ 2023-03-07 10:13:40 "exifInfo" 2023-03-07 10:13:40 ] 2023-03-07 10:13:40 } 2023-03-07 10:13:40 EntityNotFoundError: Could not find any entity of type "AssetEntity" matching: { 2023-03-07 10:13:40 "where": { 2023-03-07 10:13:40 "ownerId": "ffb0e981-4be2-442f-8981-5b3f3af8dcdb", 2023-03-07 10:13:40 "checksum": { 2023-03-07 10:13:40 "type": "Buffer", 2023-03-07 10:13:40 "data": [ 2023-03-07 10:13:40 169, 2023-03-07 10:13:40 154, 2023-03-07 10:13:40 99, 2023-03-07 10:13:40 131, 2023-03-07 10:13:40 125, 2023-03-07 10:13:40 67, 2023-03-07 10:13:40 160, 2023-03-07 10:13:40 107, 2023-03-07 10:13:40 151, 2023-03-07 10:13:40 88, 2023-03-07 10:13:40 208, 2023-03-07 10:13:40 40, 2023-03-07 10:13:40 74, 2023-03-07 10:13:40 83, 2023-03-07 10:13:40 37, 2023-03-07 10:13:40 8, 2023-03-07 10:13:40 159, 2023-03-07 10:13:40 159, 2023-03-07 10:13:40 174, 2023-03-07 10:13:40 29 2023-03-07 10:13:40 ] 2023-03-07 10:13:40 } 2023-03-07 10:13:40 }, 2023-03-07 10:13:40 "relations": [ 2023-03-07 10:13:40 "exifInfo" 2023-03-07 10:13:40 ] 2023-03-07 10:13:40 } 2023-03-07 10:13:40 at /usr/src/app/node_modules/typeorm/entity-manager/EntityManager.js:604:39 2023-03-07 10:13:40 at processTicksAndRejections (node:internal/process/task_queues:96:5) 2023-03-07 10:13:40 at async AssetService.uploadFile (/usr/src/app/dist/apps/immich/apps/immich/src/api-v1/asset/asset.service.js:74:35) 2023-03-07 10:13:40 at async AssetController.uploadFile (/usr/src/app/dist/apps/immich/apps/immich/src/api-v1/asset/asset.controller.js:60:29)

Do you have any idea why this might be happening?

I have already tried reinstalling the server from scratch 3 times (inc deleting containers + volumes) without any improvements.

Let me know If I can provide you with any additional info.

The OS that Immich Server is running on

MacOS Docker - latest immich container version

Version of Immich Server

1.50.1

Version of Immich Mobile App

1.50.0 build.88

Platform with the issue

  • Server
  • Web
  • Mobile

Your docker-compose.yml content

version: "3.8"

services:
  immich-server:
    container_name: immich_server
    image: altran1502/immich-server:release
    entrypoint: [ "/bin/sh", "./start-server.sh" ]
    volumes:
      - ${UPLOAD_LOCATION}:/usr/src/app/upload
    env_file:
      - .env
    environment:
      - NODE_ENV=production
    depends_on:
      - redis
      - database
    restart: always

  immich-microservices:
    container_name: immich_microservices
    image: altran1502/immich-server:release
    entrypoint: [ "/bin/sh", "./start-microservices.sh" ]
    volumes:
      - ${UPLOAD_LOCATION}:/usr/src/app/upload
    env_file:
      - .env
    environment:
      - NODE_ENV=production
    depends_on:
      - redis
      - database
    restart: always

  immich-machine-learning:
    container_name: immich_machine_learning
    image: altran1502/immich-machine-learning:release
    volumes:
      - ${UPLOAD_LOCATION}:/usr/src/app/upload
      - model-cache:/cache
    env_file:
      - .env
    environment:
      - NODE_ENV=production
    restart: always

  immich-web:
    container_name: immich_web
    image: altran1502/immich-web:release
    entrypoint: [ "/bin/sh", "./entrypoint.sh" ]
    env_file:
      - .env
    restart: always

  redis:
    container_name: immich_redis
    image: redis:6.2
    restart: always

  database:
    container_name: immich_postgres
    image: postgres:14
    env_file:
      - .env
    environment:
      POSTGRES_PASSWORD: ${DB_PASSWORD}
      POSTGRES_USER: ${DB_USERNAME}
      POSTGRES_DB: ${DB_DATABASE_NAME}
      PG_DATA: /var/lib/postgresql/data
    volumes:
      - pgdata:/var/lib/postgresql/data
    restart: always

  immich-proxy:
    container_name: immich_proxy
    image: altran1502/immich-proxy:release
    environment:
      # Make sure these values get passed through from the env file
      - IMMICH_SERVER_URL
      - IMMICH_WEB_URL
    ports:
      - 2283:8080
    logging:
      driver: none
    depends_on:
      - immich-server
    restart: always

volumes:
  pgdata:
  model-cache:

Your .env content

###################################################################################
# Database
###################################################################################

DB_HOSTNAME=immich_postgres
DB_USERNAME=[redacted]
DB_PASSWORD=[redacted]
DB_DATABASE_NAME=immich

# Optional Database settings:
# DB_PORT=5432

###################################################################################
# Redis
###################################################################################

REDIS_HOSTNAME=immich_redis

# Optional Redis settings:
# REDIS_PORT=6379
# REDIS_DBINDEX=0
# REDIS_PASSWORD=
# REDIS_SOCKET=

###################################################################################
# Upload File Location
#
# This is the location where uploaded files are stored.
###################################################################################

UPLOAD_LOCATION=[redacted]

###################################################################################
# Reverse Geocoding
#
# Reverse geocoding is done locally which has a small impact on memory usage
# This memory usage can be altered by changing the REVERSE_GEOCODING_PRECISION variable
# This ranges from 0-3 with 3 being the most precise
# 3 - Cities > 500 population: ~200MB RAM
# 2 - Cities > 1000 population: ~150MB RAM
# 1 - Cities > 5000 population: ~80MB RAM
# 0 - Cities > 15000 population: ~40MB RAM
####################################################################################

# DISABLE_REVERSE_GEOCODING=false
# REVERSE_GEOCODING_PRECISION=3

####################################################################################
# WEB - Optional
#
# Custom message on the login page, should be written in HTML form.
# For example:
# PUBLIC_LOGIN_PAGE_MESSAGE="This is a demo instance of Immich.<br><br>Email: <i>demo@demo.de</i><br>Password: <i>demo</i>"
####################################################################################

PUBLIC_LOGIN_PAGE_MESSAGE=

####################################################################################
# Alternative Service Addresses - Optional
#
# This is an advanced feature for users who may be running their immich services on different hosts.
# It will not change which address or port that services bind to within their containers, but it will change where other services look for their peers.
# Note: immich-microservices is bound to 3002, but no references are made
####################################################################################

IMMICH_WEB_URL=http://immich-web:3000
IMMICH_SERVER_URL=http://immich-server:3001
IMMICH_MACHINE_LEARNING_URL=http://immich-machine-learning:3003

####################################################################################
# Alternative API's External Address - Optional
#
# This is an advanced feature used to control the public server endpoint returned to clients during Well-known discovery.
# You should only use this if you want mobile apps to access the immich API over a custom URL. Do not include trailing slash.
# NOTE: At this time, the web app will not be affected by this setting and will continue to use the relative path: /api
# Examples: http://localhost:3001, http://immich-api.example.com, etc
####################################################################################

#IMMICH_API_URL_EXTERNAL=http://localhost:3001

Reproduction steps

1.Start backing up images from iOS app.
2. At some point the backup stop.

Additional information

No response

Originally created by @trustos on GitHub (Mar 7, 2023). Originally assigned to: @alextran1502 on GitHub. ### The bug Hi there, First let me say how glad I am that I found Immich! A great product! And as with all great products there is always some polishing to be done. So I am trying to upload my collection of 11 982 photos + videos from the Immich iOS app to the Immich server. I do have it set up on a subdomain. It all goes very well up until there are 31 images left in the Remainder section. ![IMG_473C4303008A-1](https://user-images.githubusercontent.com/12433240/223362421-f08ebafe-493d-4661-8d74-29abec19ce64.jpeg) So from there the process goes nowhere. In the Immich server docker logs I can see the following errors appearing, apparently for all the 31 images: `2023-03-07 10:13:40 [Nest] 1 - 03/07/2023, 8:13:40 AM ERROR [ExceptionsHandler] Could not find any entity of type "AssetEntity" matching: { 2023-03-07 10:13:40 "where": { 2023-03-07 10:13:40 "ownerId": "ffb0e981-4be2-442f-8981-5b3f3af8dcdb", 2023-03-07 10:13:40 "checksum": { 2023-03-07 10:13:40 "type": "Buffer", 2023-03-07 10:13:40 "data": [ 2023-03-07 10:13:40 169, 2023-03-07 10:13:40 154, 2023-03-07 10:13:40 99, 2023-03-07 10:13:40 131, 2023-03-07 10:13:40 125, 2023-03-07 10:13:40 67, 2023-03-07 10:13:40 160, 2023-03-07 10:13:40 107, 2023-03-07 10:13:40 151, 2023-03-07 10:13:40 88, 2023-03-07 10:13:40 208, 2023-03-07 10:13:40 40, 2023-03-07 10:13:40 74, 2023-03-07 10:13:40 83, 2023-03-07 10:13:40 37, 2023-03-07 10:13:40 8, 2023-03-07 10:13:40 159, 2023-03-07 10:13:40 159, 2023-03-07 10:13:40 174, 2023-03-07 10:13:40 29 2023-03-07 10:13:40 ] 2023-03-07 10:13:40 } 2023-03-07 10:13:40 }, 2023-03-07 10:13:40 "relations": [ 2023-03-07 10:13:40 "exifInfo" 2023-03-07 10:13:40 ] 2023-03-07 10:13:40 } 2023-03-07 10:13:40 EntityNotFoundError: Could not find any entity of type "AssetEntity" matching: { 2023-03-07 10:13:40 "where": { 2023-03-07 10:13:40 "ownerId": "ffb0e981-4be2-442f-8981-5b3f3af8dcdb", 2023-03-07 10:13:40 "checksum": { 2023-03-07 10:13:40 "type": "Buffer", 2023-03-07 10:13:40 "data": [ 2023-03-07 10:13:40 169, 2023-03-07 10:13:40 154, 2023-03-07 10:13:40 99, 2023-03-07 10:13:40 131, 2023-03-07 10:13:40 125, 2023-03-07 10:13:40 67, 2023-03-07 10:13:40 160, 2023-03-07 10:13:40 107, 2023-03-07 10:13:40 151, 2023-03-07 10:13:40 88, 2023-03-07 10:13:40 208, 2023-03-07 10:13:40 40, 2023-03-07 10:13:40 74, 2023-03-07 10:13:40 83, 2023-03-07 10:13:40 37, 2023-03-07 10:13:40 8, 2023-03-07 10:13:40 159, 2023-03-07 10:13:40 159, 2023-03-07 10:13:40 174, 2023-03-07 10:13:40 29 2023-03-07 10:13:40 ] 2023-03-07 10:13:40 } 2023-03-07 10:13:40 }, 2023-03-07 10:13:40 "relations": [ 2023-03-07 10:13:40 "exifInfo" 2023-03-07 10:13:40 ] 2023-03-07 10:13:40 } 2023-03-07 10:13:40 at /usr/src/app/node_modules/typeorm/entity-manager/EntityManager.js:604:39 2023-03-07 10:13:40 at processTicksAndRejections (node:internal/process/task_queues:96:5) 2023-03-07 10:13:40 at async AssetService.uploadFile (/usr/src/app/dist/apps/immich/apps/immich/src/api-v1/asset/asset.service.js:74:35) 2023-03-07 10:13:40 at async AssetController.uploadFile (/usr/src/app/dist/apps/immich/apps/immich/src/api-v1/asset/asset.controller.js:60:29)` Do you have any idea why this might be happening? I have already tried reinstalling the server from scratch 3 times (inc deleting containers + volumes) without any improvements. Let me know If I can provide you with any additional info. ### The OS that Immich Server is running on MacOS Docker - latest immich container version ### Version of Immich Server 1.50.1 ### Version of Immich Mobile App 1.50.0 build.88 ### Platform with the issue - [X] Server - [ ] Web - [X] Mobile ### Your docker-compose.yml content ```YAML version: "3.8" services: immich-server: container_name: immich_server image: altran1502/immich-server:release entrypoint: [ "/bin/sh", "./start-server.sh" ] volumes: - ${UPLOAD_LOCATION}:/usr/src/app/upload env_file: - .env environment: - NODE_ENV=production depends_on: - redis - database restart: always immich-microservices: container_name: immich_microservices image: altran1502/immich-server:release entrypoint: [ "/bin/sh", "./start-microservices.sh" ] volumes: - ${UPLOAD_LOCATION}:/usr/src/app/upload env_file: - .env environment: - NODE_ENV=production depends_on: - redis - database restart: always immich-machine-learning: container_name: immich_machine_learning image: altran1502/immich-machine-learning:release volumes: - ${UPLOAD_LOCATION}:/usr/src/app/upload - model-cache:/cache env_file: - .env environment: - NODE_ENV=production restart: always immich-web: container_name: immich_web image: altran1502/immich-web:release entrypoint: [ "/bin/sh", "./entrypoint.sh" ] env_file: - .env restart: always redis: container_name: immich_redis image: redis:6.2 restart: always database: container_name: immich_postgres image: postgres:14 env_file: - .env environment: POSTGRES_PASSWORD: ${DB_PASSWORD} POSTGRES_USER: ${DB_USERNAME} POSTGRES_DB: ${DB_DATABASE_NAME} PG_DATA: /var/lib/postgresql/data volumes: - pgdata:/var/lib/postgresql/data restart: always immich-proxy: container_name: immich_proxy image: altran1502/immich-proxy:release environment: # Make sure these values get passed through from the env file - IMMICH_SERVER_URL - IMMICH_WEB_URL ports: - 2283:8080 logging: driver: none depends_on: - immich-server restart: always volumes: pgdata: model-cache: ``` ### Your .env content ```Shell ################################################################################### # Database ################################################################################### DB_HOSTNAME=immich_postgres DB_USERNAME=[redacted] DB_PASSWORD=[redacted] DB_DATABASE_NAME=immich # Optional Database settings: # DB_PORT=5432 ################################################################################### # Redis ################################################################################### REDIS_HOSTNAME=immich_redis # Optional Redis settings: # REDIS_PORT=6379 # REDIS_DBINDEX=0 # REDIS_PASSWORD= # REDIS_SOCKET= ################################################################################### # Upload File Location # # This is the location where uploaded files are stored. ################################################################################### UPLOAD_LOCATION=[redacted] ################################################################################### # Reverse Geocoding # # Reverse geocoding is done locally which has a small impact on memory usage # This memory usage can be altered by changing the REVERSE_GEOCODING_PRECISION variable # This ranges from 0-3 with 3 being the most precise # 3 - Cities > 500 population: ~200MB RAM # 2 - Cities > 1000 population: ~150MB RAM # 1 - Cities > 5000 population: ~80MB RAM # 0 - Cities > 15000 population: ~40MB RAM #################################################################################### # DISABLE_REVERSE_GEOCODING=false # REVERSE_GEOCODING_PRECISION=3 #################################################################################### # WEB - Optional # # Custom message on the login page, should be written in HTML form. # For example: # PUBLIC_LOGIN_PAGE_MESSAGE="This is a demo instance of Immich.<br><br>Email: <i>demo@demo.de</i><br>Password: <i>demo</i>" #################################################################################### PUBLIC_LOGIN_PAGE_MESSAGE= #################################################################################### # Alternative Service Addresses - Optional # # This is an advanced feature for users who may be running their immich services on different hosts. # It will not change which address or port that services bind to within their containers, but it will change where other services look for their peers. # Note: immich-microservices is bound to 3002, but no references are made #################################################################################### IMMICH_WEB_URL=http://immich-web:3000 IMMICH_SERVER_URL=http://immich-server:3001 IMMICH_MACHINE_LEARNING_URL=http://immich-machine-learning:3003 #################################################################################### # Alternative API's External Address - Optional # # This is an advanced feature used to control the public server endpoint returned to clients during Well-known discovery. # You should only use this if you want mobile apps to access the immich API over a custom URL. Do not include trailing slash. # NOTE: At this time, the web app will not be affected by this setting and will continue to use the relative path: /api # Examples: http://localhost:3001, http://immich-api.example.com, etc #################################################################################### #IMMICH_API_URL_EXTERNAL=http://localhost:3001 ``` ### Reproduction steps ```bash 1.Start backing up images from iOS app. 2. At some point the backup stop. ``` ### Additional information _No response_
OVERLORD added the 🗄️server📱mobile labels 2026-02-04 22:11:41 +03:00
OVERLORD commented 2026-02-04 22:11:48 +03:00
Author
Owner
Copy Link

@samip5 commented on GitHub (Mar 7, 2023):

Are you absolutely sure that you had a fresh database? That doesn't sound like so.

@samip5 commented on GitHub (Mar 7, 2023): Are you absolutely sure that you had a fresh database? That doesn't sound like so.
OVERLORD commented 2026-02-04 22:11:52 +03:00
Author
Owner
Copy Link

@trustos commented on GitHub (Mar 7, 2023):

Sounds to me also like a db sync issue that's why I made sure to delete the postgre volume and even changed db credentials. The setup started anew with the setting up of the admin and etc.
I'll try a new installation with the isolated problematic images.

@trustos commented on GitHub (Mar 7, 2023): Sounds to me also like a db sync issue that's why I made sure to delete the postgre volume and even changed db credentials. The setup started anew with the setting up of the admin and etc. I'll try a new installation with the isolated problematic images.
OVERLORD commented 2026-02-04 22:12:00 +03:00
Author
Owner
Copy Link

@httpiga commented on GitHub (Mar 7, 2023):

I'm having this same issue as well

@httpiga commented on GitHub (Mar 7, 2023): I'm having this same issue as well
OVERLORD commented 2026-02-04 22:12:05 +03:00
Author
Owner
Copy Link

@alextran1502 commented on GitHub (Mar 7, 2023):

Are you accessing the server through dns or local ip? Can you track down that file to make sure it is not corrupted? If possible, can you share the file for debugging?

@alextran1502 commented on GitHub (Mar 7, 2023): Are you accessing the server through dns or local ip? Can you track down that file to make sure it is not corrupted? If possible, can you share the file for debugging?
OVERLORD commented 2026-02-04 22:12:13 +03:00
Author
Owner
Copy Link

@jrasm91 commented on GitHub (Mar 7, 2023):

Pretty sure this is related to uploading live photos. There is a bug in the asset upload logic and it does not handle the situation where the motion part is duplicate and the still part is missing. I believe this is a live photo and somehow the motion part of the live photo has already been uploaded independently.

@jrasm91 commented on GitHub (Mar 7, 2023): Pretty sure this is related to uploading live photos. There is a bug in the asset upload logic and it does not handle the situation where the motion part is duplicate and the still part is missing. I believe this is a live photo and somehow the motion part of the live photo has already been uploaded independently.
OVERLORD commented 2026-02-04 22:12:18 +03:00
Author
Owner
Copy Link

@trustos commented on GitHub (Mar 7, 2023):

So I tried reinstalled the whole system again, deleting all the possible volumes and containers again.
Out of the 31 problematic images I did isolate 2 and included them in another album.
With the new installation I started by uploading these 2 images and it was successful. I continued to upload the other 11K photos and videos and at the end in the Remainder there are now 29 photos that are not able to re synched.

I was originally hosting Immich through a sub domain(ex. https://immich.domain.com) that is pointing my traffic to my reverse proxy.
With my last attempt I did the test only via my local ip (ex. 192.168.2.286) and that was the result.

I have no issues sharing the photo but as it succeeded uploading when uploaded from another album I am pretty sure it is not corrupted.

@trustos commented on GitHub (Mar 7, 2023): So I tried reinstalled the whole system again, deleting all the possible volumes and containers again. Out of the 31 problematic images I did isolate 2 and included them in another album. With the new installation I started by uploading these 2 images and it was successful. I continued to upload the other 11K photos and videos and at the end in the Remainder there are now 29 photos that are not able to re synched. I was originally hosting Immich through a sub domain(ex. https://immich.domain.com) that is pointing my traffic to my reverse proxy. With my last attempt I did the test only via my local ip (ex. 192.168.2.286) and that was the result. I have no issues sharing the photo but as it succeeded uploading when uploaded from another album I am pretty sure it is not corrupted.
OVERLORD commented 2026-02-04 22:12:21 +03:00
Author
Owner
Copy Link

@jrasm91 commented on GitHub (Mar 7, 2023):

Can you see what 29 are failing to upload and see if you can find it in the timeline in immich? I believe you can click the icon in currently uploading section of the backup screen to make it show a thumbnail.

(or get the date from the image file itself and then use that to locate it in the timeline)

@jrasm91 commented on GitHub (Mar 7, 2023): Can you see what 29 are failing to upload and see if you can find it in the timeline in immich? I believe you can click the icon in currently uploading section of the backup screen to make it show a thumbnail. (or get the date from the image file itself and then use that to locate it in the timeline)
OVERLORD commented 2026-02-04 22:12:25 +03:00
Author
Owner
Copy Link

@trustos commented on GitHub (Mar 7, 2023):

I just checked 3 out of the failing ones and I can say the following.
The 3 images have in common the fact that they are edited.
So In my Recents album I do have an image IMG_1238 from June 3rd 2022 and the next image in the Photos app is an image with the same name IMG_1238, same date but it is just an edited copy of the other one. On the second img I can choose "revert to the original" but yet again it is not uploading.

Might be related?

@trustos commented on GitHub (Mar 7, 2023): I just checked 3 out of the failing ones and I can say the following. The 3 images have in common the fact that they are edited. So In my Recents album I do have an image IMG_1238 from June 3rd 2022 and the next image in the Photos app is an image with the same name IMG_1238, same date but it is just an edited copy of the other one. On the second img I can choose "revert to the original" but yet again it is not uploading. Might be related?
OVERLORD commented 2026-02-04 22:12:26 +03:00
Author
Owner
Copy Link

@jrasm91 commented on GitHub (Mar 7, 2023):

They are live photos, right? Live photos are actually two assets, a picture and a short video. I'm guessing both photos are linked to the same video and the video has already been uploaded. So I think we may not support this case - uploading a second picture that is linked to the same motion asset as another live photo.

@jrasm91 commented on GitHub (Mar 7, 2023): They are live photos, right? Live photos are actually two assets, a picture and a short video. I'm guessing both photos are linked to the same video and the video has already been uploaded. So I think we may not support this case - uploading a second picture that is linked to the same motion asset as another live photo.
OVERLORD commented 2026-02-04 22:12:30 +03:00
Author
Owner
Copy Link

@trustos commented on GitHub (Mar 7, 2023):

Yes, they are live photos. And it sounds logical to me that this is the case - two photos linking to the same motion video.
Apparently to me it is a fairly common case and I can see others with the same issue. Hope it can be handled somehow in the future - either by choosing one of the linked photos or by handling the linked asset.

So do you have any suggestion to me beside deleting the edited photos?

@trustos commented on GitHub (Mar 7, 2023): Yes, they are live photos. And it sounds logical to me that this is the case - two photos linking to the same motion video. Apparently to me it is a fairly common case and I can see others with the same issue. Hope it can be handled somehow in the future - either by choosing one of the linked photos or by handling the linked asset. So do you have any suggestion to me beside deleting the edited photos?
OVERLORD commented 2026-02-04 22:12:32 +03:00
Author
Owner
Copy Link

@jrasm91 commented on GitHub (Mar 7, 2023):

Yeah, I agree it would be nice to support that use case. I think we almost do, just need to make a few tweaks:

  • On the mobile side, upload the still and motion parts independently
  • On the server, don't delete the motion asset unless it's the last one 😄
  • We already support auto-linking, but we might need to double check that it works with multiple photos.

In the interim, I would probably move your edits to a separate folder/album, which you could exclude on the backup screen.

@jrasm91 commented on GitHub (Mar 7, 2023): Yeah, I agree it would be nice to support that use case. I think we _almost_ do, just need to make a few tweaks: - On the mobile side, upload the still and motion parts independently - On the server, don't delete the motion asset unless it's the last one :smile: - We already support auto-linking, but we might need to double check that it works with multiple photos. In the interim, I would probably move your edits to a separate folder/album, which you could exclude on the backup screen.
OVERLORD commented 2026-02-04 22:12:37 +03:00
Author
Owner
Copy Link

@trustos commented on GitHub (Mar 7, 2023):

Thank you for your answer. I hope it gets fixed.
BTW As a side effect on every app start the app tries to upload the same images and piles assets that increase my dedicated storage space.

@trustos commented on GitHub (Mar 7, 2023): Thank you for your answer. I hope it gets fixed. BTW As a side effect on every app start the app tries to upload the same images and piles assets that increase my dedicated storage space.
OVERLORD commented 2026-02-04 22:12:40 +03:00
Author
Owner
Copy Link

@trustos commented on GitHub (Mar 7, 2023):

Addendum: I went on to delete my dupes and as initially 2 of those were isolated in another album, now it shows a negative value
96E78CA9-54FA-4FFD-A6D0-330AFB1882B6

@trustos commented on GitHub (Mar 7, 2023): Addendum: I went on to delete my dupes and as initially 2 of those were isolated in another album, now it shows a negative value ![96E78CA9-54FA-4FFD-A6D0-330AFB1882B6](https://user-images.githubusercontent.com/12433240/223520754-40597bbc-af91-4b6c-9653-1e0ca6ceea58.png)
OVERLORD commented 2026-02-04 22:12:42 +03:00
Author
Owner
Copy Link

@jrasm91 commented on GitHub (Mar 7, 2023):

Yeah, the negative issue is a known bug that should hopefully get fixed soon. It is purely cosmetic.

Files not getting cleaned up sounds like a bug though. If a file is a duplicate it should get deleted and not sit around in your upload folder.

It may be worth writing a server command to list files in the upload folder that aren't used in the database do you can safely remove them

@jrasm91 commented on GitHub (Mar 7, 2023): Yeah, the negative issue is a known bug that should hopefully get fixed soon. It is purely cosmetic. Files not getting cleaned up sounds like a bug though. If a file is a duplicate it should get deleted and not sit around in your upload folder. It may be worth writing a server command to list files in the upload folder that aren't used in the database do you can safely remove them
OVERLORD commented 2026-02-04 22:12:44 +03:00
Author
Owner
Copy Link

@srwareham commented on GitHub (Mar 12, 2023):

This seems very similar to what I've been experiencing in #1902

@srwareham commented on GitHub (Mar 12, 2023): This seems very similar to what I've been experiencing in #1902
OVERLORD commented 2026-02-04 22:12:47 +03:00
Author
Owner
Copy Link

@PratikMahajan commented on GitHub (Mar 23, 2023):

i saw a similar bug.
To reproduce,

  1. take a photo
  2. duplicate the photo in photos app
  3. edit the duplicated photo.

if 1 photo is already backed up and the 2nd photo is the last one in the backup queue, it'll get stuck at 100% and wont upload until you delete the other photo on immich.

Workaround:

  1. download the photo from immich to files app or similar
  2. delete the photo on immich
  3. upload the edited photo
  4. add the downloaded photo from files app to photos
  5. upload the deleted photo.
@PratikMahajan commented on GitHub (Mar 23, 2023): i saw a similar bug. To reproduce, 1. take a photo 2. duplicate the photo in photos app 3. edit the duplicated photo. if 1 photo is already backed up and the 2nd photo is the last one in the backup queue, it'll get stuck at 100% and wont upload until you delete the other photo on immich. **Workaround:** 1. download the photo from immich to files app or similar 4. delete the photo on immich 5. upload the edited photo 6. add the downloaded photo from files app to photos 7. upload the deleted photo.
OVERLORD commented 2026-02-04 22:12:51 +03:00
Author
Owner
Copy Link

@rursache commented on GitHub (Mar 31, 2023):

I'm having the same issue as OP, docker logs are similar if not identical. There is no way I'm manually editing 6k photos to walkaround this, a fix should be made on the app itself.
issue

@rursache commented on GitHub (Mar 31, 2023): I'm having the same issue as OP, docker logs are similar if not identical. There is no way I'm manually editing 6k photos to walkaround this, a fix should be made on the app itself. ![issue](https://i.imgur.com/Nt5KiDc.jpg)
OVERLORD commented 2026-02-04 22:12:55 +03:00
Author
Owner
Copy Link

@alextran1502 commented on GitHub (Mar 31, 2023):

I'm having the same issue as OP, docker logs are similar if not identical. There is no way I'm manually editing 6k photos to walkaround this, a fix should be made on the app itself.

issue

Thank you for raising this issue up, will put this in the queue to fix it next release

@alextran1502 commented on GitHub (Mar 31, 2023): > I'm having the same issue as OP, docker logs are similar if not identical. There is no way I'm manually editing 6k photos to walkaround this, a fix should be made on the app itself. > > ![issue](https://i.imgur.com/Nt5KiDc.jpg) Thank you for raising this issue up, will put this in the queue to fix it next release
OVERLORD commented 2026-02-04 22:12:59 +03:00
Author
Owner
Copy Link

@rursache commented on GitHub (May 19, 2023):

@alextran1502 hi, are there any updates on this? i'm still having problems. the logs are still full of these errors and the last 50ish images are never uploaded. if those are dupes, the server should discard them and mark them as uploaded. or at least the iOS app should display them in a separate list so i know which ones have the problem. thanks

EntityNotFoundError: Could not find any entity of type "AssetEntity" matching: {
    "where": {
        "ownerId": "9311ddce-19d2-4ea9-8984-c4f63a9a30ed",
        "checksum": {
            "type": "Buffer",
            "data": [
                88,
                2,
                135,
                37,
                52,
                54,
                64,
                224,
                5,
                122,
                55,
                56,
                56,
                104,
                139,
                109,
                55,
                19,
                195,

            ]
        }
    },
    "relations": [
0=e 1=x 2=i 3=f 4=I 5=n 6=f 7=o 
    ]
}
    at /app/immich/server/node_modules/typeorm/entity-manager/EntityManager.js:638:39
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async AssetService.uploadFile (/app/immich/server/dist/apps/immich/apps/immich/src/api-v1/asset/asset.service.js:75:35)
    at async AssetController.uploadFile (/app/immich/server/dist/apps/immich/apps/immich/src/api-v1/asset/asset.controller.js:62:29)
[Nest] 536  - 05/19/2023, 4:45:57 AM   ERROR [ExceptionsHandler] Could not find any entity of type "AssetEntity" matching: {
    "where": {
        "ownerId": "9311ddce-19d2-4ea9-8984-c4f63a9a30ed",
        "checksum": {
            "type": "Buffer",
            "data": [
                157,
                172,
                178,
                62,
                53,
                118,
                125,
                77,
                74,
                199,
                154,
                170,
                107,
                73,
                220,
                103,
                2,
                165,
                90,

            ]
        }
    },
    "relations": [
0=e 1=x 2=i 3=f 4=I 5=n 6=f 7=o 
    ]
}
@rursache commented on GitHub (May 19, 2023): @alextran1502 hi, are there any updates on this? i'm still having problems. the logs are still full of these errors and the last 50ish images are never uploaded. if those are dupes, the server should discard them and mark them as uploaded. or at least the iOS app should display them in a separate list so i know which ones have the problem. thanks ``` EntityNotFoundError: Could not find any entity of type "AssetEntity" matching: { "where": { "ownerId": "9311ddce-19d2-4ea9-8984-c4f63a9a30ed", "checksum": { "type": "Buffer", "data": [ 88, 2, 135, 37, 52, 54, 64, 224, 5, 122, 55, 56, 56, 104, 139, 109, 55, 19, 195, ] } }, "relations": [ 0=e 1=x 2=i 3=f 4=I 5=n 6=f 7=o ] } at /app/immich/server/node_modules/typeorm/entity-manager/EntityManager.js:638:39 at runMicrotasks (<anonymous>) at processTicksAndRejections (node:internal/process/task_queues:96:5) at async AssetService.uploadFile (/app/immich/server/dist/apps/immich/apps/immich/src/api-v1/asset/asset.service.js:75:35) at async AssetController.uploadFile (/app/immich/server/dist/apps/immich/apps/immich/src/api-v1/asset/asset.controller.js:62:29) [Nest] 536 - 05/19/2023, 4:45:57 AM ERROR [ExceptionsHandler] Could not find any entity of type "AssetEntity" matching: { "where": { "ownerId": "9311ddce-19d2-4ea9-8984-c4f63a9a30ed", "checksum": { "type": "Buffer", "data": [ 157, 172, 178, 62, 53, 118, 125, 77, 74, 199, 154, 170, 107, 73, 220, 103, 2, 165, 90, ] } }, "relations": [ 0=e 1=x 2=i 3=f 4=I 5=n 6=f 7=o ] } ```
OVERLORD commented 2026-02-04 22:13:03 +03:00
Author
Owner
Copy Link

@alextran1502 commented on GitHub (May 19, 2023):

Did you happen to run some CLI import before these photos, which contain the video portion of the LivePhotos? It might cause this issue if there is duplication of the video portion

@alextran1502 commented on GitHub (May 19, 2023): Did you happen to run some CLI import before these photos, which contain the video portion of the LivePhotos? It might cause this issue if there is duplication of the video portion
OVERLORD commented 2026-02-04 22:13:05 +03:00
Author
Owner
Copy Link

@rursache commented on GitHub (May 19, 2023):

@alextran1502: Did you happen to run some CLI import before these photos, which contain the video portion of the LivePhotos? It might cause this issue if there is duplication of the video portion

I only ever used the iOS app to upload/import my photos to Immich as all my photos are in Apple Photos.

EDIT: However, in the albums list, I checked them all, including Live Photos, Slow-mo, Bursts, Portrait and Panoramas (the system albums)

@rursache commented on GitHub (May 19, 2023): > @alextran1502: Did you happen to run some CLI import before these photos, which contain the video portion of the LivePhotos? It might cause this issue if there is duplication of the video portion I only ever used the iOS app to upload/import my photos to Immich as all my photos are in Apple Photos. **EDIT**: However, in the albums list, I checked them all, including Live Photos, Slow-mo, Bursts, Portrait and Panoramas (the system albums)
OVERLORD commented 2026-02-04 22:13:10 +03:00
Author
Owner
Copy Link

@alextran1502 commented on GitHub (May 19, 2023):

Please try the following

  1. Choose only recents album and upload
  2. Try recent and exclude live photo albums
  3. Try upload on a brand new Immich instance

Let me know how that goes

@alextran1502 commented on GitHub (May 19, 2023): Please try the following 1. Choose only recents album and upload 2. Try recent and exclude live photo albums 3. Try upload on a brand new Immich instance Let me know how that goes
OVERLORD commented 2026-02-04 22:13:15 +03:00
Author
Owner
Copy Link

@rursache commented on GitHub (May 19, 2023):

@alextran1502
I tried only checking the recents album and it went from 61 "remainder" assets to 45 but now its stuck at 45. I can't start from scratch, my library is over 100GB which I don't want to transfer again. There is also another user on this instance, my girlfriend. We have some common photos/videos (way more than 45), could those interfere?

EDIT: Also from what I see, the stuck assets are videos -- not photos (.mov)

@rursache commented on GitHub (May 19, 2023): @alextran1502 I tried only checking the recents album and it went from 61 "remainder" assets to 45 but now its stuck at 45. I can't start from scratch, my library is over 100GB which I don't want to transfer again. There is also another user on this instance, my girlfriend. We have some common photos/videos (way more than 45), could those interfere? EDIT: Also from what I see, the stuck assets are videos -- not photos (.mov)
OVERLORD commented 2026-02-04 22:13:18 +03:00
Author
Owner
Copy Link

@jrasm91 commented on GitHub (May 19, 2023):

There are some weird edge cases related to live photos that cause this problem. We can look into it again though. The situation is trying to backup a live photo, which is two parts (1) motion and (2) photo/still. If the motion is already uploaded we try to return the id for the still, but sometimes it doesn't exist. The motion part could have been uploaded via a CLI import, or it could be apart of another asset (an edited photo, etc.). Those are the files that are having problems.

@jrasm91 commented on GitHub (May 19, 2023): There are some weird edge cases related to live photos that cause this problem. We can look into it again though. The situation is trying to backup a live photo, which is two parts (1) motion and (2) photo/still. If the motion is already uploaded we try to return the id for the still, but sometimes it doesn't exist. The motion part could have been uploaded via a CLI import, or it could be apart of another asset (an edited photo, etc.). Those are the files that are having problems.
OVERLORD commented 2026-02-04 22:13:22 +03:00
Author
Owner
Copy Link

@rursache commented on GitHub (May 19, 2023):

We can look into it again though

please do. i currently can't trust the app to do what it should as the background tasks get stuck for the same reason (if they start at all; that's a thing for another topic). it's crucial for Immich that the mobile apps work as they should. i would help but the app is not iOS native. thank you all for your work

@rursache commented on GitHub (May 19, 2023): > We can look into it again though please do. i currently can't trust the app to do what it should as the background tasks get stuck for the same reason (if they start at all; that's a thing for another topic). it's crucial for Immich that the mobile apps work as they should. i would help but the app is not iOS native. thank you all for your work
OVERLORD commented 2026-02-04 22:13:26 +03:00
Author
Owner
Copy Link

@rursache commented on GitHub (May 28, 2023):

still happening on v1.58.0 (both app and server)

EDIT: somehow it went from the remaining 45 assets to only 6. maybe the upload process shuffled the asset order so the stuck files were more down the pile? the app also crashed a few times during this and I can only hope for a native app instead of the current clunky and Android-looking one. maybe that would fix all these problems? 🤞🏻

@rursache commented on GitHub (May 28, 2023): still happening on v1.58.0 (both app and server) **EDIT**: somehow it went from the remaining 45 assets to only 6. maybe the upload process shuffled the asset order so the stuck files were more down the pile? the app also crashed a few times during this and I can only hope for a native app instead of the current clunky and Android-looking one. maybe that would fix all these problems? 🤞🏻
OVERLORD commented 2026-02-04 22:13:29 +03:00
Author
Owner
Copy Link

@jrasm91 commented on GitHub (May 30, 2023):

There was an attempted fix for this in 1.58. Can you re-examine the mobile app and immich-server logs when the backup runs and fails to see if it is the same error or not?

@jrasm91 commented on GitHub (May 30, 2023): There was an attempted fix for this in 1.58. Can you re-examine the mobile app and immich-server logs when the backup runs and fails to see if it is the same error or not?
OVERLORD commented 2026-02-04 22:13:34 +03:00
Author
Owner
Copy Link

@rursache commented on GitHub (May 30, 2023):

@jrasm91 there is a clear improvement proven by the fact that I went from 45 to 6 assets not uploaded (all are videos). however right now I don't see any error/warning in logs (on server) mobile logs seem also clean but I've uploaded the exported CSV here.

as of right now, the apps keeps looping through those 6 remaining videos uploading them over and over again, never finishing. the phone is also burning hot and slows down until I kill the app.

happy to provide whatever else is needed to help fix this, including testing beta builds of the iOS app if TestFlight is setup.

@rursache commented on GitHub (May 30, 2023): @jrasm91 there is a clear improvement proven by the fact that I went from 45 to 6 assets not uploaded (**all are videos**). however right now I don't see any error/warning in logs (on server) mobile logs seem also clean but I've uploaded the exported CSV [here](https://pastebin.com/p9xiAqT8). as of right now, the apps keeps looping through those 6 remaining videos uploading them over and over again, never finishing. the phone is also burning hot and slows down until I kill the app. happy to provide whatever else is needed to help fix this, including testing beta builds of the iOS app if TestFlight is setup.
OVERLORD commented 2026-02-04 22:13:39 +03:00
Author
Owner
Copy Link

@rursache commented on GitHub (May 31, 2023):

still happening on v1.59.1 (server) and v1.59.0 (app)

@rursache commented on GitHub (May 31, 2023): still happening on v1.59.1 (server) and v1.59.0 (app)
OVERLORD commented 2026-02-04 22:13:47 +03:00
Author
Owner
Copy Link

@rursache commented on GitHub (Jun 5, 2023):

still happening on v1.60.0 (server) and v1.60.0 (app)

@rursache commented on GitHub (Jun 5, 2023): still happening on v1.60.0 (server) and v1.60.0 (app)
OVERLORD commented 2026-02-04 22:13:48 +03:00
Author
Owner
Copy Link

@jrasm91 commented on GitHub (Jun 5, 2023):

The original error looks to have been resolved if you are no longer seeing those error messages.

Videos not being uploaded is most likely a setup (proxy) issue related to their size. Can you confirm how big the video files are and if you are using a reverse proxy?

@jrasm91 commented on GitHub (Jun 5, 2023): The original error looks to have been resolved if you are no longer seeing those error messages. Videos not being uploaded is most likely a setup (proxy) issue related to their size. Can you confirm how big the video files are and if you are using a reverse proxy?
OVERLORD commented 2026-02-04 22:13:52 +03:00
Author
Owner
Copy Link

@rursache commented on GitHub (Jun 5, 2023):

@jrasm91 unbelievable but you were right. i logged in using the local IP and it uploaded all the remaining videos... i'm using cloudflare tunnels, any way to increase the file size transfer limit? i don't know how big the videos are, the app isn't telling me and "IMG_xyqz.mov" doesn't mean anything

@rursache commented on GitHub (Jun 5, 2023): @jrasm91 unbelievable but you were right. i logged in using the local IP and it uploaded all the remaining videos... i'm using cloudflare tunnels, any way to increase the file size transfer limit? i don't know how big the videos are, the app isn't telling me and "IMG_xyqz.mov" doesn't mean anything
OVERLORD commented 2026-02-04 22:13:55 +03:00
Author
Owner
Copy Link

@jrasm91 commented on GitHub (Jun 5, 2023):

I don't know much about cloudflare tunnels, personally. I think I've heard 100mb limit. You would need to consult their documentation and also terms of service to verify that though.

@jrasm91 commented on GitHub (Jun 5, 2023): I don't know much about cloudflare tunnels, personally. I think I've heard 100mb limit. You would need to consult their documentation and also terms of service to verify that though.
OVERLORD commented 2026-02-04 22:13:59 +03:00
Author
Owner
Copy Link

@JustAmply commented on GitHub (Jun 5, 2023):

Yes, 100 Mbit upload limit with HTTP POST request is correct.

Source: Cloudflare limits the upload size (HTTP POST request size) per plan type

@JustAmply commented on GitHub (Jun 5, 2023): Yes, 100 Mbit upload limit with HTTP POST request is correct. Source: [Cloudflare limits the upload size (HTTP POST request size) per plan type](https://developers.cloudflare.com/cache/concepts/default-cache-behavior/#customization-options-and-limitations:~:text=Cloudflare%20limits%20the,Free%20and%20Pro)
OVERLORD commented 2026-02-04 22:14:04 +03:00
Author
Owner
Copy Link

@jrasm91 commented on GitHub (Jun 5, 2023):

Yeah, so that is a limitation of the service and not something we can fix from our side in the short or mid-term. There's some other discussions open about uploading the files in chunks, so over multiple requests, but I doubt that will be looked at or implemented any time soon.

@jrasm91 commented on GitHub (Jun 5, 2023): Yeah, so that is a limitation of the service and not something we can fix from our side in the short or mid-term. There's some other discussions open about uploading the files in chunks, so over multiple requests, but I doubt that will be looked at or implemented any time soon.
OVERLORD commented 2026-02-04 22:14:06 +03:00
Author
Owner
Copy Link

@alextran1502 commented on GitHub (Apr 27, 2024):

Stale, probably not relevant anymore

@alextran1502 commented on GitHub (Apr 27, 2024): Stale, probably not relevant anymore
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
accessibility
changelog:enhancement
changelog:security
changelog:translation
cli
date-time
documentation
external-library
format
good first issue
needs-answer
nice to have
sharing
tech-debt
📱mobile
🖥️web
🗄️server
🧠machine-learning
No Label 📱mobile 🗄️server
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: immich-app/immich#736
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?