Immich Server won't start, Redis Error
Hello Alex and Team,
Thank you for such a wonderful software.
In continuation to the issue I posted in github: https://github.com/immich-app/immich/issues/15987
I tried to do a fresh install by creating new directories for immich, and doing a fresh install in that directory, to see if the server starter normally. But for some unknown reason, the error persisted to my dismay. Do you think this has got something to do with Synology DSM Update? 7.2.2.72806 Update 3 that was released on Feb 4th 2025? Here is what I did: - Created a new folder called "imch" and added db & upload folder under that - Created a new stack in portainer and used the following yml and env - Executed the stack in portainer but the error persists.
I tried to do a fresh install by creating new directories for immich, and doing a fresh install in that directory, to see if the server starter normally. But for some unknown reason, the error persisted to my dismay. Do you think this has got something to do with Synology DSM Update? 7.2.2.72806 Update 3 that was released on Feb 4th 2025? Here is what I did: - Created a new folder called "imch" and added db & upload folder under that - Created a new stack in portainer and used the following yml and env - Executed the stack in portainer but the error persists.
6 Replies
:wave: Hey @KTN6,
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. :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.
Successfully submitted, a tag has been added to inform contributors. :white_check_mark:Here are the env/yml files and logs
@Alex Tran and other immich developers, kindly advice.
Thank you again for your lovely SW, I am also supporting you by becoming a patron. Please keep up this great work!
Please don't tag people 😛
If the error persists after a complete fresh start it is possible the downloaded container image is corrupted
To test this, stop all immich instances, delete the containers + container image, don't delete the DB or other data! and then re-pull the images
My apologies for tagging. Thank you Mrardis for your advice. I tried the same but the same error persists 😦 😦
Guys, I got the solution. It was to do with Synology Firewall. Turned it off and it works perfectly now!
This thread has been closed. To re-open, use the button below.