Immich server stop responding after update
Hi there,
I update to 1.121.0 from 1.18.2 and the webpage is not responding. All the containers restart with a "healthy" status. There is no error in the logs.
The port 2283 is open, but no service is responding. Portainer shows the network parameter "com.docker.network.bridge.host_binding_ipv4" to 0.0.0.0 and this is consistant with the Linux "netstat -tunpl | grep 2283" return. Publish ports for the immich-SERVER container shows "2283:3001". Environment: Portainer Community Edition 2.21.14 on a Synology NAS DS1517+ 16Gbs memory, with DSM 7.2.2-72806 Update 2. I am pretty novice in Docker, I can't identify what's is wrong. Thanks for your help.
The port 2283 is open, but no service is responding. Portainer shows the network parameter "com.docker.network.bridge.host_binding_ipv4" to 0.0.0.0 and this is consistant with the Linux "netstat -tunpl | grep 2283" return. Publish ports for the immich-SERVER container shows "2283:3001". Environment: Portainer Community Edition 2.21.14 on a Synology NAS DS1517+ 16Gbs memory, with DSM 7.2.2-72806 Update 2. I am pretty novice in Docker, I can't identify what's is wrong. Thanks for your help.
3 Replies
:wave: Hey @Gaogao,
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. :ballot_box_with_check: 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.
https://github.com/immich-app/immich/discussions?discussions_q=is%3Aopen+label%3Achangelog%3Abreaking-change+sort%3Adate_createdDid you read those?
The specific issue is probably only the port 2283:3001 that needs to be changed, but you should download the new compose file because it will contain new database container commands and so on
Thanks for your reply. If fixed it by just changing the immich server port to '2283:2283' from "2283:3001" inside docker-compose.yml. Before I misread the "breaking change" info of the v1.118.0. Silly, I spent hours searching but I was pretty sure it was Something as simple as this. 🙂