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

[BUG] Web upload directly to album fails to add some images to album #1217

New Issue
Closed
opened 2026-02-05 00:54:23 +03:00 by OVERLORD · 9 comments
OVERLORD commented 2026-02-05 00:54:23 +03:00
Owner
Copy Link

Originally created by @raisinbear on GitHub (Aug 12, 2023).

The bug

Hi,

I noticed that when creating an album in the web interface and uploading an admittedly large number of assets (~100 - 300), there is always a smaller number of assets displayed in immich than in the source folder. Roughy in the ballpark of 3% missing.
I could not find anything peculiar about the assets missing, nor see anything in stdout, although messages tend to fly by quickly. Starting reuploading the missing files, I noticed duplicate entry violations in the output and followed up checking the timeline where the presumably missing files were indeed showing up.
So it appears - I could only check this in 2 out of 5 instances, where assets were missing - that all my files were uploaded, but some few were not added to the album to which they were uploaded.
I guess this may be a tough one, because behavior is kind of erratic, but I'll leave it here nonetheless.
Thank you guys so much for all the effort!

The OS that Immich Server is running on

Debian

Version of Immich Server

v1.72.1

Version of Immich Mobile App

v1.72.0

Platform with the issue

  • Server
  • Web
  • Mobile

Your docker-compose.yml content

version: "3.8"

services:
  immich-server:
    container_name: immich_server
    image: ghcr.io/immich-app/immich-server:${IMMICH_VERSION:-release}
    command: [ "start.sh", "immich" ]
    volumes:
      - ${UPLOAD_LOCATION}:/usr/src/app/upload
    env_file:
      - .env
    depends_on:
      - redis
      - database
      - typesense
    restart: always

  immich-microservices:
    container_name: immich_microservices
    image: ghcr.io/immich-app/immich-server:${IMMICH_VERSION:-release}
    command: [ "start.sh", "microservices" ]
    volumes:
      - ${UPLOAD_LOCATION}:/usr/src/app/upload
    env_file:
      - .env
    depends_on:
      - redis
      - database
      - typesense
    restart: always

  immich-machine-learning:
    container_name: immich_machine_learning
    image: ghcr.io/immich-app/immich-machine-learning:${IMMICH_VERSION:-release}
    volumes:
      - model-cache:/cache
    env_file:
      - .env
    restart: always

  immich-web:
    container_name: immich_web
    image: ghcr.io/immich-app/immich-web:${IMMICH_VERSION:-release}
    env_file:
      - .env
    restart: always

  typesense:
    container_name: immich_typesense
    image: typesense/typesense:0.24.1@sha256:9bcff2b829f12074426ca044b56160ca9d777a0c488303469143dd9f8259d4dd
    environment:
      - TYPESENSE_API_KEY=${TYPESENSE_API_KEY}
      - TYPESENSE_DATA_DIR=/data
    volumes:
      - tsdata:/data
    restart: always

  redis:
    container_name: immich_redis
    image: redis:6.2-alpine@sha256:70a7a5b641117670beae0d80658430853896b5ef269ccf00d1827427e3263fa3
    restart: always

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

  immich-proxy:
    container_name: immich_proxy
    image: ghcr.io/immich-app/immich-proxy:${IMMICH_VERSION:-release}
    environment:
      # Make sure these values get passed through from the env file
      - IMMICH_SERVER_URL
      - IMMICH_WEB_URL
    ports:
      - 2283:8080
    depends_on:
      - immich-server
      - immich-web
    restart: always

volumes:
  pgdata:
  model-cache:
  tsdata:

Your .env content

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

# NOTE: The following four database variables support Docker secrets by adding a *_FILE suffix to the variable name
# See the docker-compose documentation on secrets for additional details: https://docs.docker.com/compose/compose-file/compose-file-v3/#secrets
DB_HOSTNAME=immich_postgres
DB_USERNAME=postgres
DB_PASSWORD=postgres
DB_DATABASE_NAME=immich

