Immich on UnRaid error after update: "Error: No vector extension found. Available extensions: vchord, vector"

[pglamb92361]

Good morning.

This is my first post here.

I'm running Immich on my UnRaid server. I updated the container this morning and now have an error:

[mod-init] Running Docker Modification Logic
[mod-init] Adding imagegenius/mods:universal-redis to container
[mod-init] imagegenius/mods:universal-redis at sha256:d79cc7c55bbb144e66370494abc938bc3ec42361fa3ac829f8eca48a9d7b1d43 has been previously applied skipping
[migrations] started
[migrations] no migrations found
usermod: no changes
───────────────────────────────────────

---

| | | | | | | |
| --| | | | | | | | | | | |
|||| |_| |||||
_____ __ __ _ __ ____
| __ | | | | | | \
| __ -| | | | || | |
||__||_____|____/
Based on images from linuxserver.io
───────────────────────────────────────
To support LSIO projects visit:
https://www.linuxserver.io/donate/
───────────────────────────────────────
GID/UID
───────────────────────────────────────
User UID: 99
User GID: 100
───────────────────────────────────────
/usr/bin/redis-server
**** redis-server already installed, skipping ****
[custom-init] No custom files found, skipping...
(node:239) ExperimentalWarning: WASI is an experimental feature and might change at any time
(Use node --trace-warnings ... to show where the warning was created)
Starting api worker
(node:283) ExperimentalWarning: WASI is an experimental feature and might change at any time
(Use node --trace-warnings ... to show where the warning was created)
[Nest] 283 - 07/07/2026, 9:35:29 AM LOG [Api:WebsocketRepository] Initialized websocket server
/app/immich/server/dist/repositories/database.repository.js:51
throw new Error(No vector extension found. Available extensions: ${constants_1.VECTOR_EXTENSIONS.join(', ')});
^
Error: No vector extension found. Available extensions: vchord, vector
at getVectorExtension (/app/immich/server/dist/repositories/database.repository.js:51:15)
at process.processTicksAndRejections (node:internal/process/task_queues:104:5)
at async /app/immich/server/dist/services/database.service.js:62:31
at async /app/immich/server/dist/repositories/database.repository.js:376:27
at async /app/immich/server/node_modules/.pnpm/kysely@0.28.17/node_modules/kysely/dist/cjs/kysely.js:541:20
at async DefaultConnectionProvider.provideConnection (/app/immich/server/node_modules/.pnpm/kysely@0.28.17/node_modules/kysely/dist/cjs/driver/default-connection-provider.js:12:20)
at async /app/immich/server/dist/repositories/database.repository.js:373:13
Node.js v24.15.0
api worker exited with code 1

I'm not sure how to troubleshoot this. I've relied upon the UnRaid community for Docker images.

Thank you for reading and any suggestions you may have.

Pat

[slashgob]

I have the same issue after upgrading Immich on Unraid. I'm using this PostgreSQL container: tensorchord/pgvecto-rs:pg16-v0.2.1

It obviously has something to do with pgvector but I'm not sure what to do to correct it. Some info here which I will try to follow https://docs.immich.app/install/upgrading/#migrating-to-vectorchord

[exico91]

Same problem, for now going back to version 2 "fixes" it.
If you need it working asap just replace "latest" with "2" in your docker settings and wait for a official fix.

[slashgob]

OK I fixed mine. Here is what I did:

1. Do a database backup first - I didn't do this but you really should! Search to find how to do this.
2. Stop the Immich Docker in Unraid
3. Stop the PostgreSQL Docker in Unraid
4. I changed the PostgreSQL Repository from tensorchord/pgvecto-rs:pg16-v0.2.1 to ghcr.io/immich-app/postgres:16-vectorchord0.4.3-pgvectors0.2.0
5. Let it download the new image and start it
6. I checked the logs, it started clean.
7. Then I started the Immich container and watched the logs, it did the migration and all seems to be working again.

This worked for me but please do a DB backup - don't blame me if you don't!

[pglamb92361]

OK I fixed mine. Here is what I did:

1. Do a database backup first - I didn't do this but you really should! Search to find how to do this.

2. Stop the Immich Docker in Unraid

3. Stop the PostgreSQL Docker in Unraid

4. I changed the PostgreSQL Repository from tensorchord/pgvecto-rs:pg16-v0.2.1 to ghcr.io/immich-app/postgres:16-vectorchord0.4.3-pgvectors0.2.0

5. Let it download the new image and start it

6. I checked the logs, it started clean.

7. Then I started the Immich container and watched the logs, it did the migration and all seems to be working again.

This worked for me but please do a DB backup - don't blame me if you don't!

Yes! This worked for me too. Thank you very much!!!

Now, to figure out how to make configuration changes in the Unraid Immich app to move to version 3.

[vcfxt]

OK I fixed mine. Here is what I did:

1. Do a database backup first - I didn't do this but you really should! Search to find how to do this.

2. Stop the Immich Docker in Unraid

3. Stop the PostgreSQL Docker in Unraid

4. I changed the PostgreSQL Repository from tensorchord/pgvecto-rs:pg16-v0.2.1 to ghcr.io/immich-app/postgres:16-vectorchord0.4.3-pgvectors0.2.0

5. Let it download the new image and start it

6. I checked the logs, it started clean.

7. Then I started the Immich container and watched the logs, it did the migration and all seems to be working again.

This worked for me but please do a DB backup - don't blame me if you don't!

Yes! This worked for me too. Thank you very much!!!

