cannot see photos after deploying new version
Hi guys,
I upgraded my immich from 1.118 to 123 and I downloaded the new docker compose yaml, but after I executed the commands, it gave me the first time login process and all photos cannot see. Also, I lost all of my accounts.
I checked my storage, and all the photos are still in my path.
I didn't change the content of .env.
Is there any workaround to recover from this?
Thanks
13 Replies
:wave: Hey @zgcye,
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.Don't just copy the latest compose file
Instead always read the breaking changes section thoroughly and apply the relevant changes
so I lost my database, right? Actually, this is the first time I copy the new compose file instead of changing the related part.
I can see 1.118 removed the microservice container, but it seems there's no changes on database from 118 to 123.
No
I am fairly sure you didn't do an optional migration in an earlier version and by just copying the latest compose file now you changed that without doing the respective migration
https://github.com/immich-app/immich/discussions/8930 specifically this one
my postgre are located in local folder as the notes said.
Well there are two options. Either you share your old compose file and we can have a look at the diff together, or you just revert it and manually apply the breaking changes
ok, understood, thanks Daniel. I will try to revert it first.
I found the problem:
I didn't do this change:
- - pgdata:/var/lib/postgresql/data
+ - ${DB_DATA_LOCATION}:/var/lib/postgresql/data but I added the {DB_DATA_LOCATION} in .env before...
+ - ${DB_DATA_LOCATION}:/var/lib/postgresql/data but I added the {DB_DATA_LOCATION} in .env before...
So this message was wrong 😅
And this was the correct pointer :P
apologizes. I misunderstand that. I see the postgre were located under my docker folder as I added in .env as ./postgres, so I thought it was located in local folder...
so I need to manually backup the database and deploy the new version and try to restore database from my backup, right?
Immich created a new one when you started it up with the updated container mounts :P
If you want to migrate away from a docker volume, correct. You 100% don't have to though
understood. I reverted the database settings ,then I think I can keep using docker volume. no issues so far.