#Immich Locks Up Server - Community App & Docker Install
1 messages · Page 1 of 1 (latest)
:wave: Hey @atomic tundra,
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
- :blue_square: I have verified I'm on the latest release(note that mobile app releases may take some time).
- :blue_square: I have read applicable release notes.
- :blue_square: I have reviewed the FAQs for known issues.
- :blue_square: I have reviewed Github for known issues.
- :blue_square: I have tried accessing Immich via local ip (without a custom reverse proxy).
- :blue_square: I have uploaded the relevant logs, docker compose, and .env files using the buttons below or the
/uploadcommand. - :blue_square: 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.
You can create an additional service in docker-compose.yml file to see if it helps with not locking up https://immich.app/docs/administration/jobs-workers#split-workers
feel free to post your modified docker-compose.yml here so we can help you verify
I'm using the community app right now, does that still apply to that one?
Ah then no
You may add resource limits to your compose file, as I suggested earlier. For example, limit immich to only use up to 3 CPUs so your whole system does not lock up,
https://www.baeldung.com/ops/docker-memory-limit#compose