arnob
IImmich
•Created by arnob on 2/2/2025 in #help-desk-support
Immich-Server unhealthy
It was working just fine. Yesterday, I created new user and started backing up its files from mobile to the immich server and now at morning, cannot access immich anymore. immich_server shows as unhealthy.
It is setup through docker inside a LXC.
docker-compose.yml
https://pastebin.com/t1dNAWQj
.env file
https://pastebin.com/vuG0m4ec
Docker container logs
https://pastebin.com/bSR0cSZ7
' SERVICE CREATED STATUS PORTS immich_machine_learning ghcr.io/immich-app/immich-machine-learning:release "tini -- ./start.sh" immich-machine-learning 19 minutes ago Up About a minute (healthy)
immich_postgres docker.io/tensorchord/pgvecto-rs:pg14-v0.2.0@sha256:90724186f0a3517cf6914295b5ab410db9ce23190a2d9d0b9dd6463e3fa298f0 "docker-entrypoint.s…" database 19 minutes ago Up About a minute (healthy) 5432/tcp immich_redis docker.io/redis:6.2-alpine@sha256:eaba718fecd1196d88533de7ba49bf903ad33664a92debb24660a922ecd9cac8 "docker-entrypoint.s…" redis 7 weeks ago Up About a minute (healthy) 6379/tcp immich_server ghcr.io/immich-app/immich-server:release "tini -- /bin/bash s…" immich-server 19 minutes ago Up About a minute (unhealthy) 0.0.0.0:2283->2283/tcp' Server log: Error: connect ETIMEDOUT at Socket.<anonymous> (/usr/src/app/node_modules/ioredis/built/Redis.js:170:41) at Object.onceWrapper (node:events:638:28) at Socket.emit (node:events:524:28) at Socket._onTimeout (node:net:609:8) at listOnTimeout (node:internal/timers:594:17) at process.processTimers (node:internal/timers:529:7) { errorno: 'ETIMEDOUT', code: 'ETIMEDOUT', syscall: 'connect' }
9 replies