Tommy
Tommy
IImmich
Created by Tommy on 1/1/2025 in #help-desk-support
Manually downgrade pgvector.rs?
I managed to goof up a bit and overshot the pgvecto.rs image version when upgrading my postgres instance, accidentally deploying pgvecto.rs 0.4.0 which Immich errored on. So I downgraded the image to pg16-0.3.0 instead, but Immich is still throwing an error about pgvecto.rs 0.4.0 not being compatible. Can I manually update something to make Immich realize that the container/db is running 0.3.0?
4 replies
IImmich
Created by Tommy on 7/5/2023 in #help-desk-support
500 when accessing web server URL
when accessing the web server I'm getting the response "500 self-signed certificate", my config is this:
IMMICH_SERVER_URL=http://api.immich.service.consul:{{ env "NOMAD_HOST_PORT_api" }}
PUBLIC_IMMICH_SERVER_URL=https://immich.mydomain.com/api
IMMICH_SERVER_URL=http://api.immich.service.consul:{{ env "NOMAD_HOST_PORT_api" }}
PUBLIC_IMMICH_SERVER_URL=https://immich.mydomain.com/api
am I doing something wrong here?
90 replies
IImmich
Created by Tommy on 7/4/2023 in #help-desk-support
Startup errors for services
I'm getting this startup error for the server container when starting it with Nomad (i.e. not the docker-compose config in the repo):
Request #1688503235442: Request to Node 0 failed due to "ENOTFOUND getaddrinfo ENOTFOUND typesense"
Request #1688503235442: Sleeping for 4s and then retrying request...
Request #1688503235442: Request to Node 0 failed due to "ENOTFOUND getaddrinfo ENOTFOUND typesense"
Request #1688503235442: Sleeping for 4s and then retrying request...
What is the parameter to set the typesense address, since the container seems to be trying to reach just typesense?
4 replies
IImmich
Created by Tommy on 7/4/2023 in #help-desk-support
QueryFailedError
I'm setting up Immich in my Nomad cluster, so I'm translating the docker-compose setup, but this error is throwing me off. Both the microservices and server containers throw this:
[Nest] 1 - 07/04/2023, 6:14:57 PM ERROR [TypeOrmModule] Unable to connect to the database. Retrying (7)...
QueryFailedError: function uuid_generate_v4() does not exist
at PostgresQueryRunner.query (/usr/src/app/node_modules/typeorm/driver/postgres/PostgresQueryRunner.js:211:19)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async CreateUserTable1645130759468.up (/usr/src/app/dist/infra/migrations/1645130759468-CreateUserTable.js:6:9)
at async MigrationExecutor.executePendingMigrations (/usr/src/app/node_modules/typeorm/migration/MigrationExecutor.js:225:17)
at async DataSource.runMigrations (/usr/src/app/node_modules/typeorm/data-source/DataSource.js:260:35)
at async DataSource.initialize (/usr/src/app/node_modules/typeorm/data-source/DataSource.js:148:17)
[Nest] 1 - 07/04/2023, 6:14:57 PM ERROR [TypeOrmModule] Unable to connect to the database. Retrying (7)...
QueryFailedError: function uuid_generate_v4() does not exist
at PostgresQueryRunner.query (/usr/src/app/node_modules/typeorm/driver/postgres/PostgresQueryRunner.js:211:19)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async CreateUserTable1645130759468.up (/usr/src/app/dist/infra/migrations/1645130759468-CreateUserTable.js:6:9)
at async MigrationExecutor.executePendingMigrations (/usr/src/app/node_modules/typeorm/migration/MigrationExecutor.js:225:17)
at async DataSource.runMigrations (/usr/src/app/node_modules/typeorm/data-source/DataSource.js:260:35)
at async DataSource.initialize (/usr/src/app/node_modules/typeorm/data-source/DataSource.js:148:17)
I'm running postgres:14.8-alpine for my database container, it's shared by several services. Any idea why the uuid_generate_v4 wouldn't be found, or is this error a red herring?
4 replies