Zuri3l Comments - Answer Overflow

Zuri3l

•Created by SlimDayspring on 5/31/2025 in #help-desk-support

Restoring from backup error

@JTtornado If you are using WSL, use this script. In my case, it worked perfectly. Just change the path to your backup.

gunzip < ./backup/dump.sql.gz \
| sed "s/SELECT pg_catalog.set_config('search_path', '', false);/SELECT pg_catalog.set_config('search_path', 'public, pg_catalog', true);/g" \
| docker exec -i immich_postgres psql --username=postgres

gunzip < ./backup/dump.sql.gz \
| sed "s/SELECT pg_catalog.set_config('search_path', '', false);/SELECT pg_catalog.set_config('search_path', 'public, pg_catalog', true);/g" \
| docker exec -i immich_postgres psql --username=postgres

22 replies

IImmich

•Created by SlimDayspring on 5/31/2025 in #help-desk-support

Restoring from backup error

i used the script in linux always linux i dont have windows machines and works perfectly

22 replies

IImmich

•Created by SlimDayspring on 5/31/2025 in #help-desk-support

Restoring from backup error

use the old restoration script

gunzip < ./backup/dump.sql.gz \
| sed "s/SELECT pg_catalog.set_config('search_path', '', false);/SELECT pg_catalog.set_config('search_path', 'public, pg_catalog', true);/g" \
| docker exec -i immich_postgres psql --username=postgres

gunzip < ./backup/dump.sql.gz \
| sed "s/SELECT pg_catalog.set_config('search_path', '', false);/SELECT pg_catalog.set_config('search_path', 'public, pg_catalog', true);/g" \
| docker exec -i immich_postgres psql --username=postgres

I had a similar problem with the new script

22 replies

IImmich

•Created by cuahutecutli on 5/31/2025 in #help-desk-support

Updating .env and compose for 1.133.0

In my case I changed DB_DATA LOCATION to use a named volume and restored the backup using the documentation and with the following code and it solved all my problems

gunzip < ./backup/dump.sql.gz \
| sed "s/SELECT pg_catalog.set_config('search_path', '', false);/SELECT pg_catalog.set_config('search_path', 'public, pg_catalog', true);/g" \
| docker exec -i immich_postgres psql --username=postgres

gunzip < ./backup/dump.sql.gz \
| sed "s/SELECT pg_catalog.set_config('search_path', '', false);/SELECT pg_catalog.set_config('search_path', 'public, pg_catalog', true);/g" \
| docker exec -i immich_postgres psql --username=postgres

  database:
    container_name: immich_postgres
    image: ghcr.io/immich-app/postgres:14-vectorchord0.3.0-pgvectors0.2.0
    environment:
      POSTGRES_PASSWORD: ${DB_PASSWORD}
      POSTGRES_USER: ${DB_USERNAME}
      POSTGRES_DB: ${DB_DATABASE_NAME}
      POSTGRES_INITDB_ARGS: '--data-checksums'
      # Uncomment the DB_STORAGE_TYPE: 'HDD' var if your database isn't stored on SSDs
      # DB_STORAGE_TYPE: 'HDD'
    volumes:
      # Do not edit the next line. If you want to change the database storage location on your system, edit the value of DB_DATA_LOCATION in the .env file
      ####################named-volume#####################
      - immich_postgres_data:/var/lib/postgresql/data
    restart: always

volumes:
  model-cache:
  immich_postgres_data:
    name: immich_postgres_data

  database:
    container_name: immich_postgres
    image: ghcr.io/immich-app/postgres:14-vectorchord0.3.0-pgvectors0.2.0
    environment:
      POSTGRES_PASSWORD: ${DB_PASSWORD}
      POSTGRES_USER: ${DB_USERNAME}
      POSTGRES_DB: ${DB_DATABASE_NAME}
      POSTGRES_INITDB_ARGS: '--data-checksums'
      # Uncomment the DB_STORAGE_TYPE: 'HDD' var if your database isn't stored on SSDs
      # DB_STORAGE_TYPE: 'HDD'
    volumes:
      # Do not edit the next line. If you want to change the database storage location on your system, edit the value of DB_DATA_LOCATION in the .env file
      ####################named-volume#####################
      - immich_postgres_data:/var/lib/postgresql/data
    restart: always