# Optional Database settings:
# DB_PORT=5432

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

REDIS_HOSTNAME=immich_redis

# REDIS_URL will be used to pass custom options to ioredis.
# Example for Sentinel
# {"sentinels":[{"host":"redis-sentinel-node-0","port":26379},{"host":"redis-sentinel-node-1","port":26379},{"host":"redis-sentinel-node-2","port":26379}],"name":"redis-sentinel"}
# REDIS_URL=ioredis://eyJzZW50aW5lbHMiOlt7Imhvc3QiOiJyZWRpcy1zZW50aW5lbDEiLCJwb3J0IjoyNjM3OX0seyJob3N0IjoicmVkaXMtc2VudGluZWwyIiwicG9ydCI6MjYzNzl9XSwibmFtZSI6Im15bWFzdGVyIn0=

# Optional Redis settings:

# Note: these parameters are not automatically passed to the Redis Container
# to do so, please edit the docker-compose.yml file as well. Redis is not configured
# via environment variables, only redis.conf or the command line

# REDIS_PORT=6379
# REDIS_DBINDEX=0
# REDIS_USERNAME=
# REDIS_PASSWORD=
# REDIS_SOCKET=

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

UPLOAD_LOCATION=/home/immich/data


###################################################################################
# Typesense
###################################################################################
TYPESENSE_API_KEY=[]
# TYPESENSE_ENABLED=false
# TYPESENSE_URL uses base64 encoding for the nodes json.
# Example JSON that was used:
# [
#      { "host": "typesense-1.example.net", "port": "443", "protocol": "https" },
#      { "host": "typesense-2.example.net", "port": "443", "protocol": "https" },
#      { "host": "typesense-3.example.net", "port": "443", "protocol": "https" },
# ]
# TYPESENSE_URL=ha://WwogIHsgImhvc3QiOiAidHlwZXNlbnNlLTEuZXhhbXBsZS5uZXQiLCAicG9ydCI6ICI0NDMiLCAicHJvdG9jb2wiOiAiaHR0cHMiIH0sCiAgeyAiaG9zdCI6ICJ0eXBlc2Vuc2UtMi5leGFtcGxlLm5ldCIsICJwb3J0IjogIjQ0MyIsICJwcm90b2NvbCI6ICJodHRwcyIgfSwKICB7ICJob3N0IjogInR5cGVzZW5zZS0zLmV4YW1wbGUubmV0IiwgInBvcnQiOiAiNDQzIiwgInByb3RvY29sIjogImh0dHBzIiB9Cl0=

###################################################################################
# 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

###################################################################################
# Immich Version - Optional
#
# This allows all immich docker images to be pinned to a specific version. By default,
# the version is "release" but could be a specific version, like "v1.59.0".
###################################################################################

#IMMICH_VERSION=

Reproduction steps

1. Upload > 100 assets directly to a (newly created?) album via web interface.
2. Check number of assets in immich album and note smaller number of assets than in source folder.
3. Check timeline to see missing assets are indeed on the server but not in the album.

Additional information

No response

