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
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:
I tried 0.24.0@sha and 0.24.1 but I remember that it did not work way back...
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:
I tried 0.24.0@sha and 0.24.1 but I remember that it did not work way back...
docker-compose.yml3.93KB