volumes:
  model-cache:
  immich_postgres_data:
    name: immich_postgres_data

and my .env does not have DB_DATA_LOCATION set.

# The location where your uploaded files are stored
UPLOAD_LOCATION=/storage/immich
# The location where your database files are stored
#DB_DATA_LOCATION=./postgres
#ubicacion de las copias de seguridad
#BACKUP_LOCATION=./backup

# The location where your uploaded files are stored
UPLOAD_LOCATION=/storage/immich
# The location where your database files are stored
#DB_DATA_LOCATION=./postgres
#ubicacion de las copias de seguridad
#BACKUP_LOCATION=./backup

11 replies

IImmich

•Created by McVitas on 5/19/2025 in #help-desk-support

mobile app slow

You also have to consider your hardware on the server, how much it can process all your files, could also be the problem.

14 replies

IImmich

•Created by Zuri3l on 5/22/2025 in #help-desk-support

Can't deploy a fully new instance 1.133.0 or restoring a backup

I tried it but it didn't work, for some reason even if I use sudo the owner is still root

➜  immich-app la
total 303M
-rwxrwxrwx 1 root root  943 May 22 09:28 .env
-rwxrwxrwx 1 root root 2.6K May 22 12:29 docker-compose.yml
-rwxrwxrwx 1 root root 303M May 21 18:40 dump.sql.gz
drwxrwxrwx 1 root root 4.0K May 22 14:42 library
drwxrwxrwx 1 root root 4.0K May 22 14:42 postgres
➜  immich-app sudo chown 999:999 postgres
➜  immich-app la
total 303M
-rwxrwxrwx 1 root root  943 May 22 09:28 .env
-rwxrwxrwx 1 root root 2.6K May 22 12:29 docker-compose.yml
-rwxrwxrwx 1 root root 303M May 21 18:40 dump.sql.gz
drwxrwxrwx 1 root root 4.0K May 22 14:42 library
drwxrwxrwx 1 root root 4.0K May 22 14:42 postgres

➜  immich-app la
total 303M
-rwxrwxrwx 1 root root  943 May 22 09:28 .env
-rwxrwxrwx 1 root root 2.6K May 22 12:29 docker-compose.yml
-rwxrwxrwx 1 root root 303M May 21 18:40 dump.sql.gz
drwxrwxrwx 1 root root 4.0K May 22 14:42 library
drwxrwxrwx 1 root root 4.0K May 22 14:42 postgres
➜  immich-app sudo chown 999:999 postgres
➜  immich-app la
total 303M
-rwxrwxrwx 1 root root  943 May 22 09:28 .env
-rwxrwxrwx 1 root root 2.6K May 22 12:29 docker-compose.yml
-rwxrwxrwx 1 root root 303M May 21 18:40 dump.sql.gz
drwxrwxrwx 1 root root 4.0K May 22 14:42 library
drwxrwxrwx 1 root root 4.0K May 22 14:42 postgres

And yes, I also tried to deploy it after change it and it didn't work, same error

20 replies

IImmich

•Created by Zuri3l on 5/22/2025 in #help-desk-support

Can't deploy a fully new instance 1.133.0 or restoring a backup

➜  immich docker exec -it immich_postgres bash
Error response from daemon: Container 2eb290c3064b5e398b32771b82705fa2a0d4909de9958ad5fcf5b2c3852e6ffe is restarting, wait until the container is running

➜  immich docker exec -it immich_postgres bash
Error response from daemon: Container 2eb290c3064b5e398b32771b82705fa2a0d4909de9958ad5fcf5b2c3852e6ffe is restarting, wait until the container is running

