Hi all

I have tried for hours to fix this myself and have given up. I tried searching Google and the forums here (Wish there was a way to search a specific support thread for a specific container).

Anyway, I have completely wiped my install of Immich, along with Postgres to no avail. I simply do not know what else to do. My Vaultwarden is also trashed. That REALLY has me concerned.

Here are screenshots of my (attempts) to get Immich up and RE-running...

Any help is appreciated!

Thanks!

10 hours ago, TechMed said:

Wish there was a way to search a specific support thread for a specific container

There should be a support link for that container, though possibly it's external.

Here are also a couple of threads that may help:
https://forums.unraid.net/topic/198609-immich/
https://forums.unraid.net/topic/146106-immich-docker-self-hosted-google-photos-setup/

Hi @JorgeB

Thanks for the reply!

I read through (eyes now glassy) the two links, and I think I may have found something...

This (unreadable by me) seems to be the source of the issue as the word "ERROR" pops up a lot!

>>>>>

Node.js v24.21.0

api worker exited with code 1

(node:61322) 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

[Nest] 61227 - 10/13/2026, 2:38:09 PM LOG [Api:WebsocketRepository] Initialized websocket server

Starting api worker

[Nest] 61259 - 10/13/2026, 2:38:15 PM LOG [Api:WebsocketRepository] Initialized websocket server

Starting api worker

[Nest] 61290 - 10/13/2026, 2:38:21 PM LOG [Api:WebsocketRepository] Initialized websocket server

Starting api worker

[Nest] 61322 - 10/13/2026, 2:38:27 PM LOG [Api:WebsocketRepository] Initialized websocket server

missing 'error' handler on this Redis client

missing 'error' handler on this Redis client

missing 'error' handler on this Redis client

missing 'error' handler on this Redis client

file:///app/immich/server/dist/repositories/database.repository.js:46

throw new Error(No vector extension found. Available extensions: ${VECTOR_EXTENSIONS.join(', ')});

^

Error: No vector extension found. Available extensions: vchord, vector

