I have searched the existing issues, both open and closed, to make sure this is not a duplicate report.
The bug
I just updated to 3.0.0 and now the apps and browser say they cannot find the Immich server. I don't know how to revert the update or fix this.
The OS that Immich Server is running on
Debian 6.1.159-1
Version of Immich Server
v3.0.0
Version of Immich Mobile App
v2.7.5 build.256
Platform with the issue
Device make and model
Debian 6.1.159-1
Your docker-compose.yml content
name: immich
services:
immich-server:
container_name: immich_server
image: ghcr.io/immich-app/immich-server:${IMMICH_VERSION:-release}
volumes:
- ${UPLOAD_LOCATION}:/usr/src/app/upload
- /etc/localtime:/etc/localtime:ro
- /XXXXXXXXXXXXXXXXXXXXXX
env_file:
- .env
ports:
- 2283:2283
depends_on:
- redis
- database
restart: always
immich-machine-learning:
container_name: immich_machine_learning
container_name: immich_machine_learning
# For hardware acceleration, add one of -[armnn, cuda, openvino] to the image tag.
# Example tag: ${IMMICH_VERSION:-release}-cuda
image: ghcr.io/immich-app/immich-machine-learning:${IMMICH_VERSION:-release}
# extends: # uncomment this section for hardware acceleration - see https://immich.app/docs/features/ml-hardware-acceleration
# file: hwaccel.ml.yml
# service: cpu # set to one of [armnn, cuda, openvino, openvino-wsl] for accelerated inference - use the `-wsl` version for WSL2 where applicable
volumes:
- model-cache:/cache
env_file:
- .env
restart: always
redis:
container_name: immich_redis
image: registry.hub.docker.com/library/redis:6.2-alpine@sha256:84882e87b54734154586e5f8abd4dce69fe7311315e2fc6d67c29614c8de2672
restart: always
database:
container_name: immich_postgres
image: registry.hub.docker.com/tensorchord/pgvecto-rs:pg14-v0.2.0@sha256:90724186f0a3517cf6914295b5ab410db9ce23190a2d9d0b9dd6463e3fa298f0
environment:
POSTGRES_PASSWORD: ${DB_PASSWORD}
POSTGRES_USER: ${DB_USERNAME}
POSTGRES_DB: ${DB_DATABASE_NAME}
POSTGRES_INITDB_ARGS: '--data-checksums'
volumes:
- ${DB_DATA_LOCATION}:/var/lib/postgresql/data
restart: always
command: ["postgres", "-c" ,"shared_preload_libraries=vectors.so", "-c", 'search_path="$$user", public, vectors', "-c", "logging_collector=on", "-c", "ma>
volumes:
model-cache:
Your .env content
# You can find documentation for all the supported env variables at https://immich.app/docs/install/environment-variables
# The location where your uploaded files are stored
UPLOAD_LOCATION=/XXXXXXXXXXXXX
# The location where your database files are stored
DB_DATA_LOCATION=./postgres
# The Immich version to use. You can pin this to a specific version like "v1.71.0"
IMMICH_VERSION=release
# Connection secret for postgres. You should change it to a random password
DB_PASSWORD=XXXXXXXXXXXXX
# The values below this line do not need to be changed
###################################################################################
DB_USERNAME=postgres
DB_DATABASE_NAME=immich
Reproduction steps
- Update to 3.0.0
- immediate fail
...
Relevant log output
Initializing Immich v3.0.0
Detected CPU Cores: 12
(node:7) 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
Starting microservices worker
(node:7) ExperimentalWarning: WASI is an experimental feature and might change at any time
(Use `node --trace-warnings ...` to show where the warning was created)
(node:33) ExperimentalWarning: WASI is an experimental feature and might change at any time
(Use `node --trace-warnings ...` to show where the warning was created)
[Nest] 7 - 07/02/2026, 5:41:47 PM LOG [Microservices:WebsocketRepository] Initialized websocket server
Error: No vector extension found. Available extensions: vchord, vector
at getVectorExtension (/usr/src/app/server/dist/repositories/database.repository.js:51:15)
at process.processTicksAndRejections (node:internal/process/task_queues:104:5)
at async /usr/src/app/server/dist/services/database.service.js:62:31
at async /usr/src/app/server/dist/repositories/database.repository.js:376:27
at async /usr/src/app/server/node_modules/.pnpm/kysely@0.28.17/node_modules/kysely/dist/cjs/kysely.js:541:20
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)
at async /usr/src/app/server/dist/repositories/database.repository.js:373: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 (/usr/src/app/server/dist/repositories/database.repository.js:51:15)
at process.processTicksAndRejections (node:internal/process/task_queues:104:5)
at async /usr/src/app/server/dist/services/database.service.js:62:31
at async /usr/src/app/server/dist/repositories/database.repository.js:376:27
at async /usr/src/app/server/node_modules/.pnpm/kysely@0.28.17/node_modules/kysely/dist/cjs/kysely.js:541:20
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)
at async /usr/src/app/server/dist/repositories/database.repository.js:373:13
microservices worker exited with code 1
Killing api process
Initializing Immich v3.0.0
Detected CPU Cores: 12
(node:7) ExperimentalWarning: WASI is an experimental feature and might change at any time
(Use `node --trace-warnings ...` to show where the warning was created)
Additional information
No response
I have searched the existing issues, both open and closed, to make sure this is not a duplicate report.
The bug
I just updated to 3.0.0 and now the apps and browser say they cannot find the Immich server. I don't know how to revert the update or fix this.
The OS that Immich Server is running on
Debian 6.1.159-1
Version of Immich Server
v3.0.0
Version of Immich Mobile App
v2.7.5 build.256
Platform with the issue
Device make and model
Debian 6.1.159-1
Your docker-compose.yml content
Your .env content
Reproduction steps
...
Relevant log output
Additional information
No response