ECONNREFUSED Errors in Logs. WebUI doesn't load.
I just had my unRAID server go down. I have it back up (had to replace RAM) and all containers are loading except for Immich. I am getting this error in the logs:
Request to Node 0 failed due to "ECONNREFUSED connect ECONNREFUSED 127.0.0.1:8108
The database and photos share are intact and available. I don't know what it's looking for at 8108.
Any help is appreciated. Thanks!
17 Replies
I see from the immich docs that 8108 is the Typesense host....Not sure what to do about that.
Is that container up? Sometimes it takes a long time to start. You can try restarting the rest of the containers (minus typesense) if it is running now. For large libraries it can take awhile to start.
Just checked again. Still nto started. The immich container is running (unRAID), but the logs are still showing that error for at least the past 15 minutes.
I'm not a docker pro, how do I go about restarting other parts of an immich container and not typesense?
I'm not familiar with unraid or non docker based deployments, so I can't help much there.
How big is your library asset count wise?
So, typically this is set up with typesense as a separate docker container?
Yes
Is this the "all in one image"?
This is still docker, I guess just repackaged into a self-contained piece
Yeah, I guess so ghcr.io/imagegenius/immich:latest
Last I could see the count, I trhink it was 8000 or so photos among 4 users.
Maybe @martabal has a recommendation then. Normally I would say look at the typesense logs and make sure it is up and running correctly.
I can see the logs, but I'm not sure what to be looking for...
That isn't too bad typesense should not take long to start up
You can send them here and I can take a look
Okay, there's a typesense folder and then there's a db LOG file and a meta LOG file....
Then there's a state folder with a log_inprogress file, but I can't open that.
They must be flooding pretty fgast because I can see the log files rotating out to Log.old files by the second.
I have to run out for a bit (this was not on my schedule this morning 😄 ). I'll check back later on. Thank you!!!
Hello, it seems you have an issue with typesense. Can you try to delete the
typesense folder in /config ?Thanks @martabal . Yep. That worked. Are you the same one that replied over on the github page? Thanks! 🙂
Yep it’s me
Happy to hear it solved your issue 😁