Originally created by @raisinbear on GitHub (Aug 12, 2023). ### The bug Hi, I noticed that when creating an album in the web interface and uploading an admittedly large number of assets (~100 - 300), there is always a smaller number of assets displayed in immich than in the source folder. Roughy in the ballpark of 3% missing. I could not find anything peculiar about the assets missing, nor see anything in stdout, although messages tend to fly by quickly. Starting reuploading the missing files, I noticed duplicate entry violations in the output and followed up checking the timeline where the presumably missing files were indeed showing up. So it appears - I could only check this in 2 out of 5 instances, where assets were missing - that all my files were uploaded, but some few were not added to the album to which they were uploaded. I guess this may be a tough one, because behavior is kind of erratic, but I'll leave it here nonetheless. Thank you guys so much for all the effort! ### The OS that Immich Server is running on Debian ### Version of Immich Server v1.72.1 ### Version of Immich Mobile App v1.72.0 ### Platform with the issue - [ ] Server - [X] Web - [ ] Mobile ### Your docker-compose.yml content ```YAML version: "3.8" services: immich-server: container_name: immich_server image: ghcr.io/immich-app/immich-server:${IMMICH_VERSION:-release} command: [ "start.sh", "immich" ] volumes: - ${UPLOAD_LOCATION}:/usr/src/app/upload env_file: - .env depends_on: - redis - database - typesense restart: always immich-microservices: container_name: immich_microservices image: ghcr.io/immich-app/immich-server:${IMMICH_VERSION:-release} command: [ "start.sh", "microservices" ] volumes: - ${UPLOAD_LOCATION}:/usr/src/app/upload env_file: - .env depends_on: - redis - database - typesense restart: always immich-machine-learning: container_name: immich_machine_learning image: ghcr.io/immich-app/immich-machine-learning:${IMMICH_VERSION:-release} volumes: - model-cache:/cache env_file: - .env restart: always immich-web: container_name: immich_web image: ghcr.io/immich-app/immich-web:${IMMICH_VERSION:-release} env_file: - .env restart: always typesense: container_name: immich_typesense image: typesense/typesense:0.24.1@sha256:9bcff2b829f12074426ca044b56160ca9d777a0c488303469143dd9f8259d4dd environment: - TYPESENSE_API_KEY=${TYPESENSE_API_KEY} - TYPESENSE_DATA_DIR=/data volumes: - tsdata:/data restart: always redis: container_name: immich_redis image: redis:6.2-alpine@sha256:70a7a5b641117670beae0d80658430853896b5ef269ccf00d1827427e3263fa3 restart: always database: container_name: immich_postgres image: postgres:14-alpine@sha256:28407a9961e76f2d285dc6991e8e48893503cc3836a4755bbc2d40bcc272a441 env_file: - .env environment: POSTGRES_PASSWORD: ${DB_PASSWORD} POSTGRES_USER: ${DB_USERNAME} POSTGRES_DB: ${DB_DATABASE_NAME} volumes: - pgdata:/var/lib/postgresql/data restart: always immich-proxy: container_name: immich_proxy image: ghcr.io/immich-app/immich-proxy:${IMMICH_VERSION:-release} environment: # Make sure these values get passed through from the env file - IMMICH_SERVER_URL - IMMICH_WEB_URL ports: - 2283:8080 depends_on: - immich-server - immich-web restart: always volumes: pgdata: model-cache: tsdata: ``` ### Your .env content ```Shell ################################################################################### # Database ################################################################################### # NOTE: The following four database variables support Docker secrets by adding a *_FILE suffix to the variable name # See the docker-compose documentation on secrets for additional details: https://docs.docker.com/compose/compose-file/compose-file-v3/#secrets DB_HOSTNAME=immich_postgres DB_USERNAME=postgres DB_PASSWORD=postgres DB_DATABASE_NAME=immich # Optional Database settings: # DB_PORT=5432 ################################################################################### # Redis ################################################################################### REDIS_HOSTNAME=immich_redis # REDIS_URL will be used to pass custom options to ioredis. # Example for Sentinel # {"sentinels":[{"host":"redis-sentinel-node-0","port":26379},{"host":"redis-sentinel-node-1","port":26379},{"host":"redis-sentinel-node-2","port":26379}],"name":"redis-sentinel"} # REDIS_URL=ioredis://eyJzZW50aW5lbHMiOlt7Imhvc3QiOiJyZWRpcy1zZW50aW5lbDEiLCJwb3J0IjoyNjM3OX0seyJob3N0IjoicmVkaXMtc2VudGluZWwyIiwicG9ydCI6MjYzNzl9XSwibmFtZSI6Im15bWFzdGVyIn0= # Optional Redis settings: # Note: these parameters are not automatically passed to the Redis Container # to do so, please edit the docker-compose.yml file as well. Redis is not configured # via environment variables, only redis.conf or the command line # REDIS_PORT=6379 # REDIS_DBINDEX=0 # REDIS_USERNAME= # REDIS_PASSWORD= # REDIS_SOCKET= ################################################################################### # Upload File Location # # This is the location where uploaded files are stored. ################################################################################### UPLOAD_LOCATION=/home/immich/data ################################################################################### # Typesense ################################################################################### TYPESENSE_API_KEY=[] # TYPESENSE_ENABLED=false # TYPESENSE_URL uses base64 encoding for the nodes json. # Example JSON that was used: # [ # { "host": "typesense-1.example.net", "port": "443", "protocol": "https" }, # { "host": "typesense-2.example.net", "port": "443", "protocol": "https" }, # { "host": "typesense-3.example.net", "port": "443", "protocol": "https" }, # ] # TYPESENSE_URL=ha://WwogIHsgImhvc3QiOiAidHlwZXNlbnNlLTEuZXhhbXBsZS5uZXQiLCAicG9ydCI6ICI0NDMiLCAicHJvdG9jb2wiOiAiaHR0cHMiIH0sCiAgeyAiaG9zdCI6ICJ0eXBlc2Vuc2UtMi5leGFtcGxlLm5ldCIsICJwb3J0IjogIjQ0MyIsICJwcm90b2NvbCI6ICJodHRwcyIgfSwKICB7ICJob3N0IjogInR5cGVzZW5zZS0zLmV4YW1wbGUubmV0IiwgInBvcnQiOiAiNDQzIiwgInByb3RvY29sIjogImh0dHBzIiB9Cl0= ################################################################################### # 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 ################################################################################### # Immich Version - Optional # # This allows all immich docker images to be pinned to a specific version. By default, # the version is "release" but could be a specific version, like "v1.59.0". ################################################################################### #IMMICH_VERSION= ``` ### Reproduction steps ```bash 1. Upload > 100 assets directly to a (newly created?) album via web interface. 2. Check number of assets in immich album and note smaller number of assets than in source folder. 3. Check timeline to see missing assets are indeed on the server but not in the album. ``` ### Additional information _No response_
OVERLORD added the 🗄️server label 2026-02-05 00:54:23 +03:00
OVERLORD commented 2026-02-05 00:54:29 +03:00
Author
Owner
Copy Link

