Can't setup Immich
After a week of trying and failing im getting "500 Error ECONNREFUSED", I'm using docker and Portainer and the stack has been successfully been deployed but I'm not able to access the WEB UI, the Immich web log is showing the following line
"Listening on 0.0.0.0:3000
[hooks.server.ts]:handleError connect ECONNREFUSED 192.168.64.8:3001"
Please help, it's driving me crazy!!!
66 Replies
Can you post your docker-compose.yml and .env? What do the immich server logs say?
Here are the files
BTW, I'm not using any Reverse Proxy service
Unable to connect to the database. error: password authentication failed for user "postgres"
How is your env file called?
If this is a completely new instance (with nothing uploaded yet), try running
docker compose down -v && docker compose up -d
to clear out the database volume and let it set up from scratch again
Ah, I see you've set this manually on your postgres container
You don't need to change that - the ${}
entries mean they automatically get taken from your env file
Try fixing that then running the command I gave aboveahh, my bad
should I redeploy the the stack with default values ?
That works too
should I change '${UPLOAD_LOCATION}' in docker-compose.yml or will it also take it from .env
You shouldn't need to change the docker-compose.yml at all
okay, let me deploy it again then I'll update you
so i redeployed the stack and I've literally changed nothing in docker-compose.yml EXCEPT .env to stack.env still same error and in the env file i only changed API and Upload Location...
here's my compose and env files...
Did you delete the pgdata volume?
where do you find that
i'm using Portainer
I removed the entire stack
idk, I don't use portainer. I imagine it should have a volumes section somewhere?
It has a section on the left menu called volumes
Yeah I delete all the volumes I had, and redeployed the stack
Those do not look like server logs
it certainly is 😄
What do the logs of the typesense container look like?
Did you delete the tsdata volume as well?
Yes, I deleted all volumes related to Immich
Does it have anything to do with Nginx ?
I mean installing Immich
because i haven't touched Nginx yet
I don't think so. The typesense container is failing to start because of some file system errors
What did you do to redeploy the stack?
I removed the entire stack, then I also removed the volumes related to immich, them i installed (redeployed) immich normally
what method would you suggest for deep cleaning any files or volume which may be left behind
I'm thinking of reinstalling the entire OS, which is a bit annoying but it should help?
Tbh I don't have experience with portainer, so not sure how stuff works there :/
This sounds a bit radical lol
well I only made home server as a hobby and to learn new stuff, and it's fairly new setup so its not ridiculous
Getting into homelab is super fun but it can be annoying sometimes
Yes, that's understandable...
So the "tsdata" volume specifically, you deleted too?
Can you go to the command line and run docker volume ls?
yes

If you've got a cli it becomes a lot easier... Could you bring down the stack again and then run
docker ps -a
?
Ok,
docker volume ls
is probably unchanged, right?
yes !?
Yep, k
Could you run
docker volume prune
?
And confirm with 'y'
yep
Oh, so this hasn't deleted the immich volumes
Could you try
docker volume rm immich_pgdata
then?
And if that works, same for the other immich volumes
did it worked ?
You can check with
docker volume ls
again
But it looks like it, yesyes I checked, it's gone now
Then do the same for the other two :)
which 2
You can also just pass both in the same command
immich_model-cache and immich_tsdata

Just to make sure, could you run
docker volume inspect fac[TAB FOR COMPLETION]
and confirm that this volume doesn't belong to immich?doesn't look like it

Yep, looks very unused tbh
Should have been pruned but whatever, let's just ignore it
Then I guess you can try bringing the stack up again
Did it work?
We should really careful asking the use running this command because it can remove volumes of stopped containers that is not related to Immich
We did an ls before, so I considered it safe enough
But yeah, probably just removing the affected volumes would be better
(Which we ended up doing anyways, because they didn't get pruned lol)
sorry for the late reply, I've been busy lately
just for sanity check I installed Docker on my Windows PC and installed Immich on it and BAM It Worked!
and it gave me a bit confidence so I nuked the OS on my server and reinstalled Debian on it
I tired installing Immich on it and it gave me same old error '500' 😦
I also tried Fedora and same error
@Alex thoughts ?
Logs?
which container logs ?
server would be helpful
Ah you server doesn't seem to support Typesense
I belive the CPU doesn't support AVX instruction
ahh, yes it's a pretty old CPU (Pentium 5800), I never thought about it!
I will be upgrading my homelab hardware soon, then i'll try
meanwhile THANK YOU for your help!
No problem! Cheer!
what is this thingy ?

on iOS
Status