#Upgrade from 135 to 135.1 server keeps stopping with errors
1 messages · Page 1 of 1 (latest)
:wave: Hey @round goblet,
Thanks for reaching out to us. Please carefully read this message and follow the recommended actions. This will help us be more effective in our support effort and leave more time for building Immich
.
References
- Container Logs:
docker compose logsdocs - Container Status:
docker ps -adocs - Reverse Proxy: https://immich.app/docs/administration/reverse-proxy
- Code Formatting https://support.discord.com/hc/en-us/articles/210298617-Markdown-Text-101-Chat-Formatting-Bold-Italic-Underline#h_01GY0DAKGXDEHE263BCAYEGFJA
Checklist
I have...
- :ballot_box_with_check: verified I'm on the latest release(note that mobile app releases may take some time).
- :ballot_box_with_check: read applicable release notes.
- :ballot_box_with_check: reviewed the FAQs for known issues.
- :ballot_box_with_check: reviewed Github for known issues.
- :ballot_box_with_check: tried accessing Immich via local ip (without a custom reverse proxy).
- :ballot_box_with_check: uploaded the relevant information (see below).
- :blue_square: tried an incognito window, disabled extensions, cleared mobile app cache, logged out and back in, different browsers, etc. as applicable
(an item can be marked as "complete" by reacting with the appropriate number)
Information
In order to be able to effectively help you, we need you to provide clear information to show what the problem is. The exact details needed vary per case, but here is a list of things to consider:
- Your docker-compose.yml and .env files.
- Logs from all the containers and their status (see above).
- All the troubleshooting steps you've tried so far.
- Any recent changes you've made to Immich or your system.
- Details about your system (both software/OS and hardware).
- Details about your storage (filesystems, type of disks, output of commands like
fdisk -landdf -h). - The version of the Immich server, mobile app, and other relevant pieces.
- Any other information that you think might be relevant.
Please paste files and logs with proper code formatting, and especially avoid blurry screenshots.
Without the right information we can't work out what the problem is. Help us help you ;)
If this ticket can be closed you can use the /close command, and re-open it later if needed.
Successfully submitted, a tag has been added to inform contributors. :white_check_mark:
Portainer stack YML:
services:
immich-redis:
image: redis
container_name: Immich-REDIS
hostname: immich-redis
security_opt:
- no-new-privileges:true
healthcheck:
test: ["CMD-SHELL", "redis-cli ping || exit 1"]
user: 1026:100
environment:
- TZ=Europe/Amsterdam
volumes:
- /volume1/docker/immich/redis:/data:rw
restart: on-failure:5
immich-db:
image: ghcr.io/immich-app/postgres:16-vectorchord0.4.2-pgvectors0.2.0 #16-vectorchord0.3.0-pgvectors0.2.0
container_name: Immich-DB
hostname: immich-db
security_opt:
- no-new-privileges:true
volumes:
- /volume1/docker/immich/db:/var/lib/postgresql/data:rw
environment:
- TZ=Europe/Amsterdam
- POSTGRES_DB=immich
- POSTGRES_USER=immichuser
- POSTGRES_PASSWORD=immichpw
- DB_STORAGE_TYPE=HDD
restart: on-failure:5
immich-server:
image: ghcr.io/immich-app/immich-server:release
container_name: Immich-SERVER
hostname: immich-server
user: 1026:100
security_opt:
- no-new-privileges:true
env_file:
- stack.env
ports:
- 8212:2283
volumes:
- /volume1/docker/immich/upload:/usr/src/app/upload:rw
restart: on-failure:5
depends_on:
immich-redis:
condition: service_healthy
immich-db:
condition: service_started
immich-machine-learning:
image: ghcr.io/immich-app/immich-machine-learning:release
container_name: Immich-LEARNING
hostname: immich-machine-learning
user: 1026:100
security_opt:
- no-new-privileges:true
env_file:
- stack.env
volumes:
- /volume1/docker/immich/upload:/usr/src/app/upload:rw
- /volume1/docker/immich/cache:/cache:rw
- /volume1/docker/immich/matplotlib:/matplotlib:rw
environment:
- MPLCONFIGDIR=/matplotlib
restart: on-failure:5
depends_on:
immich-db:
condition: service_started
Just to verify, standard installation via portainer on synology NAS. The #19313 issue is gone after the 1.135.2 bugfix
Running on Server v1.135.2 and postgres:16-vectorchord0.4.3-pgvectors0.2.0 now without any problems so far! Thanks devs!
[Issue] 1.135.1 fails to start with vchord 4.2 when using PostgreSQL 15 or later (immich-app/immich#19313)
Warnings on the prewarm also gone