Now, to figure out how to make configuration changes in the Unraid Immich app to move to version 3.

This fix worked for me as well from v 0.3.0 FYI.

Note - my Unraid Immich version is reflecting 3.0.1, so I do not believe any further action is required? The issue is just that you needed postgres to have vectorchord capability (pardon my rudimentary understanding / explanation) https://docs.immich.app/install/upgrading#migrating-to-vectorchord

[feenx]

OK I fixed mine. Here is what I did:

1. Do a database backup first - I didn't do this but you really should! Search to find how to do this.
2. Stop the Immich Docker in Unraid
3. Stop the PostgreSQL Docker in Unraid
4. I changed the PostgreSQL Repository from tensorchord/pgvecto-rs:pg16-v0.2.1 to ghcr.io/immich-app/postgres:16-vectorchord0.4.3-pgvectors0.2.0
5. Let it download the new image and start it
6. I checked the logs, it started clean.
7. Then I started the Immich container and watched the logs, it did the migration and all seems to be working again.

This worked for me but please do a DB backup - don't blame me if you don't!

+1

[Timelightnl]

OK I fixed mine. Here is what I did:

1. Do a database backup first - I didn't do this but you really should! Search to find how to do this.
2. Stop the Immich Docker in Unraid
3. Stop the PostgreSQL Docker in Unraid
4. I changed the PostgreSQL Repository from tensorchord/pgvecto-rs:pg16-v0.2.1 to ghcr.io/immich-app/postgres:16-vectorchord0.4.3-pgvectors0.2.0
5. Let it download the new image and start it
6. I checked the logs, it started clean.
7. Then I started the Immich container and watched the logs, it did the migration and all seems to be working again.

This worked for me but please do a DB backup - don't blame me if you don't!

This did the trick for me. Thank you! Do I also need to revert it back or can I just keep it like this in the future?

[grove-guard]

OK I fixed mine. Here is what I did:

1. Do a database backup first - I didn't do this but you really should! Search to find how to do this.

2. Stop the Immich Docker in Unraid

3. Stop the PostgreSQL Docker in Unraid

4. I changed the PostgreSQL Repository from tensorchord/pgvecto-rs:pg16-v0.2.1 to ghcr.io/immich-app/postgres:16-vectorchord0.4.3-pgvectors0.2.0

5. Let it download the new image and start it

6. I checked the logs, it started clean.

7. Then I started the Immich container and watched the logs, it did the migration and all seems to be working again.

This worked for me but please do a DB backup - don't blame me if you don't!

This worked for me as well to access my WebUI. However I still can't backup from my android app to the server. I can see the photos, but backup doesn't complete. The logs two errors.
Yellow: Linked remote album not found for ID: 77be0a7b-42e5-4ec5-a532-d09d7c3418f2
Red: Error in runInIsolateGentle for remote-sync
Details: ApiException 400: Failed to get sync stream: {"message":"SyncRequestType.AssetsV1 is deprecated, use SyncRequestType.AssetsV2 instead"}

I'm having trouble figuring out if this is even related to the fix to "PostgreSQL_Immich" docker, or something else entirely.

Edit: Nevermind; was using the android app version from f-droid which was outdated. Manually downloaded the latest apk from github and now it's working fine.

[Brad787]

Thank you. This got Immich v3.01 up and running on my Unraid machine.

I noticed this docker is based on postgres v16 while other dockers are based on v18. Is this something that will eventually give us problems?

[dyeinsanity]

I had this same issue fixed worked for me as well. Hoping in future updates we are not going to have to do this all the time.

[joshkaspar]

Just wanted to add a heads up for anyone else landing here — make sure you check what version you're actually coming from first. That's the second number in your Postgres container's Repository field (the v0.X.X part), and you need to match it when you pick your new image, not just copy-paste the example from the docs.

So for example, mine was tensorchord/pgvecto-rs:pg16-v0.3.0, so I went with ghcr.io/immich-app/postgres:16-vectorchord0.4.3-pgvectors0.3.0 — matching both the pg16 and the 0.3.0 pgvecto.rs version.

Also don't forget to add --shm-size=128mb in the Extra Parameters field on the Postgres container. This one tripped me up because I first tried adding it as an environment variable (shm_size), and that does nothing - it has to be a Docker container flag, not an env var.

And before you touch any of this back up your database first, with everything still running:

docker exec -t <your_postgres_container_name> pg_dumpall --clean --if-exists --username=postgres > immich_db_backup.sql

(swap the container name and username for whatever yours actually are)

Then stop both containers, swap the Postgres image, start Postgres and check the logs come up clean, then start Immich and watch it do its reindex/migration thing. Then test your Immich server by searching for an object. If it works, you are good to go.

[FS1961]

Thank you. I was completely lost and this helped me.

[ssgittyup]

OK I fixed mine. Here is what I did:

1. Do a database backup first - I didn't do this but you really should! Search to find how to do this.
2. Stop the Immich Docker in Unraid
3. Stop the PostgreSQL Docker in Unraid
4. I changed the PostgreSQL Repository from tensorchord/pgvecto-rs:pg16-v0.2.1 to ghcr.io/immich-app/postgres:16-vectorchord0.4.3-pgvectors0.2.0
5. Let it download the new image and start it
6. I checked the logs, it started clean.
7. Then I started the Immich container and watched the logs, it did the migration and all seems to be working again.

This worked for me but please do a DB backup - don't blame me if you don't!

Thanks, this fixed the issue for me as well.