Closed bossanovaorca closed 4 days ago
has anyone run into this issue as well? sadly I am still unable to start my Immich instance due to this redis error loop. It was previously working after installation for a few days but I assume the connection dropped somehow and is unrepairable now?
I believe that the redis docker mod is broken, does it work if you create a seperate redis container and update the redis url?
I believe that the redis docker mod is broken, does it work if you create a seperate redis container and update the redis url?
yes fortunately so far it seems the application does run with a separate redis container. I was hoping to keep redis internal to the immich container though. Is it possible to recover it somehow? in the meantime I'm ok this workaround
I believe that the redis docker mod is broken, does it work if you create a seperate redis container and update the redis url?
yes fortunately so far it seems the application does run with a separate redis container. I was hoping to keep redis internal to the immich container though. Is it possible to recover it somehow? in the meantime I'm ok this workaround
I am facing the exact same in unraid issue as you. Would it be possible if you could share what you did for a work around? Which Redis docker and what you modified/changed to get it working?
Update: Managed to figure it out. I installed prostgresql15 and changed it's repository to "tensorchord/pgvecto-rs:pg14-v0.2.0" and used default port 5432. Then installed Redis (jj9987's repository). Lastly I changed the "DB_PORT" in immich container back to 5432. This worked flawlessly and is actually a bit quicker too!
I've tried restarting my host machine, and re-pulling the images but that didn't work. it seems to have trouble connecting to redis and this error just keeps looping: