Can't deploy a fully new instance 1.133.0 or restoring a backup
I've been having issues updating or restoring my instance backup, so I decided to deploy a new instance as a test, but when I tried,
-redis = ok
-machine_learning = ok
-database = wrong
-immich_server = wrong
If I try to restore a backup, the situation is similar.
and the same thing over and over again, whenever I try to deploy it, even if it's a new instance like at the beginning
HELPPPP...
13 Replies
:wave: Hey @Zuri3l,
Thanks for reaching out to us. Please carefully read this message and follow the recommended actions. This will help us be more effective in our support effort and leave more time for building Immich :immich:.
References
- Container Logs:
docker compose logs
docs
- Container Status: docker ps -a
docs
- Reverse Proxy: https://immich.app/docs/administration/reverse-proxy
- Code Formatting https://support.discord.com/hc/en-us/articles/210298617-Markdown-Text-101-Chat-Formatting-Bold-Italic-Underline#h_01GY0DAKGXDEHE263BCAYEGFJA
Checklist
I have...
1. :blue_square: verified I'm on the latest release(note that mobile app releases may take some time).
2. :blue_square: read applicable release notes.
3. :blue_square: reviewed the FAQs for known issues.
4. :blue_square: reviewed Github for known issues.
5. :blue_square: tried accessing Immich via local ip (without a custom reverse proxy).
6. :blue_square: uploaded the relevant information (see below).
7. :blue_square: tried an incognito window, disabled extensions, cleared mobile app cache, logged out and back in, different browsers, etc. as applicable
(an item can be marked as "complete" by reacting with the appropriate number)
Information
In order to be able to effectively help you, we need you to provide clear information to show what the problem is. The exact details needed vary per case, but here is a list of things to consider:
- Your docker-compose.yml and .env files.
- Logs from all the containers and their status (see above).
- All the troubleshooting steps you've tried so far.
- Any recent changes you've made to Immich or your system.
- Details about your system (both software/OS and hardware).
- Details about your storage (filesystems, type of disks, output of commands like fdisk -l
and df -h
).
- The version of the Immich server, mobile app, and other relevant pieces.
- Any other information that you think might be relevant.
Please paste files and logs with proper code formatting, and especially avoid blurry screenshots.
Without the right information we can't work out what the problem is. Help us help you ;)
If this ticket can be closed you can use the /close
command, and re-open it later if needed.Here are my compose.yml and .env files
You forgot to disable the
command
part of the database containerOkay, I've fixed that mistake
is now waiting for database i think
but the database = ❌
same problem
I fixed the error in compose.yml. I'm deploying from scratch and the same problem.
Could you show us an
ls -la
from the folder where your docker compose.yml is atyup, give me a second
This is from the test stack
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.
Your postgres folder is owned by root
How did you make this "test" stack?
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

I even downloaded the docker-compose.yml and example.env files from the repository to test and it didn't work either
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.
try changing the owner of your postgres folder to user
999
I tried it but it didn't work, for some reason even if I use sudo the owner is still root
And yes, I also tried to deploy it after change it and it didn't work, same error
what 👀
Ok here's what I would do in case everything seems "stuck" like this
Turn off the immich stack, reboot the whole machine, see if you can change owner now