Redis Auth Issue After Switching to Valkey – Immich Won’t Start
Hey folks! 👋
I’ve been running Immich smoothly for about 6 months, but recently it stopped working out of nowhere—looks like it’s choking on Redis auth. I’m not sure if I had already switched to Valkey or if that happened during the crash, but since then I haven’t been able to get it back online.
Here’s the error I’m seeing:
🔍 A few things I’ve tried:
- Logging in via redis-cli using both the password and no password → works fine.
- Double-checked that the password is correctly passed in .env and not empty.
- Tried using a custom Redis user (immich) instead of the default Valkey user → still no luck.
I’d prefer not to use the default Valkey user for security reasons, so I’m trying to stick with a dedicated user and password.
Here’s a snippet of my setup:
.env
docker-compose.yml
Redis is reachable, and I can authenticate manually, but Immich keeps throwing the WRONGPASS error. Has anyone managed to get Immich working with Valkey + custom Redis ACLs?
Any tips or working configs would be super appreciated 🙏
7 Replies
:wave: Hey @ilSaul,
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. :blue_square: 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.Why is your
REDIS_HOST
valkey?
Please post your compose @ilSaul
Also, why are you setting these values at allHi! I’ve set up Immich using its Docker Compose file, but Valkey is a separate service with its own Docker Compose configuration. Here’s the ACL I’m using for Immich:
And here’s the Valkey service definition:
Inspect the valkey container, does it also believe it's DNS name is 'valkey' ?
Also... why
Do you think it’s not reaching the Valkey container? It actually responds with the exact error message, so I’m pretty sure it does. I even tried using the default user without disabling security, and the message said that the default user can’t be used from outside the host without a password—so that confirms the connection is working. The error itself is clear: the Redis AUTH command with username and password is being interpreted as a wrong password.
I recommend you start with just a default Immich setup, then apply whatever custom things you want step by step to figure out where it's going wrong
I test it with the command: getent hosts valkey on immich server and the replay is the internal docker ip of the container valkey.
@bo0tzz The Valkey setup is a default one. Have you verified that authentication with username and password works correctly?
I try your configuration add immich_redis inside the compose using default user with nopass and work ... now I try to add user and pw
I try with user and pw work ... now i try to take it out of compose file