@Gyromancer commented on GitHub (Aug 12, 2023):

I've also encountered this problem when uploading a large number of photos using Web Upload. A small portion of the images are stuck in the upload folder partially loaded. I tried deleting one of these partially uploaded images and re-uploading the same image, and while the web interface says the image was successfully uploaded, it seems to go missing.

Checking the logs, I received the following errors when attempting to re-upload the photo:

[Nest] 425 - 08/12/2023, 6:58:19 PM ERROR [JobService] Unable to run job handler: Error: Input file contains unsupported image format
[Nest] 425 - 08/12/2023, 6:58:19 PM ERROR [JobService] Error: Input file contains unsupported image format
[Nest] 425 - 08/12/2023, 6:58:19 PM ERROR [JobService] Object:
{
"id": "bf67c70c-d68a-40f3-8ae3-5fa4016a2132",
"source": "upload"
}

I then ended up with an image at the top of my feed that doesn't display. When clicking on it, the server produces the following errors:

[Nest] 153 - 08/12/2023, 7:20:45 PM WARN [AssetService] WebP thumbnail requested but not found for asset bf67c70c-d68a-40f3-8ae3-5fa4016a2132, falling back to JPEG
[Nest] 153 - 08/12/2023, 7:20:45 PM ERROR [AssetService] Cannot create read stream for asset bf67c70c-d68a-40f3-8ae3-5fa4016a2132
getAssetThumbnail

