107 Replies
:wave: Hey @alexeiivanovich,
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. :ballot_box_with_check: verified I'm on the latest release(note that mobile app releases may take some time).
2. :ballot_box_with_check: read applicable release notes.
3. :ballot_box_with_check: reviewed the FAQs for known issues.
4. :ballot_box_with_check: reviewed Github for known issues.
5. :ballot_box_with_check: tried accessing Immich via local ip (without a custom reverse proxy).
6. :ballot_box_with_check: uploaded the relevant information (see below).
7. :ballot_box_with_check: 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.
Successfully submitted, a tag has been added to inform contributors. :white_check_mark:If only there was some kind of error message with a handy link or something in your logs...
How do I "Run docker compose down --remove-orphans"
and sorry i assumed updating stack would automatically make minor changes like this
Updating the stack pulls new container images, it does not update the compose itself
1.118 has breaking change you need to apply
yes, i know. how do i run that command in unraid?
Wherever the compose or config is located at, #unraid is reliant on community support so I'm not sure myself
https://discord.com/channels/979116623879368755/1228387901889445989/1300424741966057494 seems it should "just work" after upgrading
huh? i can edit the docker-compose.yml
i'm asking how to run
docker compose down --remove-orphans
i get these errors without doing that:
is it better to run the AIO container now that exists?No clue how you run CLI commands in Unraid, sorry
And AIO could work fine but I'm guessing you'll need to backup/restore to it
same as any linux, i just don't know the actual command
hmm okay it's not necessary to remove orphans
but now it's giving me the admin reg screen
has it deleted my account?
wow and all photos have been deleted too now
what has happened in this update that has renmoved all previous config
You made some change that resulted in the database being removed or pointing at a different folder
i have made zero changes
where even can you change the db loco?
same as a year ago
where did you get that compose file from? (afaik, immich has always used a variable which is defined as a path in the env file)
you mapped a named volume instead of a bind volume, I assume you did something to delete that named volume
PS: if you provide all data you confirmed you submitted, it is easier to help
you only provided part of the compose file even
check which volumes are available, if the volume is gone and you dont have any backups then you are out of luck
lets hope you did not do the same for your immich, if you used bind mounts there, you should be able to at least access your library and then manually reimport the files (though they might be named differently, depending on your settings)
i originally installed following immich docs
sorry what info do you need that i missed?
i don't know what you mean by named volume vs bind volume
Originally immich did use a docker volume for the db, it was converted at some point to use a file system bind
all my volumes are external libraries
i cant see anywhere to change the database location
i am unfamiliar with unraid, can you list the docker volumes?
docker volume ls
where do i run that command
this is a docker compose so i have no access to console
i dont know :[
sorry, probably best to ask in #unraid
what are docker volumes in this context?
what you listed under volumes
here?
in the database you have it named "pgdata"
just various external libraries
etc.
but as your database seems "cleaned", it is likely you somehow deleted that volume
the only volumes i mapped were for images, none for db
nothing with UPLOAD_LOCATION ?
for the database, you mapped a named volume (pgdata)
ok, your environment file, what is upload location set to?
you can check the folder it is set to for your original pictures
yea, then there...
you can check if you see your photos in there, just to check you at least still have those
yes all files are exactly where they have always been
You should be able to get a terminal somewhere in unraid. You will need to type in
docker volume ls and see if your database still exists in those results.PS: providing bits and pieces is cumbersome, cant you provide all info thats requested by the bot?
nothing about the system has changed
what info
that does nothing in normal terminal
the info you confirmed you submitted
logs is a too massive file
Any recent changes you've made to Immich or your system: none
dpaste.org
Details about your system (both software/OS and hardware):
unraid 6.9.2
i3 12100 • 32 GB DDR4 • Z690
I doubt that, it doesn't "magically" stop working, you must have changed something or updated Immich or such
you didnt update?
cause there were many breaking changes that are mentioned
your logs say immich 130.3
so you likely updated without considering breaking changes
i have updated stack nothing more
df -h https://dpaste.org/jH73d
did you take account of the breaking changes?
if you write what each paste contains, it will be easier for us
which version did you upgrade from?
no idea, i ran update stack as per the instructions
nowhere did it say you need to check logs for breaking changes
logs still too big to copy unless there's a command to get them
It says pretty much everywhere that you should account for breaking changes
as it's now refreshing entire library
could you put all that info together in one post in case this is a longer case and others need to check the info?
its easier to find then
best even to edit one of your first posts to include all information
nowhere i can see: https://immich.app/docs/install/unraid/
there is, it says right in the posts I linked
i mean this
did you click the link right next to it?
also, what is the version you upgraded from?
so that's not the command? it's actually
docker logs immich_server?
100s of screens worth of data i can't copy paste it
as above no idea because i onlly followed the instructions on https://immich.app/docs/install/unraid/
some logs: https://dpaste.org/n9xuK
i just dont get where the old db could have gone. is it still there somewhere?ok, please provide the info that was asked for in a single post in a readable manner, it just makes it easier for us to help you
i was trying to find out by reading logs and the output of "docker volume ls"
docker volume ls does nothing. if you have a working command i can try that
there are no logs in there
edited post
define nothing...
# docker volume ls
DRIVER VOLUME NAME
would still be "something"You should post the actual output of things, not your interpretation of it
That's the wrong command
volume without sso please give me the correct command then
"some logs"...
can you separate it so we can see logs of each container for example?
docker volume ls
i would love to if you tell me how
https://immich.app/docs/guides/docker-help#logs
thats the link right next to the text asking for that info
that was all for
immich_server
which other logs do you needcan you give me the output of
docker volume inspect immich_pgdata ?
every container listed in your compose file "CreatedAt": "2025-03-31T13:40:15+01:00",
it looks like the volume was recreated 😦
you can double check the size by checking the files in the Mountpoint /var/lib/docker/volumes/immich_pgdata/_data
but it looks like the database is lost if you dont have a backup
make sure to backup your photos before you continue to not accidentally delete themwhat volume exactly?
@bo0tzz ?
i am not very familiar with unraid nor with named volumes...
does the update process delete named volumes in unraid?!?
i had to create a new user as the database was all gone
It shouldn't, but no idea if unraid does some nonsense there
all libraries are external and ro so should be safe
i have no idea what named volumes means
all volumes are mapped in the docker-composed.yml as ro
there are no images other than from those external libraries
named volumes are handled by docker engine, they are easier to delete but have some advantages when it comes to permissions on the underlying file system
i only use bind mounts, pointing to directories like you have for your libraries
somehow unraid must have deleted the volume
am i using "bind mounts" or "named volumes" or what?
i have no idea what this terminology means
For the libraries you were using bind mounts (a mount to a folder on the host), for the database you're using https://docs.docker.com/engine/storage/volumes/
i just used the docker-compose.yml that it came with
and only edits i made was adding the externasl libraries
volumes:
- pgdata:/var/lib/postgresql/data
that is a named volume (pgdata, no path given)
volumes:
- "/mnt/user/photos/:/mnt/immich/:ro" # add external library as read only
that is a bind volume, mapping a directory to a directory inside your container
the named volume was already there
and the bind volumes i added
yes, seems that this was in there in previous versions, immich now moved to bind mounts
should i change it
i guess i have to recreate the db again from scratch
i hope there's not an orphan taking up space somewhere
do i have to do all the ml again from scratch too?
yes
right now it looks like this:
if you start from scratch, use an updated compose file, not the one you currently have
im guessing needs to do thumbs
updated how?
it seems i have to start from scratch so maybe easier to just use the AIO anyway?
🤷♂️ I never used Unraid, I use the docker compose method
unraid is using docker compose
👍
I am sorry, I never used Unraid
what do i need to change in my docker-compose
start over probably
sorry what does that entail. delete the stack and start again
i cant even compose down now:
thats a warning, you can remove the version as newer compose versions dont use it
ok but delete stack is no longer available even though it's stopped
sorry, i cannot help you with unraid
need to go to #unraid