if i just tried to update and immich is now telling me to setup an admin user, how cooked am i?
currently gathering info but i was on immich like 133.1 or something like that and trying to update to the current latest version.
I think i have a backup (untested) of the DB so i guess that helps. Curious if theres a recovery guide somewhere though
10 Replies
:wave: Hey @Adrian E. (Open Source),
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.Your compose + .env?
yeah ive been using a compose + .env setup
i also work a lot with docker and docker compose day to day for work if that helps
Yeah, sorry, I meant more info as per the auto-post above
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.
ohhhh
I'm just thinking how it could lost Postgres data. Maybe if PG data volume was anonymous or like that.
i tend to avoid volumes for important data. only volume im using is model-cache. everything else is mounted to a path on the machine
i think when i first brought things up after upgrading it was using
ghcr.io/immich-app/postgres:14-vectorchord0.4.3-pgvectors0.2.0@sha256:8d292bdb796aa58bbbaa47fe971c8516f6f57d6a47e7172e62754feb6ed4e7b0
for the db, but the old image for the server, so it complained about vectorchord 0.4.3 being too new. Wonder if that could have done it?
currently trying to connect to the db and see whether it basically got initialized or what happened (and possibly restore it from the backup)
ah yep, db looks empty af
(sorry for the lack of info, im sorta just liveposting here as i work through this and figure out what happened)
one log line i did see that was interesting was
if the DB is empty that makes sense
most likely you had a broken mount point or something like that
postgres doesn't just lose databases
the db definitely didnt used to be empty though
so uuh idk what happened
i prob could have still f*cked up a mount point or something
yep thats what happened
in migrating to using ansible to manage my docker stuff, i fucked up a path
yep, i got it to work again
This thread has been closed. To re-open, use the button below.