[BUG] CLI: bulk uploaded albums are not ordered by date (and some videos too) #853

Closed
opened 2026-02-04 23:04:00 +03:00 by OVERLORD · 3 comments
Owner

Originally created by @usikpavel on GitHub (May 16, 2023).

The bug

Thank you for very helpful CLI tool! I've used it to upload some albums downloaded from Google Photos. And there is an issue with ordering by date.

Scenario:

  • download Google Photo album as .zip-file
  • unpack it to a folder
  • (optionally) check that all files have correct LastModified date
  • go to that folder and run a PowerShell script there (I'm using Windows):
    $currentDirName = Split-Path -Path $pwd -Leaf
    docker run -it --rm -v "$(pwd):/import" ghcr.io/immich-app/immich-cli:latest upload --key xxxKEYxxx --server http://192.168.2.7:2283/api -al "$($currentDirName)" -y

Here are 2 issues in result:

  1. album is not ordered by date. It is the first in the Albums list. (But I have created manually some new albums with more new photos/videos before.)
  2. some videos has invalid (empty) metadata dates, but correct Created and LastModified dates. So they are uploaded and ordered in Photos list with invalid date 01.01.1970, for example:

image

What I've tried to resolve the issues:

  • set folder's Created and LastModified dates from the first photo file in the album (for ex., 04-05-2023, dd-mm-yyyy)
  • set photo/video files Created = LastModified
  • then remove photos/videos/album and upload album again

No success.

The OS that Immich Server is running on

Windows 10

Version of Immich Server

v1.55.1

Version of Immich Mobile App

v1.55.0 build.78

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:release
    entrypoint: ["/bin/sh", "./start-server.sh"]
    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:release
    entrypoint: ["/bin/sh", "./start-microservices.sh"]
    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:release
    volumes:
      - ${UPLOAD_LOCATION}:/usr/src/app/upload
      - model-cache:/cache
    env_file:
      - .env
    restart: always

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

  typesense:
    container_name: immich_typesense
    image: typesense/typesense:0.24.0
    environment:
      - TYPESENSE_API_KEY=${TYPESENSE_API_KEY}
      - TYPESENSE_DATA_DIR=/data
    logging:
      driver: none
    volumes:
      - tsdata:/data
    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: ghcr.io/immich-app/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:
  tsdata:

Your .env content

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

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

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





###################################################################################
# Upload File Config
###################################################################################

UPLOAD_LOCATION=./photos

###################################################################################
# Typesense
###################################################################################
TYPESENSE_API_KEY=some-random-text
# 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://WwogICAgeyAnaG9zdCc6ICd0eXBlc2Vuc2UtMS5leGFtcGxlLm5ldCcsICdwb3J0JzogJzQ0MycsICdwcm90b2NvbCc6ICdodHRwcycgfSwKICAgIHsgJ2hvc3QnOiAndHlwZXNlbnNlLTIuZXhhbXBsZS5uZXQnLCAncG9ydCc6ICc0NDMnLCAncHJvdG9jb2wnOiAnaHR0cHMnIH0sCiAgICB7ICdob3N0JzogJ3R5cGVzZW5zZS0zLmV4YW1wbGUubmV0JywgJ3BvcnQnOiAnNDQzJywgJ3Byb3RvY29sJzogJ2h0dHBzJyB9LApd

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

#DISABLE_REVERSE_GEOCODING=true


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


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

- download Google Photo album as .zip-file
- unpack it to a folder
- (optionally) check that all files have correct _LastModified_ date
- go to that folder and run a PowerShell script there (I'm using Windows):
`$currentDirName = Split-Path -Path $pwd -Leaf`
`docker run -it --rm -v "$(pwd):/import" ghcr.io/immich-app/immich-cli:latest upload --key xxxKEYxxx --server http://192.168.2.7:2283/api -al "$($currentDirName)" -y`

Additional information

No response

Originally created by @usikpavel on GitHub (May 16, 2023). ### The bug Thank you for very helpful CLI tool! I've used it to upload some albums downloaded from Google Photos. And there is an issue with ordering by date. Scenario: - download Google Photo album as .zip-file - unpack it to a folder - (optionally) check that all files have correct _LastModified_ date - go to that folder and run a PowerShell script there (I'm using Windows): `$currentDirName = Split-Path -Path $pwd -Leaf` `docker run -it --rm -v "$(pwd):/import" ghcr.io/immich-app/immich-cli:latest upload --key xxxKEYxxx --server http://192.168.2.7:2283/api -al "$($currentDirName)" -y` Here are 2 issues in result: 1. album is not ordered by date. It is the first in the _Albums_ list. (But I have created manually some new albums with more new photos/videos before.) 2. some videos has invalid (empty) _metadata_ dates, but correct _Created_ and _LastModified_ dates. So they are uploaded and ordered in _Photos_ list with invalid date 01.01.1970, for example: ![image](https://github.com/immich-app/immich/assets/18679813/471306a3-df02-4c65-9bf1-3035bd7f9e72) What I've tried to resolve the issues: - set folder's _Created_ and _LastModified_ dates from the first photo file in the album (for ex., 04-05-2023, _dd-mm-yyyy_) - set photo/video files _Created_ = _LastModified_ - then remove photos/videos/album and upload album again No success. ### The OS that Immich Server is running on Windows 10 ### Version of Immich Server v1.55.1 ### Version of Immich Mobile App v1.55.0 build.78 ### Platform with the issue - [X] Server - [ ] 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:release entrypoint: ["/bin/sh", "./start-server.sh"] 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:release entrypoint: ["/bin/sh", "./start-microservices.sh"] 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:release volumes: - ${UPLOAD_LOCATION}:/usr/src/app/upload - model-cache:/cache env_file: - .env restart: always immich-web: container_name: immich_web image: ghcr.io/immich-app/immich-web:release entrypoint: ["/bin/sh", "./entrypoint.sh"] env_file: - .env restart: always typesense: container_name: immich_typesense image: typesense/typesense:0.24.0 environment: - TYPESENSE_API_KEY=${TYPESENSE_API_KEY} - TYPESENSE_DATA_DIR=/data logging: driver: none volumes: - tsdata:/data 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: ghcr.io/immich-app/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: tsdata: ``` ### Your .env content ```Shell ################################################################################### # Database ################################################################################### 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 # Optional Redis settings: # REDIS_PORT=6379 # REDIS_DBINDEX=0 # REDIS_PASSWORD= # REDIS_SOCKET= ################################################################################### # Upload File Config ################################################################################### UPLOAD_LOCATION=./photos ################################################################################### # Typesense ################################################################################### TYPESENSE_API_KEY=some-random-text # 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://WwogICAgeyAnaG9zdCc6ICd0eXBlc2Vuc2UtMS5leGFtcGxlLm5ldCcsICdwb3J0JzogJzQ0MycsICdwcm90b2NvbCc6ICdodHRwcycgfSwKICAgIHsgJ2hvc3QnOiAndHlwZXNlbnNlLTIuZXhhbXBsZS5uZXQnLCAncG9ydCc6ICc0NDMnLCAncHJvdG9jb2wnOiAnaHR0cHMnIH0sCiAgICB7ICdob3N0JzogJ3R5cGVzZW5zZS0zLmV4YW1wbGUubmV0JywgJ3BvcnQnOiAnNDQzJywgJ3Byb3RvY29sJzogJ2h0dHBzJyB9LApd ################################################################################### # 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 #DISABLE_REVERSE_GEOCODING=true #################################################################################### # 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 #################################################################################### # 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 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 - download Google Photo album as .zip-file - unpack it to a folder - (optionally) check that all files have correct _LastModified_ date - go to that folder and run a PowerShell script there (I'm using Windows): `$currentDirName = Split-Path -Path $pwd -Leaf` `docker run -it --rm -v "$(pwd):/import" ghcr.io/immich-app/immich-cli:latest upload --key xxxKEYxxx --server http://192.168.2.7:2283/api -al "$($currentDirName)" -y` ``` ### Additional information _No response_
OVERLORD added the 🗄️server label 2026-02-04 23:04:00 +03:00
Author
Owner

@alextran1502 commented on GitHub (Nov 1, 2023):

Hello is this issue still relevance? if not, can you help me close it?

@alextran1502 commented on GitHub (Nov 1, 2023): Hello is this issue still relevance? if not, can you help me close it?
Author
Owner

@usikpavel commented on GitHub (Nov 1, 2023):

Perhaps, the issue is fixed. I didn't reproduce an issue again (did not bulk-upload some assets). But now what I have:

  1. I've upated the Immich to the latest version 1.83.0 and runned a job to extract metadata.
  2. In my library I have initially bulk-uploaded videos that I described in this issue as an example. I don't see the videos with 1970:01:01 date anymore.
  3. And it looks like the videos are ordered correctly.
@usikpavel commented on GitHub (Nov 1, 2023): Perhaps, the issue is fixed. I didn't reproduce an issue again (did not bulk-upload some assets). But now what I have: 1. I've upated the Immich to the latest version 1.83.0 and runned a job to extract metadata. 2. In my library I have initially bulk-uploaded videos that I described in this issue as an example. I don't see the videos with 1970:01:01 date anymore. 3. And it looks like the videos are ordered correctly.
Author
Owner

@jrasm91 commented on GitHub (Nov 1, 2023):

We have definitely fixed some issues with regards to video metadata extraction, so glad to hear it is working correctly now.

@jrasm91 commented on GitHub (Nov 1, 2023): We have definitely fixed some issues with regards to video metadata extraction, so glad to hear it is working correctly now.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: immich-app/immich#853