I have tried to manually change the permissions of the container folder but it does not allow me to enter the container for obvious reasons.

20 replies

IImmich

•Created by Zuri3l on 5/22/2025 in #help-desk-support

Can't deploy a fully new instance 1.133.0 or restoring a backup

I even downloaded the docker-compose.yml and example.env files from the repository to test and it didn't work either

20 replies

IImmich

•Created by Zuri3l on 5/22/2025 in #help-desk-support

Can't deploy a fully new instance 1.133.0 or restoring a backup

20 replies

IImmich

•Created by Zuri3l on 5/22/2025 in #help-desk-support

Can't deploy a fully new instance 1.133.0 or restoring a backup

On my Windows 10 machine, using WSL 2 with Ubuntu and using the terminal, I used mkdir for the main folder and from the terminal using Docker Compose I deployed the stack. but I have the same problem with my installation on my server with omv, in fact they are the same errors that it is giving me, but only version 1.133.0, all previous versions work correctly and I can deploy them normally, for immich I do not use the gui, only terminal

20 replies

IImmich

•Created by Zuri3l on 5/22/2025 in #help-desk-support

Can't deploy a fully new instance 1.133.0 or restoring a backup

This is the command in my main stack, which is working correctly with version 1.132.3, where I have the same problem when updating or restoring the database.

➜  immich ls -la
total 32
drwxr-s---+  3 root                  users 4096 may 22 07:57 .
drwxrws---+ 15 root                  users 4096 may 21 17:43 ..
-rw-r-----+  1 root                  users 3446 may 22 07:56 docker-compose.yml
-rw-r-----+  1 root                  users 1017 may 22 07:57 .env
drwx------+ 21 openmediavault-webgui root  4096 may 22 07:57 postgres

➜  immich ls -la
total 32
drwxr-s---+  3 root                  users 4096 may 22 07:57 .
drwxrws---+ 15 root                  users 4096 may 21 17:43 ..
-rw-r-----+  1 root                  users 3446 may 22 07:56 docker-compose.yml
-rw-r-----+  1 root                  users 1017 may 22 07:57 .env
drwx------+ 21 openmediavault-webgui root  4096 may 22 07:57 postgres

20 replies

IImmich

•Created by Zuri3l on 5/22/2025 in #help-desk-support

Can't deploy a fully new instance 1.133.0 or restoring a backup

yup, give me a second This is from the test stack

➜  immich ls -la
total 310248
drwxrwxrwx 1 root root      4096 May 22 13:11 .
drwxrwxrwx 1 root root      4096 May 22 12:34 ..
-rwxrwxrwx 1 root root       943 May 22 09:28 .env
-rwxrwxrwx 1 root root      2605 May 22 12:29 docker-compose.yml
-rwxrwxrwx 1 root root 317683872 May 21 18:40 dump.sql.gz
drwxrwxrwx 1 root root      4096 May 22 13:11 library
drwxrwxrwx 1 root root      4096 May 22 13:11 postgres

➜  immich ls -la
total 310248
drwxrwxrwx 1 root root      4096 May 22 13:11 .
drwxrwxrwx 1 root root      4096 May 22 12:34 ..
-rwxrwxrwx 1 root root       943 May 22 09:28 .env
-rwxrwxrwx 1 root root      2605 May 22 12:29 docker-compose.yml
-rwxrwxrwx 1 root root 317683872 May 21 18:40 dump.sql.gz
drwxrwxrwx 1 root root      4096 May 22 13:11 library
drwxrwxrwx 1 root root      4096 May 22 13:11 postgres

20 replies

IImmich

•Created by Zuri3l on 5/22/2025 in #help-desk-support

Can't deploy a fully new instance 1.133.0 or restoring a backup

Okay, I've fixed that mistake

immich_server  =
Initializing Immich v1.133.0

Detected CPU Cores: 16