However, I stopped experiencing the upload problem recently, and my Immich server is now running v1.72.2, so it may have been a problem with 1.72.1, but I'm not certain. That said, my attempts to re-upload the photos stuck in limbo still fail as described above.

@Gyromancer commented on GitHub (Aug 12, 2023): I've also encountered this problem when uploading a large number of photos using Web Upload. A small portion of the images are stuck in the upload folder partially loaded. I tried deleting one of these partially uploaded images and re-uploading the same image, and while the web interface says the image was successfully uploaded, it seems to go missing. Checking the logs, I received the following errors when attempting to re-upload the photo: > [Nest] 425 - 08/12/2023, 6:58:19 PM ERROR [JobService] Unable to run job handler: Error: Input file contains unsupported image format > [Nest] 425 - 08/12/2023, 6:58:19 PM ERROR [JobService] Error: Input file contains unsupported image format > [Nest] 425 - 08/12/2023, 6:58:19 PM ERROR [JobService] Object: > { > "id": "bf67c70c-d68a-40f3-8ae3-5fa4016a2132", > "source": "upload" > } I then ended up with an image at the top of my feed that doesn't display. When clicking on it, the server produces the following errors: > [Nest] 153 - 08/12/2023, 7:20:45 PM WARN [AssetService] WebP thumbnail requested but not found for asset bf67c70c-d68a-40f3-8ae3-5fa4016a2132, falling back to JPEG > [Nest] 153 - 08/12/2023, 7:20:45 PM ERROR [AssetService] Cannot create read stream for asset bf67c70c-d68a-40f3-8ae3-5fa4016a2132 > getAssetThumbnail However, I stopped experiencing the upload problem recently, and my Immich server is now running v1.72.2, so it may have been a problem with 1.72.1, but I'm not certain. That said, my attempts to re-upload the photos stuck in limbo still fail as described above.
OVERLORD commented 2026-02-05 00:54:34 +03:00
Author
Owner
Copy Link

@raisinbear commented on GitHub (Aug 13, 2023):

Might at least be connected, @Gyromancer. However, these messages didn't appear for me and the images were also successfully processed to the point were faces and locations are tagged. They just hadn't been added to the album I was uploading them to.
Thanks for pointing out 1.72.2! I missed that one entirely. Next time I have more to upload, I'll report back.

@raisinbear commented on GitHub (Aug 13, 2023): Might at least be connected, @Gyromancer. However, these messages didn't appear for me and the images were also successfully processed to the point were faces and locations are tagged. They just hadn't been added to the album I was uploading them to. Thanks for pointing out 1.72.2! I missed that one entirely. Next time I have more to upload, I'll report back.
OVERLORD commented 2026-02-05 00:54:39 +03:00
Author
Owner
Copy Link

@raisinbear commented on GitHub (Aug 13, 2023):

Just checked, it’s reproducible in 1.72.2 as well. This time I observed the server output and there was nothing unusual. Still 9/200 and 2/50 went „missing“, respectively.

@raisinbear commented on GitHub (Aug 13, 2023): Just checked, it’s reproducible in 1.72.2 as well. This time I observed the server output and there was nothing unusual. Still 9/200 and 2/50 went „missing“, respectively.
OVERLORD commented 2026-02-05 00:54:43 +03:00
Author
Owner
Copy Link

@raisinbear commented on GitHub (Aug 16, 2023):

Same in 1.73.0, just to update.

@raisinbear commented on GitHub (Aug 16, 2023): Same in 1.73.0, just to update.
OVERLORD commented 2026-02-05 00:54:48 +03:00
Author
Owner
Copy Link

@djmeas commented on GitHub (Aug 23, 2023):

I've just installed 1.74.0 and noticed the same quirk. I decided to upload about 1,400 photos from a big event and about 20 or 30 did not make it into the album @raisinbear.

