#Immich error connect timeout

1 messages · Page 1 of 1 (latest)

muted lodge
#

Hello everyone, I’ve been trying to get my Immich setup running correctly since December 2025. Whenever I completely reinstall everything and the external libraries have been scanned and all jobs have finished, it runs fine for 1–2 days, sometimes even up to 5 days. Then suddenly, out of nowhere, all active jobs in the task queue get stuck at “1”, and the problems start piling up — external libraries stop being scanned, or Immich reports that corrupted files were found…
Can someone help me with this? Unfortunately, I’m not very familiar with Docker.

My setup:

Intel N100 mini PC with 16 GB RAM running Windows 11

Linux VM running on Oracle VirtualBox, with Immich running in Docker

The VM has 4 CPU cores and 11 GB RAM assigned

External libraries are mounted in Linux via NFS 4.1

Photos and videos are stored on my Synology NAS

The database is stored locally on the VM’s SSD

Thumbnails and encoded videos are stored on the NAS

Immich version: V2.7.5

The Immich server logs, Redis logs, ML logs, plus my Docker Compose and .env files are attached.
Immich was restarted using docker compose down and docker compose up -d, and the logs were collected about 20 minutes afterward.

Thank you very much for your help,
Regards,
Moritz

📎 env 📎 docker-compose.yml 📎 Immich_Server_logs.txt 📎 ML.txt 📎 redis.txt
molten nebulaBOT
#

:wave: Hey @muted lodge,

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

#

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.

brave urchin
#

Hey, unfortunately we only provide support in English (otherwise only very few people can help you and it makes moderation much harder). The logs pretty clearly show that Immich cannot reach Redis anymore. I am quite confused by your setup. You're saying it's running on a mini PC that's running Windows, but then you have a VM on oracle?

balmy kernel
#

I think this is a NFS mount from a NAS to the Oracle VM. Which ... sounds like waiting for things to break. Network mounts on high latency links over the internet just are not all that reliable.

muted lodge
#

Okay, sorry for the confusion...

I have a mini PC with Windows 11 installed on it. On Windows 11, I created a virtual machine with Linux Mint using Oracle, and Immich is running inside that VM. I know it's probably the worst possible setup, but I haven’t found any way to make my NAS visible in Docker Desktop on Windows 11. Everywhere I’ve read, people say that Docker Desktop cannot handle network drives. The mini PC and my NAS are on the same network. I also read that the best way to use external libraries from a network drive is through NFS, because everything else seems to be too error‑prone for Immich when dealing with many files.

📎 Docker_PS.txt
brave urchin
#

created a virtual machine with Linux Mint using Oracle
This still doesn't make any sense to me. Oracle is a company

muted lodge
#

Oracel Virtalbox

brave urchin
#

Oh, Virtualbox, I see

#

Tbh I am actually not really sure what's going on. Is it possible that windows is pausing/halting the virtual machine somehow?

#

Or, like, go to standby or something

muted lodge
#

Unfortunately not — I sometimes have these issues even when I’m directly inside the Linux VM and watching the live logs of the Immich server.
Jellyfin is also running inside the same Linux VM, and we never have any problems with it. The media for Jellyfin are also mounted via NFS, and everything works perfectly there.
That’s why I was hoping that maybe my compose file or my environment variables are incorrect, or that I’m simply missing a variable that needs to be added.
When I restart Immich using docker compose down and docker compose up, I’m often lucky and everything works again for a while. After some time, however, the issues return. Immich never becomes completely unusable — it stays reachable — but all my active jobs jump back to 1 whenever new images are added to the external library, and sometimes I also get failed tasks.
I’m not very good at English, so I’m using a translator. Because of that, some words or sentences might not make perfect sense — sorry about that.

brave urchin
#

Yeah the behavior you're seeing makes sense as the only thing that's failing is the connection to Redis. Redis is the job broker we're using and handles the job queues (so they never get processed correctly and the active jobs stay at 1 etc). It's just weird that it fails to connect while Redis still seems to be running perfectly fine (there are logs from around that showing it's up and running)

#

As for English, you're good! We're also happy to deal with not-so-good english, so if you want to practice that, feel free to! If there are some words you don't know in English, German is also fine (I'm German actually), I'd just like to keep the primary conversation in english :)

#

@balmy kernel you got anything?

safe basin
#

did you do anything weird to try to get docker to run on the NAS? please post output of docker inspect immich_redis

# 
     - /mnt/nas/homes/Linux/immich:/data
      - /mnt/nas/homes:/external

This is problematic , could be leading to infinite loop and system overload maybe

muted lodge
#

I previously had Immich running on my NAS in Docker for a while, but the CPU was too weak, so the context search was unusable even after indexing and using the smallest CLIP model. Currently, Immich is running in Docker inside my Linux VM.

/mnt/nas/homes/Linux/immich:/data → this is where Immich stores its data, such as encoded videos, thumbnails, etc.

/mnt/nas/homes:/external → this contains all user home directories from my NAS. I mounted the entire homes folder so I can easily add new external libraries in Immich without creating a new mount for each user and modifying the compose file again. However, if this setup could be causing the issues, I’m absolutely willing to restructure the mounts and only mount the actual photo folder of each NAS user and update the compose file accordingly.

The output of docker inspect immich_redis is attached.
Thanks for your help.

📎 docker_inspect_immich_redis.txt
muted lodge
#

I’ve created new dedicated mounts for each user and updated my docker‑compose configuration so that the external library paths and the /data directory no longer overlap. I’ll monitor the system over the next few days to see how it behaves.

balmy kernel
# brave urchin <@135843138492170241> you got anything?

Not really, since logs do seem normal apart from the connection issue. Since it's internal docker network I don't think the virtual network adapter is the issue, or at least I would not expect it. The manual definition of the immich network is not in our example compose file, but it should be following docker defaults. i.e. also unlikely.

#

Apart from doing a full docker compose down & docker compose up cycle, you might also want to try to delete the redis volume to start clean.

muted lodge
#

Ah ok, I completely reinstalled Immich so everything could start fresh with the new mounts and external libraries. My mini PC is still indexing (we have over 700 GB of photos and videos). Since the reinstall, everything has been running normally.

I have the feeling that the issues only appear when I restart Immich using docker compose down/up or when I reboot the VM. Once the indexing is finished, I’ll create a snapshot of the VM so I can always return to a known working state and then test different scenarios.

From what I understand based on your feedback, Immich itself seems fine, and the problem is more likely related to my Docker setup — or more specifically the internal Docker network. Is that correct?