-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] connect ECONNREFUSED 172.18.0.8:3001 due to typesense #2224
Comments
What is the CPU used in this machine? What version did you upgrade from? |
I upgraded from v1.50.1 but get the same results on a fresh install CPU Model Name: Pentium(R) Dual-Core CPU E5500 @ 2.80GHz |
That's a very old CPU that typesense probably won't work on (although you'd have to ask them to be sure). I recommend removing typesense from your docker-compose.yml and setting |
Just had the same issue. Disabling typesense fixed it, but wouldn't there be a way to have search with older cpus? Mine is |
I just got this error while updating my stack. My CPU is:
I didn't find anything on the typesense requirements site, so I must assume that it uses AVX2 or something new like that? |
Typesense uses AVX, yes. I believe some people have had success with compiling it themselves to get around that. |
Is there any workaround for this yet without disabling search? I have the same issue on a Intel Pentium D CPU 2.80GHz |
The bug
Can't connect to immich after update to version 1.53.0.
I have tried this using the default docker-compose.yml and .env using an empty media folder and still recieve the same result.
I am running my docker compose using Portainer BE 2.17.1 if that is for any importance.
The OS that Immich Server is running on
Ubuntu 22.04
Version of Immich Server
v1.53.0
Version of Immich Mobile App
not used
Platform with the issue
Your docker-compose.yml content
Your .env content
Reproduction steps
Additional information
Error log of immich server:
Error log of Typesense:
This is my docker ps output:
The text was updated successfully, but these errors were encountered: