#unable to connect after upgrade

1 messages · Page 1 of 1 (latest)

stone tiger
#

I upgraded from 1.131 to 1.141 today, I followed the breaking update instructions for 1.133 and made the edits to the docker-compose.yml before running docker compose pull && docker compose up -d
The breaking changes instructions for 1.136 didn't seem to apply to me as I do not have "IMMICH_MEDIA_LOCATION" in my .env
For the breaking changes in 1.137, I missed the part for the TypeORM Upgrade, but after it failing initially I went back to double check and then set the version to "v1.133.0" in the.env before running the upgrade again (I used 1.133 instead of the suggested 1.132 because I had already made the changes to the docker-compose-yml for 1.133)
Once I did, while the containers show as running and healthy, when I try to open immich I just get the "This site can’t be reached" error.
I tried following the instructions from the backup and restore page, using the automatic backup from yesterday, to no avail. Running docker ps shows server, machine learning, postgres, and redis as running, but I am unable to access the aplication. I apologize if I missed something obvious.

somber tideBOT
#

:wave: Hey @stone tiger,

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 immich.

References

#

Checklist

I have...

  1. :ballot_box_with_check: verified I'm on the latest release(note that mobile app releases may take some time).
  2. :ballot_box_with_check: read applicable release notes.
  3. :ballot_box_with_check: reviewed the FAQs for known issues.
  4. :ballot_box_with_check: reviewed Github for known issues.
  5. :ballot_box_with_check: tried accessing Immich via local ip (without a custom reverse proxy).
  6. :ballot_box_with_check: uploaded the relevant information (see below).
  7. :ballot_box_with_check: 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 -l and df -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.

stone tiger
#

Running on Ubuntu 24.04.3 LTS
Hardware HP ProDesk 400 G5 SFF
Processor Intel® Core™ i5-8500 × 6
RAM 16.0 GiB

somber tideBOT
quiet jetty
#

Thank you for providing required info!
If you run v1.133 then adjust Postgres image accordingly. It seems Immich v1.133 is not happy with the newer Postgres/VectorChord specified in your compose currently. From logs:

Initializing Immich v1.133.0
...
Error: The VectorChord extension version is 0.4.3, but Immich only supports >=0.3 <0.4.
    Please change VectorChord to a compatible version in the Postgres instance.
quiet jetty
#

Overall v1.131 -> v1.133 -> v1.141 is a viable upgrade path.

I also quickly tested 133->141 on a sandbox instance: all DB migrations completed successfully, Immich is up and running with either compose file (from v141 or from v133)

# using script from https://github.com/skatsubo/immich-upgrade-lab
./test-upgrade.sh v1.133.0 v1.141.1

Testing upgrade: v1.133.0 -> v1.141.1

deploy_stack [v1.133.0] These docker images will be used:
    image: ghcr.io/immich-app/postgres:14-vectorchord0.3.0-pgvectors0.2.0
    image: ghcr.io/immich-app/immich-server:v1.133.0

main [v1.133.0] 🟡
main [v1.133.0] 🟡 [Test 1] Upgrade to v1.141.1 using the existing/current docker-compose.yml (matching v1.133.0)
main [v1.133.0] 🟡

wait_for_immich_running [v1.133.0] Wait for Immich to become ready

main [v1.141.1] Begin upgrade. Set target IMMICH_VERSION=v1.141.1, but keep the existing compose of the current version v1.133.0
deploy_stack [v1.141.1] These docker images will be used:
    image: ghcr.io/immich-app/postgres:14-vectorchord0.3.0-pgvectors0.2.0
    image: ghcr.io/immich-app/immich-server:v1.141.1

Upgrade to v1.141.1 done. Verify it: upload photos, check logs for errors.

...

main [v1.133.0] 🟡
main [v1.133.0] 🟡 [Test 2] Upgrade to v1.141.1 using docker-compose.yml for the target version (released in v1.141.1)
main [v1.133.0] 🟡

wait_for_immich_running [v1.133.0] Wait for Immich to become ready

main [v1.141.1] Begin upgrade. Use compose of the target version (released in v1.141.1)
deploy_stack [v1.141.1] These docker images will be used:
    image: ghcr.io/immich-app/postgres:14-vectorchord0.3.0-pgvectors0.2.0
    image: ghcr.io/immich-app/immich-server:v1.141.1

Upgrade to v1.141.1 done. Verify it: upload photos, check logs for errors.
stone tiger
#

Ok, so bear with my ignorance for a second, if I understood correctly, I need to change

    container_name: immich_postgres
    image: ghcr.io/immich-app/postgres:14-vectorchord0.4.3-pgvectors0.2.0@sha256:32324a2f41df5de9efe1af166b7008c3f55646f8d0e00d9550c16c9822366b4a```
Is it okay to just change the "vectorchord0.4.3" to 0.3.0 like so in the .yml?
```  database:
    container_name: immich_postgres
    image: ghcr.io/immich-app/postgres:14-vectorchord0.3.0-pgvectors0.2.0@sha256:32324a2f41df5de9efe1af166b7008c3f55646f8d0e00d9550c16c9822366b4a```
And after that one works, change the immich ver in the .env to 1.141 and the vectorchord back to 0.4.3 in the .yml?
stone tiger
#

So I made that change I mentioned as I mentioned it, the docker compose file says database: container_name: immich_postgres image: ghcr.io/immich-app/postgres:14-vectorchord0.3.0-pgvectors0.2.0@sha256:32324a2f41df5de9efe1af166b7008c3f55646f8d0e00d9550c16c9822366b4a
The .env is pinned to 1.133.0

IMMICH_VERSION=v1.133.0```
``` But I still get those same errors in the logs
quiet jetty
#

Postgres image in docker compose for v1.133.0 from "Assets" in https://github.com/immich-app/immich/releases/tag/v1.133.0:
image: ghcr.io/immich-app/postgres:14-vectorchord0.3.0-pgvectors0.2.0
It should have worked...

UPD. I mean, pinning it with sha checksum forced another version, 0.4.3, which explains why you got the same error.

quiet jetty
# stone tiger I tried to reinstall and restore from backup following the instructions on the b...

Are you using compose for v1.133 when set IMMICH_VERSION=v1.133.0 ?
This error

  LOG [Api:StorageService] Verifying system mount folder checks <...>
ERROR [Api:StorageService] Failed to read upload/encoded-video/.immich: Error: ENOENT: no such file or directory, open 'upload/encoded-video/.immich'
api worker exited with code 1

looks for me as if Immich container's internal "upload" directory is incorrectly mounted. There was change between v1.133 and v1.137 in docker compose file. That's why I'm asking.

stone tiger
stone tiger
quiet jetty
#

If you are restoring back to Immich v1.133 and you are using database dump from version v1.133 or earlier (maybe 1.131? Depending on when you started the upgrade journey) then it's definitely better to use compose from v1.133 too.

#

Go ahead with setting it back to - ${UPLOAD_LOCATION}:/usr/src/app/upload if I'm not mistaken.

stone tiger
#

Yeah, just confirmed from the github release, it was "/usr/src/app/upload", I'll try that now, thanks for all your help thus far.

#

Ok, so I got 1.133 up and running successfully, for 1.142 (since that's out now) I change the volume line back to /data instead of /usr/src/app/upload again right?

quiet jetty
#

Yep.
You can do it simultaneously: version change and /data line change. Or in 2 steps: version; apply; then the line. Both should work.

stone tiger
#

Actually, nevermind, I'm going to freeze on 1.133 for now. I went ahead and tried it and it went back to not responding, so I'm rolling back.

#

But I really appreciate all your help.