Cannot connect to web interface 500connect ECONNREFUSED 172.18.0.8:3001
Hi All
Been using Immich for about a week now and its all been working great. However today I can no longer access the webui, i get the error above.
When i check the logs on my immich_server container im getting:
Request to Node 0 failed due to "undefined Request failed with HTTP code 503 | Server said: Not Ready or Lagging"
Request #1689688854030: Sleeping for 4s and then retrying request...
Does anyone have any suggestions?
41 Replies
do you still have this error? Try bring down and bring up and all the containers
yeah i have restarted all containers, and even restarted my unraid system, still the same
this indicate typesense has issue, I saw a similar report today, I am not sure what is going on with the container yet since we pinned the version
which installation method do you use?
ive been getting Nest] 1 - 07/18/2023, 2:29:17 PM ERROR [JobService] Unable to run job handler: Error: connect ECONNREFUSED 172.18.0.8:3003
[Nest] 1 - 07/18/2023, 2:29:17 PM ERROR [JobService] Error: connect ECONNREFUSED 172.18.0.8:3003
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1494:16)
[Nest] 1 - 07/18/2023, 2:29:17 PM ERROR [JobService] Object:
{
"id": "7e3132bf-70f0-49e6-92f6-b5df1f4c4053",
"source": "upload"
} in micro container service log
which installation method do you use?
ive been using the repository in the unraid appstore
imagegenius repository
Can you reach out to the maintainer of that image, to see if somethings has changed in their build? We don't maintain that image
yeah sure
do you reckon its worth burning all the containers and bringing it up again with compose?
Depends on your use case, with the recommended method, you will get better support because we control the process
actually i cant remember if i used the official version or not now.. i need to check my history on ym computer at home....🤔
right sorry, i DID use the official version to install
Unraid | Immich
Immich can easily be installed and updated on Unraid via:
via docker-compose?
yeah i installed docker compose on unraid
exactly as per that link
Great, you can now try this. Use this image for Typesense
image: typesense/typesense:0.24.0just delete the other one and install that manually via docker?
you change the image name in docker-compose file, the bring down the stack with
docker-compose down and then docker-compose pull to pull new images and finally docker-compose upright ok, sorry im fairly new to containerization
No problem man, we can help
this is a fantastic project by the way, people like you are heros 😄
Thank you 🙂
so thats effectivly knocking it back to the previous version?
There are reported issue with 0.24.1 version of Typesense on some systems so it is good to try the previous version of Typesense, it shouldn't intefere with how Immich works
yeah no i get that, i work in IT so I deal with crap like that all the time 🙄
takes a while to start on my machine..
hmm, still getting: Request to Node 0 failed due to "undefined Request failed with HTTP code 503 | Server said: Not Ready or Lagging"
Request #1689692050032: Sleeping for 4s and then retrying request...
Request #1689692050032: Request to Node 0 failed due to "undefined Request failed with HTTP code 503 | Server said: Not Ready or Lagging"
in the immich_server log
let it sit there for a bit, typesense might be indexing
how many assets do you have on the instance?
yeah...well...quite alot
67k
yeah it might take maybe a minute before the reindexing is done
bearing in mind my hardware is fairly old
that would add some more times one top
once its up and going its been running surprisingly quickly
my instance with about 30k assets
also get that message when it is indexing
so you should be set once it is done
i think the immich_server instance is restarting
Can you please capture the entire logs of immich_server please?
Can you wait for a few more minutes and check the log to see if the server eventually starts?
yeah im just finishing work now anyway so will drive home and see what happens
is it usual that the typesense instance doesnt provide logs?
we disable logs of Typesense instance because we don't normally use those messages
You can reanable it by remove the line
of typesense in docker-compose file
ok thats ok then
wasnt sure if it might be useful..
Hey Alex, thanks so much for your help earlier, seems to be working again now!
No problem, so it might just be whenever you restart/update the stack, it might take a bit of time to get the indexing done
Yeah possibly, but I think rolling back typesense fixed the main issue. I was just impatient after that. 😁