ImmichI
Immich•3y ago
jolly-jump

EAI_AGAIN when first using typesense

Hi.
I have the problem that I disabled typesense around the time the API_KEY was needed in the .env-file, since then the following happens:
  • typesense starts
  • immich-server (and all others) start but the logs say
    "immich-server | Request #1687720564012: Request to Node 0 failed due to "EAI_AGAIN getaddrinfo EAI_AGAIN typesense"
    immich-server | Request #1687720564012: Sleeping for 4s and then retrying request...
    "
    and, of course, no webservice is possible, saying
    500
    connect ECONNREFUSED 172.18.0.15:3001
My setup is a bit off the standard, since I am using a nginx reverse proxy in front of the immich-proxy.
docker-compose.yml, relevant part is appended.

The .env-File, except comments:
NODE_ENV=production
LOG_LEVEL=verbose
DB_HOSTNAME=immich-db
DB_USERNAME=postgres
DB_PASSWORD=xxxxxxxxxxx
DB_DATABASE_NAME=immich
REDIS_HOSTNAME=immich-redis
UPLOAD_LOCATION=/srv/docker/immich/data
TYPESENSE_ENABLED=false
TYPESENSE_API_KEY=chuthii6Jei1ooraiFoyeezuph4ohc
DISABLE_REVERSE_GEOCODING=true
PUBLIC_LOGIN_PAGE_MESSAGE=
IMMICH_WEB_URL=http://immich-web:3000
IMMICH_SERVER_URL=http://immich-server:3001
IMMICH_MACHINE_LEARNING_URL=http://immich-ml:3003


I tried 0.24.0@sha and 0.24.1 but I remember that it did not work way back...
docker-compose.yml3.93KB
Was this page helpful?