Starting api worker

Starting microservices worker

[Nest] 7  - 05/22/2025, 12:26:48 PM     LOG [Microservices:EventRepository] Initialized websocket server

[Nest] 19  - 05/22/2025, 12:26:49 PM     LOG [Api:EventRepository] Initialized websocket server

microservices worker error: Error: getaddrinfo ENOTFOUND database, stack: Error: getaddrinfo ENOTFOUND database

    at GetAddrInfoReqWrap.onlookupall [as oncomplete] (node:dns:120:26)

microservices worker exited with code 1

Killing api process

immich_server  =
Initializing Immich v1.133.0

Detected CPU Cores: 16

Starting api worker

Starting microservices worker

[Nest] 7  - 05/22/2025, 12:26:48 PM     LOG [Microservices:EventRepository] Initialized websocket server

[Nest] 19  - 05/22/2025, 12:26:49 PM     LOG [Api:EventRepository] Initialized websocket server

microservices worker error: Error: getaddrinfo ENOTFOUND database, stack: Error: getaddrinfo ENOTFOUND database

    at GetAddrInfoReqWrap.onlookupall [as oncomplete] (node:dns:120:26)

microservices worker exited with code 1

Killing api process

is now waiting for database i think but the database = ❌

Using SSD storage

chmod: changing permissions of '/var/lib/postgresql/data': Operation not permitted

The files belonging to this database system will be owned by user "postgres".

This user must also own the server process.


The database cluster will be initialized with locale "en_US.utf8".

The default database encoding has accordingly been set to "UTF8".

The default text search configuration will be set to "english".


Data page checksums are enabled.


initdb: error: could not change permissions of directory "/var/lib/postgresql/data": Operation not permitted

fixing permissions on existing directory /var/lib/postgresql/data ... 2025-05-22T18:24:56.464255958Z Using SSD storage

chmod: changing permissions of '/var/lib/postgresql/data': Operation not permitted

The files belonging to this database system will be owned by user "postgres".

This user must also own the server process.

Using SSD storage

chmod: changing permissions of '/var/lib/postgresql/data': Operation not permitted

The files belonging to this database system will be owned by user "postgres".

This user must also own the server process.


The database cluster will be initialized with locale "en_US.utf8".

The default database encoding has accordingly been set to "UTF8".

The default text search configuration will be set to "english".


Data page checksums are enabled.


initdb: error: could not change permissions of directory "/var/lib/postgresql/data": Operation not permitted

fixing permissions on existing directory /var/lib/postgresql/data ... 2025-05-22T18:24:56.464255958Z Using SSD storage

chmod: changing permissions of '/var/lib/postgresql/data': Operation not permitted

The files belonging to this database system will be owned by user "postgres".

This user must also own the server process.

same problem I fixed the error in compose.yml. I'm deploying from scratch and the same problem.

20 replies

IImmich

•Created by Zuri3l on 5/22/2025 in #help-desk-support

Can't deploy a fully new instance 1.133.0 or restoring a backup

Here are my compose.yml and .env files

20 replies

IImmich

•Created by Hypolumar on 5/19/2025 in #help-desk-support

Error in windows 11 Docker WSL2

the best way of deploy in windows is usin wsl in terminal, your directories appear like linux an works realy good, use the route

 /mnt/your-disk/route/to/ur/library

 /mnt/your-disk/route/to/ur/library

165 replies

IImmich

•Created by Mike_M on 5/22/2025 in #help-desk-support

Is the way I updated to v1.133.0 fine?

Well, the instructions are there, so I don't think there is any error or problem.

7 replies

IImmich

•Created by Mike_M on 5/22/2025 in #help-desk-support

Is the way I updated to v1.133.0 fine?

Sorry, but how did you do the restore? I use the Docker CLI, and when I use docker start immich_postgres, the container restarts, and the logs say there are errors in the postgresql.conf file and I can't get the container to start

7 replies

Gaming

Programming