at getVectorExtension (file:///app/immich/server/dist/repositories/database.repository.js:46:15)

at process.processTicksAndRejections (node:internal/process/task_queues:104:5)

at async file:///app/immich/server/dist/services/database.service.js:56:31

at async file:///app/immich/server/dist/repositories/database.repository.js:378:27

at async #props.executor.provideConnection.freeze.signal (file:///app/immich/server/node_modules/.pnpm/[email protected]/node_modules/kysely/dist/kysely.js:647:20)

at async DefaultConnectionProvider.provideConnection (file:///app/immich/server/node_modules/.pnpm/[email protected]/node_modules/kysely/dist/driver/default-connection-provider.js:10:20)

at async file:///app/immich/server/dist/repositories/database.repository.js:375:13

<<<<<<<

I have no idea if anyone can read this and decipher it.

If so I would appreciate the education!!!

Thanks again!!!

The key error is:

Error: No vector extension found. Available extensions: vchord, vector

This means Immich cannot find a supported vector extension in the PostgreSQL server it connects to. These extensions provide database features that Immich needs.

An older PostgreSQL image could explain this, particularly if Immich updated recently.

Please post:

• The full Repository value, including the tag, from the Immich and PostgreSQL container settings.

• The Immich version shown near the beginning of its startup log.

• The PostgreSQL container’s startup log.

Remove passwords and tokens before posting.

When you wiped the installation, did you remove only the containers, or also their appdata/database folders? Please preserve any remaining database files, photos, and backups while we identify the correct recovery steps.

Thank you @JorgeB for responding ,

Apologies for the late reply. This annoying thing called 'work' got in the way.

So I 'mostly' understand what you are referring to in the error. I have been following all of the "Update Available" notifications. In hind sight, I probably should not have. My original install posted by Ed (SI1) did 'mostly' work fine. It had issues with uploading large files (primarily videos) from my phone, but again, it did work. I did keep all of that media on my phone as I was still testing Immich; had major issues with Nextcloud and learned my lesson about saving the original data until I trusted the new install(s). All that said, I uninstalled/deleted everything and it still didn't want to work after a fresh install. (Both Immich and Postgres)

Anyway, I hope this is what you are looking for: (PLEASE let me know if not as I really liked Immich and would like to get it working again)

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Immich Log >>>>>>>>>>>>

text error warn system array login

api worker exited with code 1

Connection to 192.168.69.240 7979 port [tcp/*] succeeded!

Error: No vector extension found. Available extensions: vchord, vector

at getVectorExtension (file:///app/immich/server/dist/repositories/database.repository.js:46:15)

at process.processTicksAndRejections (node:internal/process/task_queues:104:5)

at async file:///app/immich/server/dist/services/database.service.js:56:31

at async file:///app/immich/server/dist/repositories/database.repository.js:378:27

at async #props.executor.provideConnection.freeze.signal (file:///app/immich/server/node_modules/.pnpm/[email protected]/node_modules/kysely/dist/kysely.js:647:20)

at async DefaultConnectionProvider.provideConnection (file:///app/immich/server/node_modules/.pnpm/[email protected]/node_modules/kysely/dist/driver/default-connection-provider.js:10:20)

at async file:///app/immich/server/dist/repositories/database.repository.js:375:13

microservices worker error: Error: No vector extension found. Available extensions: vchord, vector, stack: Error: No vector extension found. Available extensions: vchord, vector

at getVectorExtension (file:///app/immich/server/dist/repositories/database.repository.js:46:15)

at process.processTicksAndRejections (node:internal/process/task_queues:104:5)

at async file:///app/immich/server/dist/services/database.service.js:56:31

at async file:///app/immich/server/dist/repositories/database.repository.js:378:27

at async #props.executor.provideConnection.freeze.signal (file:///app/immich/server/node_modules/.pnpm/[email protected]/node_modules/kysely/dist/kysely.js:647:20)

at async DefaultConnectionProvider.provideConnection (file:///app/immich/server/node_modules/.pnpm/[email protected]/node_modules/kysely/dist/driver/default-connection-provider.js:10:20)

at async file:///app/immich/server/dist/repositories/database.repository.js:375:13

microservices worker exited with code 1

(node:750) ExperimentalWarning: WASI is an experimental feature and might change at any time

(Use node --trace-warnings ... to show where the warning was created)

node:internal/process/promises:394

triggerUncaughtException(err, true /* fromPromise */);

^

Error: connect ECONNREFUSED 192.168.69.240:5433

at TCPConnectWrap.afterConnect [as oncomplete] (node:net:2021:16) {

errno: -111,

code: 'ECONNREFUSED',

syscall: 'connect',

address: '192.168.69.240',

port: 5433

}

Node.js v24.21.0

node:internal/process/promises:394

triggerUncaughtException(err, true /* fromPromise */);

^

Error: connect ECONNREFUSED 192.168.69.240:5433

at TCPConnectWrap.afterConnect [as oncomplete] (node:net:2021:16) {

errno: -111,

code: 'ECONNREFUSED',

syscall: 'connect',

address: '192.168.69.240',

port: 5433

}

Node.js v24.21.0

api worker exited with code 1

Connection to 192.168.69.240 7979 port [tcp/*] succeeded!

node:internal/process/promises:394

triggerUncaughtException(err, true /* fromPromise */);

^

Error: connect ECONNREFUSED 192.168.69.240:5433

at TCPConnectWrap.afterConnect [as oncomplete] (node:net:2021:16) {

errno: -111,

code: 'ECONNREFUSED',

syscall: 'connect',

address: '192.168.69.240',

port: 5433

}

Node.js v24.21.0

node:internal/process/promises:394

triggerUncaughtException(err, true /* fromPromise */);

^

Error: connect ECONNREFUSED 192.168.69.240:5433

at TCPConnectWrap.afterConnect [as oncomplete] (node:net:2021:16) {

errno: -111,

code: 'ECONNREFUSED',

syscall: 'connect',

address: '192.168.69.240',

port: 5433

}

Node.js v24.21.0

Connection to 192.168.69.240 7979 port [tcp/*] succeeded!

[Nest] 699 - 10/13/2026, 9:45:14 PM LOG [Microservices:WebsocketRepository] Initialized websocket server

Starting api worker

[Nest] 750 - 10/13/2026, 9:45:19 PM LOG [Api:WebsocketRepository] Initialized websocket server

[10/13/26 21:45:21] INFO Handling signal: term

[10/13/26 21:45:21] INFO Shutting down

[10/13/26 21:45:21] INFO Waiting for application shutdown.

[10/13/26 21:45:21] INFO Application shutdown complete.

[10/13/26 21:45:21] INFO Finished server process [338]

[10/13/26 21:45:21] INFO Worker (pid:338) was sent SIGTERM!

[10/13/26 21:45:21] INFO Shutting down: Master

Press ANY KEY to close this window

<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>Postgres Log >>>>>>>>>>>>>>

postgresql-2026-10-13_214423.log

<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>Postgres Install log BELOW>>>>>>>>>>>>>>>>>>>>>

<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

Thanks again!!!

J

Edited Thursday at 06:28 PM4 days by TechMed
Update information

The PostgreSQL log shows two things:

- The database is brand new and empty. Immich can't find even its first table (system_metadata), so nothing from the old install is in it.

- The PostgreSQL image you are using (PostgreSQL 16.8) doesn't include the vector extensions that Immich needs (vchord/vector). Recent Immich releases need a PostgreSQL image with VectorChord. A plain postgres image or the older pgvecto-rs image won't work anymore.

Because the database is empty, the easiest fix is to start it fresh with the correct image:

1. Stop the Immich and PostgreSQL containers.

2. Delete the PostgreSQL container's appdata folder (the database folder only, not your photos/upload folder). It contains no Immich data now.

3. Edit the PostgreSQL container and change Repository to:

ghcr.io/immich-app/postgres:16-vectorchord0.4.3-pgvectors0.2.0

Keep the same user, password, and database name settings that Immich uses.

4. Start PostgreSQL first. Wait until its log shows "database system is ready to accept connections", then start Immich.

If it still fails, post the full Repository value of both containers and the new logs from both.

Your earlier attempt to upload to Immich may have left files in the Immich upload folder. Your originals are still on your phone, so the cleanest start is an empty upload folder.

Hi Jorge,
First, I cannot thank you enough for your assistance!!! Seriously!

So I tried twice to utilize your instructions. However, the database (PostgresSQL) keeps stopping (Log attached).

The curious point is, log does show "database system is ready to accept connections", then makes a U-Turn and receives a "fast shutdown request".

It appears to be coming from command "/usr/local/bin/docker-entrypoint.sh: ignoring /docker-entrypoint-initdb.d/*" Why is it ignoring it? was it not created?

Here are the items you requested...

(A million 'thanks' again!)

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>Immich Repo>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

(LOG BELOW)

<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>PostgresSQL Repo >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

(LOG BELOW)

<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

Immich_log.pdf PostgresSQL_log.pdf

Tthe new PostgreSQL image works. The "No vector extension found" error is gone. Immich now finds its vector indexes (clip_index and face_index) and starts its database migrations.

PostgreSQL is not crashing, what you see is normal:

- On the first start with an empty folder, the container creates the database with a temporary server, runs any custom scripts, then stops that temporary server with a "fast shutdown" and starts the real one. "ignoring /docker-entrypoint-initdb.d/*" only means there are no custom scripts, and none are needed.

- The later "received fast shutdown request" lines (09:32 and 10:15) mean the container was told to stop, for example by the Stop button, a restart, or a backup plugin. PostgreSQL does not stop by itself like that. At 10:15:09 both containers stopped within a few seconds of each other while Immich was running its migrations, so Immich failed with CONNECTION_CLOSED. The ECONNREFUSED errors are Immich trying to connect while PostgreSQL was stopped.

The first Immich start on a new database can take several minutes, because it creates all the tables and imports the geodata. If it is interrupted, it must start again.

You can try this:

1. Start PostgreSQL and wait for "database system is ready to accept connections".

2. Start Immich.

3. Leave both alone for at least 10 to 15 minutes. Do not stop, restart or update either container during this time.

4. Then check the Immich log, it should show that the server is listening.

If PostgreSQL stops again without you stopping it, check if a plugin is scheduled at that time, for example Appdata Backup, which stops containers while it runs.

The database is still empty, so if the migrations keep failing you can safely repeat the reset steps.

One more thing: an older start in the Immich log failed with EADDRNOTAVAIL when Immich tried to listen on your server's IP address at port 7979. A container cannot listen on the server's IP directly. If that error comes back, post a screenshot of the Immich container settings (click "Show more settings" and hide any passwords).

Got it.

I have to go out for a while today, so I am going to start them now and check them when I get home.

Until then...

👍

Edited Friday at 03:18 PM3 days by TechMed
spelling

Hi Jorge,

No good. It/they ran for 8-10 hours before I touched them.

I am attaching a video of the log to show "IMMICH" just looping and based on what I can tell, never attaching to the db.

Nothing has been changed since here...

I am going to be gone for the day, but would like to work through this.

During my initial research it appears others are having semi-similar issues and perhaps this will help them get it running.

Like I mentioned, I liked Immich (save the video upload issue) very much. I have no problem tossing a couple of bucks someone's way too, if it gets stable...for me.

All that said...thanks again for hanging in there with me.

PostgresSQL_1017_log.pdf Immich_1017_log.pdf

Thanks. Both PDFs you attached contain the PostgreSQL log, and it looks healthy now. It has been running without errors or stops. The Immich log is not included.

Please post the Immich container log as text. Click the Immich icon, select Logs, and copy everything from the start until it begins to repeat. Then paste it here or attach it as a .txt file.

@JorgeB Good evening...

Thanks again....

Please see attach.

This run of code just keeps looping...

Immich_log_for_JorgeB.txt

The database part is now fully fixed: Immich finishes its migrations, finds no schema problems, and all its folders check out.

The loop has a different cause:

listen EADDRNOTAVAIL: address not available 192.168.69.240:7979

Immich is set to listen on your server's IP address. A container cannot do that, so the server process exits and restarts every few seconds.

Please edit the Immich container, click "Show more settings", and find the variable that sets the listening address. It is usually named IMMICH_HOST, and it probably has 192.168.69.240 as its value. Change it to 0.0.0.0 or delete it. Then apply and check the log again.

Do not change the database and Redis hostname variables. Those should keep the server IP.

Also, if a variable such as IMMICH_PORT is set to 7979, the container port in the port mapping must be the same number. If you are not sure, post a screenshot of the Immich container settings with passwords hidden.

@JorgeB

Finally! 🎆

Many many many thanks!!!!

I haven't uploaded anything yet as I still have a few questions.

What are your thoughts on container "updates"?

For example, Immich has an update right now. Do I avoid it/them or wait until there is an update for the db AND Immich, or...

If you have any additional info to impart, generally speaking, I'd appreciate it. (I now need to work on VaultWarden; they both took a dump simultaneously...UGH)

I am attaching pdf's of my ProgressSQL and Immich container setup files so if anyone else runs across similar issues.

Really appreciate you hanging in there with me to get this working!!!

🍻🍻 on it's way!

Glad it's working now, I don't use Immich myself, so these are more general suggestions:

- Before you update, read the release notes. Some releases have breaking changes or need changes to the database or the container settings.

- The PostgreSQL tag is pinned, so only change it if the Immich notes tell you to.

- Back up the upload folder and the database before you upload a lot of photos.

Got it!