@djmeas commented on GitHub (Aug 23, 2023): I've just installed 1.74.0 and noticed the same quirk. I decided to upload about 1,400 photos from a big event and about 20 or 30 did not make it into the album @raisinbear.
OVERLORD commented 2026-02-05 00:54:53 +03:00
Author
Owner
Copy Link

@raisinbear commented on GitHub (Aug 23, 2023):

I've just installed 1.74.0 and noticed the same quirk. I decided to upload about 1,400 photos from a big event and about 20 or 30 did not make it into the album @raisinbear.

Yeah right, forgot to update but I have noticed nothing has changed 😐. Using CLI for now, as I don’t experience it then. It’s mostly about other people who I have made accounts for. Cannot force cli on everyone 😅

@raisinbear commented on GitHub (Aug 23, 2023): > I've just installed 1.74.0 and noticed the same quirk. I decided to upload about 1,400 photos from a big event and about 20 or 30 did not make it into the album @raisinbear. Yeah right, forgot to update but I have noticed nothing has changed 😐. Using CLI for now, as I don’t experience it then. It’s mostly about other people who I have made accounts for. Cannot force cli on everyone 😅
OVERLORD commented 2026-02-05 00:54:56 +03:00
Author
Owner
Copy Link

@djmeas commented on GitHub (Aug 24, 2023):

@raisinbear I've tried using the bulk upload CLI on about 1,000 photos and noticed not all were uploaded either.

I even tested out a smaller album of 35 photos and only 33 were uploaded (despite the upload progress showing 100% and 35/35 photos). I then deleted the 35 photos and album and tried to use the same CLI command with the same results of 33 photos being uploaded but the CLI showing 35/35 uploaded.

-- Edit --
FYI that I do end up seeing the missing images within the upload folder so perhaps there's something about processing those items and moving them to the actual library?

@djmeas commented on GitHub (Aug 24, 2023): @raisinbear I've tried using the bulk upload CLI on about 1,000 photos and noticed not all were uploaded either. I even tested out a smaller album of 35 photos and only 33 were uploaded (despite the upload progress showing 100% and 35/35 photos). I then deleted the 35 photos and album and tried to use the same CLI command with the same results of 33 photos being uploaded but the CLI showing 35/35 uploaded. -- Edit -- FYI that I do end up seeing the missing images within the `upload` folder so perhaps there's something about processing those items and moving them to the actual library?
OVERLORD commented 2026-02-05 00:55:01 +03:00
Author
Owner
Copy Link

@rlegan commented on GitHub (Oct 17, 2023):

hi!

anyone got any news on this ? experiencing it in 1.82.0.
for about 200 photos uploaded, at least 6 were not uploaded and stuck inside the upload folder.
what should I do to force it to sync ?
it wasn't even showing up on the mobile app and the file in the upload folder were in majority .mov file and there were not valid files.

would love to use immich but if some of my photos/videos are missing when syncing, i can't trust it and don't want to use it... thats a bummer 😞

thanks!

@rlegan commented on GitHub (Oct 17, 2023): hi! anyone got any news on this ? experiencing it in 1.82.0. for about 200 photos uploaded, at least 6 were not uploaded and stuck inside the upload folder. what should I do to force it to sync ? it wasn't even showing up on the mobile app and the file in the upload folder were in majority .mov file and there were not valid files. would love to use immich but if some of my photos/videos are missing when syncing, i can't trust it and don't want to use it... thats a bummer 😞 thanks!
OVERLORD commented 2026-02-05 00:55:02 +03:00
Author
Owner
Copy Link

@alextran1502 commented on GitHub (Oct 17, 2023):

@rlegan if you can please head over to Discord and provide the information that you have tried, we might be able to explain and walk you through the solution

@alextran1502 commented on GitHub (Oct 17, 2023): @rlegan if you can please head over to Discord and provide the information that you have tried, we might be able to explain and walk you through the solution
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
accessibility
changelog:enhancement
changelog:security
changelog:skip
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 🗄️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#1217
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?