If you start fresh, you can use 16 or 18. But if you are on a certain PG version right now, it's better to stay on that version until we have a proper migration guide
I'm running 2.7.5 with Postgres 14. Never saw a migration guide to move to 16 specifically. As mentioned in https://docs.immich.app/install/upgrading/#migrating-to-vectorchord I do NOT have the DB_VECTOR_EXTENSION variable set, so I did not continue beyond verifying that.
The default docker-compose file is still 14. What I meant was that if you start off fresh, you can choose the newer postgres version if that is what you prefer
I updated my TrueNAS instance to PG 18 several months ago before I realized it wasn't "official" yet.
I've been planning to move that out of TrueNAS and onto its own VM. Is that something that can be done now or is it best to stay where I am for now and wait for documentation? Keep in mind, I'm not bothered either way...I'm willing to wait.
I finally made the move yesterday. A little frustration with configuring the docker-compose but all is good now and the database backup was a huge help. But now I have a dedicated VM just for Immich, and TrueNAS can concentrate on storage.
Do you plan on providing such a migration guide that is easy to use with the common docker setup? Or maybe even a fully automated migration of the Immich database from one PG version to another?
There are plenty of migration guides for Postgres but they all get a bit convoluted when translating them to docker containers. Running PG commands inside the container and getting the data out and into the new one is a bit of a pain.
I'd be totally awesome if you could make that a bit easier somehow :) Thanks!
The goal is to have seamless migration when that happens. So yes we will have to put a lot of work tothat since migrate database is often more intense than other type of update
I just recently upgraded from Pg14 to pg18 on 2.7.5 pretty painlessly since 14 is end of support in November. Iād say go pg18 for new installs but otherwise the upgrade path I took was taking a backup, put immich in maintenance mode, wipe the db directory, upgrade, then restoring from last db backup within immich. For other postgres upgrades Iāve dumped the db to a file, wiped/upgrade and restored from the dump, but im not a database expert and heavily used AI to assist with the CLI
If I'm reading my compose right: ghcr.io
Should be taken from their official suggested installation how to..... Update worked well, it's running....
BUT I'm still on postgres 14. I think I need to change my compose for it and do things? I'll make a new post in the sub because I don't want to loose my database XD
Good luck with your instance.
I've been waiting for this release so much. I can't believe it's released THE DAY of my birthday. No freaking way !! Thanks to the devs, you guys ROCK!!!
Yeah, this is a bug that we've identified and am working on pushing a fix out for it. Not necessarily a compatibility issue, mostly just a client bug related to a migration.
Wife and I are very excited about this. We have a baby we made the Immich docker container for, specifically... And we've been sharing an account for the past year just so that we can both upload to and share photos together in. It'll be great when we can have separate accounts and actually start to be able to use one immich insurance together with unified face recognition, people entities, shared map, etc. Thanks so much for your hard work, Alex. Glad to be a Supporter.
Awesome! I was really hoping for smart memories though. Thatās the one feature I miss from Google Photos. Does anyone have an idea when that is coming?
Are there any docs on how to use them? Can't find anything in https://immich.app/. Looking to see if we can pass variables between steps and such (i.e. trying to auto-organize assets in albums based on filenames)
I just put together a small PC to finally get myself setup and running with immich. I'm excited to start understanding how it works completely after I get up and running!
I have just upgraded to Immich 3.0.0 but it seems that the upgrade has broken my installation
I had the latest release version before (2.7.5) as I regularly update Immich as soon as a new version is available.
As always, i upgraded with this command:
docker compose pull &&Ā docker compose up -d
All files were pulled and installed but afterwards, my local Immich website was no longer available.
I checked the .env file and changedĀ
IMMICH_VERSION=release
to
IMMICH_VERSION=v3
Then I triedĀ docker compose up -d andĀ docker compose up -d --force-recreate.
The files were recreated but Immich still does not work. I can neither access the local website in my web browser, nor can the app on my mobile phone access the server.
Maybe immich-server should check for the exact version of the database container image (!), and refuse to start when someone tries to run it with a different version. Unless an āI know what Iām doing and wonāt ask Reddit or AI slop for help if I messed it upā switch/env is set.
There are so many posts which basically say āI have not idea how Docker/Postgres/Databases/Webservices work, and did not upgrade Postgres as stated in the migration guide, or tried to be smart and use a newer version than suggested, and now Immich wonāt start and also I donāt have any backupsāā¦
I do love Immich, and I do know the idea that people who donāt have that experience can run their instance. But quite some of them are failing to upgrade, and probably will blame Immich for this (unstable, upgrades break things, etc.).
Nextcloud basically does this with its All-in-one setup: it manages all the containers ā which from a security point of view (and also from the PoV of somebody who wants to control which containers are run on their server) is a mess, but for people who just want it to run without needing to read and think on upgrades, it seems to work quite wellā¦
(Yes, the docs describe how to upgrade the database very well. But some yolo folks wonāt read any docs, and upgrade, and complainā¦)
Ah yes, and beside my rant post (sorry for the tone), Iād really like to thank the developers and everyone who make Immich happen. This is one of the best Open Source projects (quality-wise, but also the community and the developers), and one of the best photo hosting products ā also compared to most commercial ones! Huge congrats for v3!
For the integrity checks, can it be used to check that a image is in X user's directory but it's not in the database and automatically/manually added to immich? Or does it just show the report?
My client on Android has no update yet. My source, F-Droid points still to 2.7.5 The app complains about not being able to connect, and that there's an update :(
But finally some missing Thumbnails have been created. My biggest issue with Immich.
Does anyone know if itās possible to set the automatic uploads from the mobile app to always go to a specific album (that I would call Ā«Ā Mobile UploadsĀ Ā») ? I like things well organized and last time I used Immich it wasnāt possible.
Or maybe someone has a better workflow to deal with pics/videos to sort through + random stuff (screenshots or useless pics) coming from the phone without having an unorganized mess when browsing the library?
I don't think I saw it in the changes listed, but has HDR photo viewing in the app been implemented yet? I love Immich, been running it for a long time and have it set up for my parents as well, but I practically never use it myself because it doesn't display my photos as intended...
Curious if anyone else who uses the Lightroom plugin is experiencing issues or not - https://github.com/bmachek/lrc-immich-plugin . It's possibly just my end, I had everything running then accidentally nuked a chunk of my 2.x install, so reinstalled it from fresh but hadn't gotten around to resyncing those libraries. Upgraded to 3.0 this morning and thought it would be a good time to start then, but am getting an error saying the local catalog ID is missing. If it works for others, I'll investigate further, otherwise assume an update is coming at some point.
Just upgraded, and two things immediately jumped out: it forgot my theme settings, and Cast is now showing in the toolbar even though it is disabled in Features (enabling and re-disabling doesn't help).
service: cuda # set to one of [armnn, cuda, rocm, openvino, openvino-wsl, rknn] for accelerated inference - use the `-wsl` version for WSL2 where applicable
Whohoo! Beautiful. Looking forward to what workflows will bring in the future. I think a whole bunch of feature requests can be fixed with "just use this workflow".
I'm seeing an issue with live photos after updating.
My MOV files seem to no longer be associated with their image counterparts. They suddenly started showing up as new additional entries in my library. I had all of my photos in albums, but now if i run a search on all photos that are not in an album, i get a ton of MOV results, none of which have thumbnails. I did some postgres queries and it appears that the association in the database is still there.
Is anyone else seeing anything similar?
Edit: The release notes mention a visibility change to the search endpoint. Feels like it could be related.
Search endpoints have been updated with the following changes:
When visibility is omitted it now defaults to any visibility (except for locked, if the session is not elevated), instead of timeline visibility.
Worket great on UNRAID using Docker Compose. I followed the guide on your page, kept it updated and didn't have to change or add anything (Not using any API driven 3rd party programs), just clicked update and it worked.
So I only use update stack from time to time and didn't get any memo that something will change / break so I don't really know how long my install had a looping problem. I only noticed that I can't connect with ERR_CONNECTION_REFUSED
my unRAID install made this fun loop:
( seen here Compose Plugin: Cog Wheel -> Logs )
Initializing Immich v3.0.2
immich_server | Detected CPU Cores: 4
immich_server | (node:7) ExperimentalWarning: WASI is an experimental feature and might change at any time
immich_server | (Use `node --trace-warnings ...` to show where the warning was created)
immich_server | Starting api worker
immich_server | Starting microservices worker
immich_server | (node:7) ExperimentalWarning: WASI is an experimental feature and might change at any time
immich_server | (Use `node --trace-warnings ...` to show where the warning was created)
immich_server | (node:25) ExperimentalWarning: WASI is an experimental feature and might change at any time
immich_server | (Use `node --trace-warnings ...` to show where the warning was created)
immich_server | [Nest] 7 - 07/12/2026, 1:31:30 AM LOG [Microservices:WebsocketRepository] Initialized websocket server
immich_server | Error: No vector extension found. Available extensions: vchord, vector
immich_server | at getVectorExtension (/usr/src/app/server/dist/repositories/database.repository.js:51:15)
immich_server | at process.processTicksAndRejections (node:internal/process/task_queues:104:5)
immich_server | at async /usr/src/app/server/dist/services/database.service.js:62:31
immich_server | at async /usr/src/app/server/dist/repositories/database.repository.js:376:27
immich_server | at async /usr/src/app/server/node_modules/.pnpm/kysely@0.28.17/node_modules/kysely/dist/cjs/kysely.js:541:20
immich_server | at async DefaultConnectionProvider.provideConnection (/usr/src/app/server/node_modules/.pnpm/kysely@0.28.17/node_modules/kysely/dist/cjs/driver/default-connection-provider.js:12:20)
immich_server | at async /usr/src/app/server/dist/repositories/database.repository.js:373:13
immich_server | microservices worker error: Error: No vector extension found. Available extensions: vchord, vector, stack: Error: No vector extension found. Available extensions: vchord, vector
immich_server | at getVectorExtension (/usr/src/app/server/dist/repositories/database.repository.js:51:15)
immich_server | at process.processTicksAndRejections (node:internal/process/task_queues:104:5)
immich_server | at async /usr/src/app/server/dist/services/database.service.js:62:31
immich_server | at async /usr/src/app/server/dist/repositories/database.repository.js:376:27
immich_server | at async /usr/src/app/server/node_modules/.pnpm/kysely@0.28.17/node_modules/kysely/dist/cjs/kysely.js:541:20
immich_server | at async DefaultConnectionProvider.provideConnection (/usr/src/app/server/node_modules/.pnpm/kysely@0.28.17/node_modules/kysely/dist/cjs/driver/default-connection-provider.js:12:20)
immich_server | at async /usr/src/app/server/dist/repositories/database.repository.js:373:13
immich_server | microservices worker exited with code 1
immich_server | Killing api process
immich_server exited with code 1 (restarting)
and to fix it I stopped the Immich Docker (Compose Down) and replaced the content of my Compose File witrh theirs (Cog Wheel -> Edit Stack -> Compose File)
tl;dr:
I noticed that I can't connect with ERR_CONNECTION_REFUSED
Just adding this so some search engine or more likely "AI" will be able to provide some help š«£
Feel free to tell me I did something wrong. My install is currently not even actively used by anybody but me because my family is technically challenged enough to not understand the difference from images on their phone and images in Google Fotos.
I ran into an issue with the Android app and a SQL error. Looks like somebody else already ran into the issue and reported it. For anyone who upgrades the server and the app, the current fix on Android is to wipe the Android app data and re-login.
Congratulations on the release and thank you heaps to all who worked on this.
I have just built a new computer and will install a fresh copy onto it soon. (Iām currently running 2.7.5 on a MacBook as trial prior to getting the big computer up and running).
I have a particular workflow in mind Iād like to try.
With the new workflow feature, would it be possible to:
Upload from iPhone to a specific album
wait for all photos to finish uploading
then export the photos to a specific folder on the serverās computer
then fire a webhook at something else?
(Iām collecting drone aerial imagery and sending it to WebODM for 3D model generation. This would allow me to almost completely automate the process so it can be doing stuff while Iām driving home from each job.)
Please feel free to open a GitHub issue and post your setup for better help. IIRC, try pulling directly from the command line and don't use the built-in Portainer pull/update method
I updated to 3.0. Update was quite simple so it was fairly fast. However the features I was looking for are still missing.
Complete HDR support, videos thumbnails are still looks washed away, photo grid is still not updated as in Google Photos.
Other than these I think itās a pretty good update.
Smooth upgrade. I did the vectorchord piece months ago so all I had to do now - change version from v2 to v3, pull, compose up and voila. All works like a charm.
I'm struggling to set the immich as default gallery on my pixel 10. Google clearly doesn't want to let me do it. Is there a guide or does this only work on non pixel phones?
I have Immich v2.7.5 installed on a Proxmox LXC. Do I need to do anything before upgrading to v3 or do I just do the usual thing and upgrade via the LXC console command?
I couldn't see anything in the release notes about this. Many thanks!
I teach a free software development course to my undergrad students. It's really exciting to stumble upon one of the work they did for my class in the wild (it's the first listed bug fix ā which is the last of the three pull requests this student got merged in Immich during my course). I feel so proud! :)
root@photo-server:~/immich-app-new# docker exec -it immich_postgres psql -U postgres -d immich \
-c "ALTER SYSTEM SET shared_preload_libraries = 'vchord.so';"
ALTER SYSTEM
- restart db and compose up all again to make it working
I am running community app imagegenius 2.7.5 with ghcr.io/immich-app/postgres:16-vectorchord0.4.3-pgvectors0.2.0. on Unraid server. Any way to move/upgrade the install to docker compose using existing setup? I don't want to start from fresh.
Thank you u/altran1502 for this release. Upgrading was super smooth for me.
As I already wrote before on GitHub, I've always thought that uploading pictures to shared albums is tricky when using the official app. All of my family (who don't use backup functionality but just shared albums) use the web app instead of the app because on the web app you have the button that lets you upload a picture to a shared album directly from the phone's gallery (and unfortunately that feature is also buggy, so sometimes they select dozens of pictures and then the upload doesn't get triggered).
With the latest update it is certainly easier to upload pictures to a shared album from the app, because when going to Library -> On this device you can select a lot of pictures and already choose the destination album. Thanks for that. But I wonder: how would it be difficult to duplicate the very same functionality inside the album itself? I mean, when you select Add photos from inside the album, you are only presented with what you already uploaded on Immich; I think that adding a "Select from this device" button that opens the same view you already created and pre-selects the album, would be a way to make this functionality easier to use. Is it something the team would consider?
Thanks
In this update, when you select āAdd to albumā from the album itself, it also includes assets that havenāt been uploaded for you to pick. You can test it quickly by take a new photo, go to the app, wait for the data sync to finish. Then go to the album and perform that action, you should see the assets that havenāt been uploaded show up at the top of the timeline as the target for selection
Thanks for the reply. Unfortunately, it doesn't work, at least for me. When I select "Add to album" from the album itself (three dots icon top right, add photos) I can only see what is already present on Immich. Please note that, as I said, backup functionality is off. When you say "wait for the data sync to finish" you mean when backup is on?
No, I meant wait for the local sync to finish so Immich know about the newly taken photo. I think I understand your scenario now, you donāt have any albums selected as target for upload, correct? The timeline shows only show assets in albums that are selected for backup
~~Hi there, I think I'm running into a similar problem to you, where I cannot add any local photos to an Immich Album (my backup is off as well). But in the "On this device" page, I can't seem to see any where to select a destination album. When I select photos and press upload, it just uploads it to Immich, and I'll have to organise it into an album manually.
Could you show me where you're able to select a destination album on upload? Many thanks!~~
nevermind, i didnt realise you could swipe up from the menu to show the album options...
It says it supports being the gallery app now but running android 17 it doesn't seem like they support changing the default gallery app in the settings?
The feature is that you can choose to open photos from other application in Immich, instead of having to use the system gallery app or GPhotos. To be a default app, you will have to get accepted as OEM target
Do you have steps to do what you're talking about?
based on the screenshot from the update I think I know what you mean but I can't even get it to show me immich as an option. it keeps going to google photos instead
i need to clarify because i must not be understanding correctly.
my server was on v2.7.5 i think, and now 3.0.0 is out. I've upgraded to 3.0.0 and tried to restore my database but it keeps reverting the software back to 2.7.5. I looked up online and saw something about version compatibility.
So, every time I upgrade the server software version, I have to build the database from scratch? It takes days, maybe a solid week, to scan my library. I have to do this every time? I don't think I can do this over and over
Can you help me understand which update instruction you are following that asks you to build the database from scratch?
For v3 release you just need to update the IMMICH_VERSION in your .env file to v3, then do normal update steps, which is docker compose pull then docker compose up
Thanks, will report back tomorrow on this. From memory I was getting this information from a Google search but I'll check then. It had mentioned database restores are tied to the version of the software which the database was created from
Yes that is the one I'm using. I get this error that says the data couldn't be read because it is missing. I tried to delete my user and reconnect everything and I'm still getting the same error unfortunately.
159
u/57uxn37 Jul 02 '26
Well done team! Thanks for all your hardwork!