You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have searched the existing issues, both open and closed, to make sure this is not a duplicate report.
Yes
The bug
By scrolling through the pictures with the right arrow in the Photos view (movong backwards in time) Immich jumps a few days ahead when reaching the last picture of a day (e.g. clicking the right arrow on the last picture of 22.01.2022 shows the first picture of 29.12.2021 instead of 21.01.2022). Similar behaviour when clicking left (moving forward in time). Immich jumps to a certain date
There is no regularity or pattern to be seen (at least not by me...).
The OS that Immich Server is running on
Ubuntu 24.04 Server
Version of Immich Server
v1.130
Version of Immich Mobile App
v1.129.0 build 197
Platform with the issue
Server
Web
Mobile
Your docker-compose.yml content
## WARNING: To install Immich, follow our guide: https://immich.app/docs/install/docker-compose## 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: immichservices:
immich-server:
container_name: immich_serverimage: ghcr.io/immich-app/immich-server:${IMMICH_VERSION:-release}# extends:# file: hwaccel.transcoding.yml# service: cpu # set to one of [nvenc, quicksync, rkmpp, vaapi, vaapi-wsl] for accelerated transcodingvolumes:
# Do not edit the next line. If you want to change the media storage location on your system, edit the value of UPLOAD_LOCATION in the .env file
- ${UPLOAD_LOCATION}:/usr/src/app/upload
- /mnt/fotos:/mnt/fotos:ro
- /etc/localtime:/etc/localtime:roenv_file:
- .envports:
- '2283:2283'depends_on:
- redis
- databaserestart: alwayshealthcheck:
disable: falseimmich-machine-learning:
container_name: immich_machine_learning# For hardware acceleration, add one of -[armnn, cuda, openvino] to the image tag.# Example tag: ${IMMICH_VERSION:-release}-cudaimage: ghcr.io/immich-app/immich-machine-learning:${IMMICH_VERSION:-release}# extends: # uncomment this section for hardware acceleration - see https://immich.app/docs/features/ml-hardware-acceleration# file: hwaccel.ml.yml# service: cpu # set to one of [armnn, cuda, openvino, openvino-wsl] for accelerated inference - use the `-wsl` version for WSL2 where applicablevolumes:
- model-cache:/cacheenv_file:
- .envrestart: alwayshealthcheck:
disable: falseredis:
container_name: immich_redisimage: docker.io/redis:6.2-alpine@sha256:148bb5411c184abd288d9aaed139c98123eeb8824c5d3fce03cf721db58066d8healthcheck:
test: redis-cli ping || exit 1restart: alwaysdatabase:
container_name: immich_postgresimage: docker.io/tensorchord/pgvecto-rs:pg14-v0.2.0@sha256:739cdd626151ff1f796dc95a6591b55a714f341c737e27f045019ceabf8e8c52environment:
POSTGRES_PASSWORD: ${DB_PASSWORD}POSTGRES_USER: ${DB_USERNAME}POSTGRES_DB: ${DB_DATABASE_NAME}POSTGRES_INITDB_ARGS: '--data-checksums'volumes:
# Do not edit the next line. If you want to change the database storage location on your system, edit the value of DB_DATA_LOCATION in the .env file
- ${DB_DATA_LOCATION}:/var/lib/postgresql/datahealthcheck:
test: >- pg_isready --dbname="$${POSTGRES_DB}" --username="$${POSTGRES_USER}" || exit 1; Chksum="$$(psql --dbname="$${POSTGRES_DB}" --username="$${POSTGRES_USER}" --tuples-only --no-align --command='SELECT COALESCE(SUM(checksum_failures), 0) FROM pg_stat_database')"; echo "checksum failure count is $$Chksum"; [ "$$Chksum" = '0' ] || exit 1interval: 5mstart_interval: 30sstart_period: 5mcommand: >- postgres -c shared_preload_libraries=vectors.so -c 'search_path="$$user", public, vectors' -c logging_collector=on -c max_wal_size=2GB -c shared_buffers=512MB -c wal_compression=onrestart: alwaysvolumes:
model-cache:
# nfs-docker-upload:# driver_opts:# type: "nfs"# o: "addr=192.168.178.112,nfsvers=4.1,rw"# device: ":/mnt/Pool_01/docker/immich"
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/immich_upload
#UPLOAD_LOCATION=./library# The location where your database files are stored
DB_DATA_LOCATION=./postgres
# To set a timezone, uncomment the next line and change Etc/UTC to a TZ identifier from this list: https://en.wikipedia.org/wiki/List_of_tz_database_time_zones#List# TZ=Etc/UTC# 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# Please use only the characters `A-Za-z0-9`, without special characters or spaces
DB_PASSWORD=postgres
# The values below this line do not need to be changed###################################################################################
DB_USERNAME=postgres
DB_DATABASE_NAME=immich
Reproduction steps
Open Photos view
Scroll through pictures by either using left or right arrow
Scroll as long as the dates jumps several days or weeks ahead or back in time
...
Relevant log output
Didn't find any relevant output
Additional information
No response
The text was updated successfully, but these errors were encountered:
I have searched the existing issues, both open and closed, to make sure this is not a duplicate report.
The bug
By scrolling through the pictures with the right arrow in the Photos view (movong backwards in time) Immich jumps a few days ahead when reaching the last picture of a day (e.g. clicking the right arrow on the last picture of 22.01.2022 shows the first picture of 29.12.2021 instead of 21.01.2022). Similar behaviour when clicking left (moving forward in time). Immich jumps to a certain date
There is no regularity or pattern to be seen (at least not by me...).
The OS that Immich Server is running on
Ubuntu 24.04 Server
Version of Immich Server
v1.130
Version of Immich Mobile App
v1.129.0 build 197
Platform with the issue
Your docker-compose.yml content
Your .env content
Reproduction steps
...
Relevant log output
Didn't find any relevant output
Additional information
No response
The text was updated successfully, but these errors were encountered: