Hi. A few weeks ago, I set up Immich on my server but didn't have time to import all of my photos yet. Now I came back to it and wanted to import my google photos so I went to the domain my immich was running under and immich opened but returned a 404 error. So, since I didn't have any important data on the server yet I decided to quickly delete the docker containers, download the updated docker-compose.yml and set it up again. However, since then the immich_server fails to start. When I run docker compose up it, all containers start normally except for immich_server which simply returns immich_server exited with code 0.
Anyone know what to do?
#immich_server keeps crashing
1 messages · Page 1 of 1 (latest)
:wave: Hey @fallen tartan,
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
.
References
- Container Logs:
docker compose logsdocs - Container Status:
docker compose psdocs - Reverse Proxy: https://immich.app/docs/administration/reverse-proxy
Checklist
- :ballot_box_with_check: I have verified I'm on the latest release(note that mobile app releases may take some time).
- :ballot_box_with_check: I have read applicable release notes.
- :ballot_box_with_check: I have reviewed the FAQs for known issues.
- :ballot_box_with_check: I have reviewed Github for known issues.
- :ballot_box_with_check: I have tried accessing Immich via local ip (without a custom reverse proxy).
- :ballot_box_with_check: I have uploaded the relevant logs, docker compose, and .env files using the buttons below or the
/uploadcommand. - :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.
docker compose logs
can you do docker compose down then docker compose pull then docker compose up -d --remove-orphans
Thanks! That fixed it!
This thread has been closed. To re-open, use the button below.