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] Immich app continously reuploads images #1086

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

Originally created by @easez88 on GitHub (Jul 10, 2023).

The bug

Immich IOS app appears to continuously try to upload the same images. The issue that I had to reinitialize Immich and used the CLI to upload all the images previously uploaded from my phone to Immich again. Now when I open the app, Immich starts attempting to back up photos on my phone, assume sees that they exist in the server already and ignores them. The Total Number and remainder number go down all the way to zero, but the back up number never increases.

I believe the issue is that the app checks to see if the app is already in the server and does not reupload it, but it does not mark it as uploaded so it does not try to back it up again next time the back up job runs or when the app opens.

Please let me know if this is not clear. I can try to explain better.

The OS that Immich Server is running on

Fedora 37

Version of Immich Server

v1.66.1

Version of Immich Mobile App

v1.66.0 Build.106

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:
      - data:/usr/src/app/upload
    env_file:
      - stack.env
    environment:
      - NODE_ENV=production
    depends_on:
      - redis
      - postgres
      - typesense
    restart: always
    ports:
      - 3001:3001

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

  immich-machine-learning:
    container_name: immich_machine_learning
    image: ghcr.io/immich-app/immich-machine-learning:${IMMICH_VERSION:-release}
    deploy:
        resources:
            limits:
              cpus: "0.5"
    volumes:
      - data:/usr/src/app/upload
      - model-cache:/cache
    env_file:
      - stack.env
    restart: always

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

  typesense:
    container_name: immich_typesense
    image: typesense/typesense:0.24.0
    environment:
      - TYPESENSE_DATA_DIR=/data
    env_file:
      - stack.env
    logging:
      driver: none
    volumes:
      - tsdata:/data
    restart: always
      
  redis:
    container_name: immich_redis
    image: redis:6.2
    restart: always

  postgres:
    container_name: immich_postgres
    image: postgres:14
    env_file:
      - stack.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

volumes:
  data:
  pgdata:
  model-cache:
  tsdata:

Your .env content

DB_HOSTNAME=immich_postgres
DB_USERNAME=postgres
DB_PASSWORD=PASSWORD
DB_DATABASE_NAME=immich
REDIS_HOSTNAME=immich_redis
UPLOAD_LOCATION=/location
DISABLE_REVERSE_GEOCODING=false
REVERSE_GEOCODING_PRECISION=3
PUBLIC_LOGIN_PAGE_MESSAGE="My photos"
IMMICH_WEB_URL=http://immich-web:3000
IMMICH_SERVER_URL=http://immich-server:3001
IMMICH_MACHINE_LEARNING_URL=http://immich-machine-learning:3003
TYPESENSE_API_KEY=APIKEY

Reproduction steps

1. Set up immich 
2. Upload previously backed up photos using immich upload cli command. 
3. Set up app on phone
4. Start upload. 
5. Immich will recognize process each photo and recognize that they don't need to be uploaded again. 
6. Wait for back up to finish, then close and reopen immich. 
5. Processing will start again. 
...

Additional information

No response

