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:3001My 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...
10 Replies
Your typesense container has a different name than in the default docker-compose.yml, so you would need to set TYPESENSE_HOST accordingly
ah... oh, ok. I'll try the default then
@bo0tzz That worked, yeah! Thanks
Follow up: The example.env mentions
which I can't reproduce, I think the last "," in the json is wrong anyway.
Would it not be better to write the following into the example.env
?
For a basic setup you're probably better off using
_HOST
etc https://immich.app/docs/install/environment-variables#typesenseright! makes totally sense for my setup.
does it make sense, that the webclient says "Server: offline" and I can see no photos etc... but as soon as I disable typesense again, the server is online again, and the photos are there.
The logs don't show any problem, when typesense is enabled.
Did you check the logs of all the containers?
yes.
when I try to login from another browser, it shows the login screen but "error: unable to connect"
can you post the immich_server log from when this is happening?
sorry, this is the output of:
docker-compose logs -f --tail=1000 immich-server
It's connecting to typesense and starting up with no problems 🤔
oh, maybe the log was not way back as it should. here is a beginning:
and then the server does not complain anymore.
The original post was solved, can I close this post? Let's try.