34 Replies
:wave: Hey @Dead,
Thanks for reaching out to us. Please follow the recommended actions below; 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 compose ps docs
- Reverse Proxy: https://immich.app/docs/administration/reverse-proxy
Checklist
1. :ballot_box_with_check: I have verified I'm on the latest release(note that mobile app releases may take some time).
2. :ballot_box_with_check: I have read applicable release notes.
3. :ballot_box_with_check: I have reviewed the FAQs for known issues.
4. :ballot_box_with_check: I have reviewed Github for known issues.
5. :ballot_box_with_check: I have tried accessing Immich via local ip (without a custom reverse proxy).
6. :ballot_box_with_check: I have uploaded the relevant logs, docker compose, and .env files, making sure to use code formatting.
7. :ballot_box_with_check: I have 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)
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:Another set of logs
Can you try remove the immich_server image and repull it?
I've done that a few times now given the other tickets similar to this one but no luck
Can you elaborate on how did you remove the images?
I've tried deleting the images via the docker compose GUI as well as doing the docker compose down, prune, pull and then up
maybe theres something else I can do to properly clear the enviroment that I'm missing?
So you can do this
run
docker compose down to bring down the stack
then run docker image to list the images
then
docker rmi <image-id> to remove the imageWill try this thank you
Did I miss any?
looks good
now run
docker compose pullThen up?
yup
Looks stable, will test now
2024-11-26 16:53:41 immich_server | (node:19) [DEP0060] DeprecationWarning: The
util._extend API is deprecated. Please use Object.assign() instead.
2024-11-26 16:53:41 immich_server | (Use node --trace-deprecation ... to show where the warning was created)
2024-11-26 16:53:41 immich_server | (node:7) [DEP0060] DeprecationWarning: The util._extend API is deprecated. Please use Object.assign() instead.
Getting this now
Thanks for the help so faryou can ignore that warning
Doesn't seem to connect via web
2024-11-26 16:55:36 immich_server | [Nest] 7 - 11/26/2024, 3:55:36 AM ERROR [TypeOrmModule] Unable to connect to the database. Retrying (1)...
can you post the content of .env and docker-compose file?
looks normal to me
do
docker compose down and docker compose up again?No luck
did you change this value?
No, oops
oops?
Shouldn't I have?
Looks like there was a different value there when you created the stack, then it was changed
is this a brand new instance?
I had an old one running but shouldve cleared it all out and used defaults for everything
Do I need to change that value elsewhere?
Looks like you are still connecting to the old database
to clean out the old one you will need to remove the postgres folder
That seems to have done it - thank you
Now to build things from scratch again
by any chance do you know how to set up external libaries properly?
What is your docker-compose file looks like>
I got it sorted, found the documentation, wasn't straight forward imo but figured it out 🙂
Thanks for your help mate
No problem man!