Originally created by @easez88 on GitHub (Jul 10, 2023). ### The bug Immich IOS app appears to continuously try to upload the same images. The issue that I had to reinitialize Immich and used the CLI to upload all the images previously uploaded from my phone to Immich again. Now when I open the app, Immich starts attempting to back up photos on my phone, assume sees that they exist in the server already and ignores them. The Total Number and remainder number go down all the way to zero, but the back up number never increases. I believe the issue is that the app checks to see if the app is already in the server and does not reupload it, but it does not mark it as uploaded so it does not try to back it up again next time the back up job runs or when the app opens. Please let me know if this is not clear. I can try to explain better. ### The OS that Immich Server is running on Fedora 37 ### Version of Immich Server v1.66.1 ### Version of Immich Mobile App v1.66.0 Build.106 ### Platform with the issue - [ ] Server - [ ] Web - [X] 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: - data:/usr/src/app/upload env_file: - stack.env environment: - NODE_ENV=production depends_on: - redis - postgres - typesense restart: always ports: - 3001:3001 immich-microservices: container_name: immich_microservices image: ghcr.io/immich-app/immich-server:${IMMICH_VERSION:-release} command: [ "start.sh", "microservices" ] volumes: - data:/usr/src/app/upload env_file: - stack.env environment: - NODE_ENV=production depends_on: - redis - postgres - typesense restart: always immich-machine-learning: container_name: immich_machine_learning image: ghcr.io/immich-app/immich-machine-learning:${IMMICH_VERSION:-release} deploy: resources: limits: cpus: "0.5" volumes: - data:/usr/src/app/upload - model-cache:/cache env_file: - stack.env restart: always immich-web: container_name: immich_web image: ghcr.io/immich-app/immich-web:${IMMICH_VERSION:-release} env_file: - stack.env restart: always ports: - 3000:3000 typesense: container_name: immich_typesense image: typesense/typesense:0.24.0 environment: - TYPESENSE_DATA_DIR=/data env_file: - stack.env logging: driver: none volumes: - tsdata:/data restart: always redis: container_name: immich_redis image: redis:6.2 restart: always postgres: container_name: immich_postgres image: postgres:14 env_file: - stack.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 volumes: data: pgdata: model-cache: tsdata: ``` ### Your .env content ```Shell DB_HOSTNAME=immich_postgres DB_USERNAME=postgres DB_PASSWORD=PASSWORD DB_DATABASE_NAME=immich REDIS_HOSTNAME=immich_redis UPLOAD_LOCATION=/location DISABLE_REVERSE_GEOCODING=false REVERSE_GEOCODING_PRECISION=3 PUBLIC_LOGIN_PAGE_MESSAGE="My photos" IMMICH_WEB_URL=http://immich-web:3000 IMMICH_SERVER_URL=http://immich-server:3001 IMMICH_MACHINE_LEARNING_URL=http://immich-machine-learning:3003 TYPESENSE_API_KEY=APIKEY ``` ### Reproduction steps ```bash 1. Set up immich 2. Upload previously backed up photos using immich upload cli command. 3. Set up app on phone 4. Start upload. 5. Immich will recognize process each photo and recognize that they don't need to be uploaded again. 6. Wait for back up to finish, then close and reopen immich. 5. Processing will start again. ... ``` ### Additional information _No response_
OVERLORD added the 📱mobile label 2026-02-05 00:23:38 +03:00
OVERLORD commented 2026-02-05 00:23:43 +03:00
Author
Owner
Copy Link

@lividhen commented on GitHub (Jul 21, 2023):

Also experiencing this

@lividhen commented on GitHub (Jul 21, 2023): Also experiencing this
OVERLORD commented 2026-02-05 00:23:47 +03:00
Author
Owner
Copy Link

@alextran1502 commented on GitHub (Jul 21, 2023):

@easez88 Sorry for not responding to this. What you are experiencing is the expected behavior. Since the assets were uploaded from the CLI, the mobile app uploading process will receive a status code from the server stating the assets existed on the server, therefore the app would black-listing them so that they won't be uploaded again for the following runs.

@lividhen Is your behavior similar to OP? that you upload from the CLI first then upload from the mobile?

The future improvement will be calculating the hash of the assets from the mobile app and then check the hash with the server to avoid uploading assets to the server for duplication checking, therefore reducing bandwidth and less confusing

@alextran1502 commented on GitHub (Jul 21, 2023): @easez88 Sorry for not responding to this. What you are experiencing is the expected behavior. Since the assets were uploaded from the CLI, the mobile app uploading process will receive a status code from the server stating the assets existed on the server, therefore the app would black-listing them so that they won't be uploaded again for the following runs. @lividhen Is your behavior similar to OP? that you upload from the CLI first then upload from the mobile? The future improvement will be calculating the hash of the assets from the mobile app and then check the hash with the server to avoid uploading assets to the server for duplication checking, therefore reducing bandwidth and less confusing
OVERLORD commented 2026-02-05 00:23:52 +03:00
Author
Owner
Copy Link

@lividhen commented on GitHub (Jul 21, 2023):

Yes that is correct. I have since fixed it as it was an issue with my reverse proxy which I hadn't realized, so I'm not sure how much immich was involved.

@lividhen commented on GitHub (Jul 21, 2023): Yes that is correct. I have since fixed it as it was an issue with my reverse proxy which I hadn't realized, so I'm not sure how much immich was involved.
OVERLORD commented 2026-02-05 00:23:56 +03:00
Author
Owner
Copy Link

@easez88 commented on GitHub (Jul 21, 2023):

Ok good to know thatnks

@easez88 commented on GitHub (Jul 21, 2023): Ok good to know thatnks
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
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#1086
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?