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 25 Packages Projects Releases 10 Wiki Activity

File upload wrongly skips previously deleted assets #2153

New Issue
Closed
opened 2026-02-05 05:19:57 +03:00 by OVERLORD · 2 comments
OVERLORD commented 2026-02-05 05:19:57 +03:00
Owner
Copy Link

Originally created by @fritut08 on GitHub (Feb 11, 2024).

The bug

If a file is deleted within immich (using the trash can icon), it is left untouched in the filesystem but only receives an entry "deletedAt" in the database. This makes it disappear from the photo history and show up in the trash instead. If one now tries to upload the same file again, immich detects the file in the filesystem and skips the upload. Consequently, the file is left in the trash and still does not appear in the photo history.

If I try to upload a file, I would expect it to appear in the photo history regardless of whether it had previously been deleted.

A fix to this bug might still skip the upload but should then erase the "deletedAt" entry of the asset in the database so that it appears in the photo history again.

The OS that Immich Server is running on

Debian GNU/Linux 12 (bookworm) LXC within Proxmox

Version of Immich Server

v1.94.1

Version of Immich Mobile App

v1.92.0 build.117

Platform with the issue

  • Server
  • Web
  • Mobile

Your docker-compose.yml content

version: "3.8"

#
# WARNING: Make sure to use the docker-compose.yml of the current release:
#
# https://github.com/immich-app/immich/releases/latest/download/docker-compose.yml
#
# The compose file on main may not be compatible with the latest release.
#

name: immich

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
      - /etc/localtime:/etc/localtime:ro
    env_file:
      - .env
    ports:
      - 2283:3001
    depends_on:
      - redis
      - database
    restart: always

  immich-microservices:
    container_name: immich_microservices
    image: ghcr.io/immich-app/immich-server:${IMMICH_VERSION:-release}
    # extends:
    #   file: hwaccel.yml
    #   service: hwaccel
    command: [ "start.sh", "microservices" ]
    volumes:
      - ${UPLOAD_LOCATION}:/usr/src/app/upload
      - /etc/localtime:/etc/localtime:ro
    env_file:
      - .env
    depends_on:
      - redis
      - database
    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

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

  database:
    container_name: immich_postgres
    image: tensorchord/pgvecto-rs:pg14-v0.1.11@sha256:0335a1a22f8c5dd1b697f14f079934f5152eaaa216c09b61e293be285491f8ee
    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

volumes:
  pgdata:
  model-cache:

Your .env content

# You can find documentation for all the supported env variables at https://immich.app/docs/install/environment-variables

# The location where your uploaded files are stored
UPLOAD_LOCATION=/mnt/hdd

# The Immich version to use. You can pin this to a specific version like "v1.71.0"
IMMICH_VERSION=release

# Connection secret for postgres. You should change it to a random password
DB_PASSWORD=MYRANDOMPASSWORD

# The values below this line do not need to be changed
###################################################################################
DB_HOSTNAME=immich_postgres
DB_USERNAME=postgres
DB_DATABASE_NAME=immich

REDIS_HOSTNAME=immich_redis

Reproduction steps

1. Upload file to immich.
2. Delete file within immich (trash can icon).
3. Try to upload file again.
4. Immich will say that the file is a duplicate and the upload is thus skipped. The file does not appear in the photo history but stays in the trash.

Additional information

Related discussion

Originally created by @fritut08 on GitHub (Feb 11, 2024). ### The bug If a file is deleted within immich (using the trash can icon), it is left untouched in the filesystem but only receives an entry "deletedAt" in the database. This makes it disappear from the photo history and show up in the trash instead. If one now tries to upload the same file again, immich detects the file in the filesystem and skips the upload. Consequently, the file is left in the trash and still does not appear in the photo history. If I try to upload a file, I would expect it to appear in the photo history regardless of whether it had previously been deleted. A fix to this bug might still skip the upload but should then erase the "deletedAt" entry of the asset in the database so that it appears in the photo history again. ### The OS that Immich Server is running on Debian GNU/Linux 12 (bookworm) LXC within Proxmox ### Version of Immich Server v1.94.1 ### Version of Immich Mobile App v1.92.0 build.117 ### Platform with the issue - [X] Server - [X] Web - [X] Mobile ### Your docker-compose.yml content ```YAML version: "3.8" # # WARNING: Make sure to use the docker-compose.yml of the current release: # # https://github.com/immich-app/immich/releases/latest/download/docker-compose.yml # # The compose file on main may not be compatible with the latest release. # name: immich 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 - /etc/localtime:/etc/localtime:ro env_file: - .env ports: - 2283:3001 depends_on: - redis - database restart: always immich-microservices: container_name: immich_microservices image: ghcr.io/immich-app/immich-server:${IMMICH_VERSION:-release} # extends: # file: hwaccel.yml # service: hwaccel command: [ "start.sh", "microservices" ] volumes: - ${UPLOAD_LOCATION}:/usr/src/app/upload - /etc/localtime:/etc/localtime:ro env_file: - .env depends_on: - redis - database 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 redis: container_name: immich_redis image: redis:6.2-alpine@sha256:c5a607fb6e1bb15d32bbcf14db22787d19e428d59e31a5da67511b49bb0f1ccc restart: always database: container_name: immich_postgres image: tensorchord/pgvecto-rs:pg14-v0.1.11@sha256:0335a1a22f8c5dd1b697f14f079934f5152eaaa216c09b61e293be285491f8ee 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 volumes: pgdata: model-cache: ``` ### Your .env content ```Shell # You can find documentation for all the supported env variables at https://immich.app/docs/install/environment-variables # The location where your uploaded files are stored UPLOAD_LOCATION=/mnt/hdd # The Immich version to use. You can pin this to a specific version like "v1.71.0" IMMICH_VERSION=release # Connection secret for postgres. You should change it to a random password DB_PASSWORD=MYRANDOMPASSWORD # The values below this line do not need to be changed ################################################################################### DB_HOSTNAME=immich_postgres DB_USERNAME=postgres DB_DATABASE_NAME=immich REDIS_HOSTNAME=immich_redis ``` ### Reproduction steps ```bash 1. Upload file to immich. 2. Delete file within immich (trash can icon). 3. Try to upload file again. 4. Immich will say that the file is a duplicate and the upload is thus skipped. The file does not appear in the photo history but stays in the trash. ``` ### Additional information [Related discussion](https://github.com/immich-app/immich/discussions/6381)
OVERLORD commented 2026-02-05 05:20:02 +03:00
Author
Owner
Copy Link

@martabal commented on GitHub (Feb 11, 2024):

I think this is the desired behavior, but another warning can be added to avoid that kind of confusion

@martabal commented on GitHub (Feb 11, 2024): I think this is the desired behavior, but another warning can be added to avoid that kind of confusion
OVERLORD commented 2026-02-05 05:20:06 +03:00
Author
Owner
Copy Link

@aviv926 commented on GitHub (Feb 12, 2024):

Duplicate of https://github.com/immich-app/immich/issues/6639

@aviv926 commented on GitHub (Feb 12, 2024): Duplicate of https://github.com/immich-app/immich/issues/6639
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
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#2153
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?