Cannot connect to immich.
I had immich running for awhile but have not been able to get it to respond after a power loss (probably unrelated)
it's up to date and i do not see any errors in the logs. I've made sure it's up to date and have not changed any of my configs
64 Replies
Are you talking specifically about the mobile app, the web client, or both? Local network?
cannot connect in any way
What does cannot connect mean? Are you running into a network error?
Does it just spin forever?
app says to check the URL, browser says it can't connect. "Firefox can’t establish a connection to the server at 192.168.1.105:2283."
And docker ps shows all the containers running?
From that machine can you curl port 2283/api/server-info?
refused
Firewall?
no firewall
Can you remote into the server container and curl localhost:3001/server-info (i think)
oh that would do it.
3001 is uptime kuma.
That's port isn't exposed
If you execute it in the container we could verify the API is running correctly.
oh sorry i missed that bit
The only exposed port is 2283 with a reverse proxy via the Nginx container to the API.
You should be able to do docker exec -it containeName sh
curl not found
lol
Wget?
Must have removed it to keep the image small lol
/usr/src/app # cat server-info
{"diskAvailable":"586.7 GiB","diskSize":"3.6 TiB","diskUse":"2.9 TiB","diskAvailableRaw":629924110336,"diskSizeRaw":3934171283456,"diskUseRaw":3143238746112,"diskUsagePercentage":79.9}/usr/src/app #
Sweet
So that means API is up and running fine.
and that i have a good chunk of free disk space lol
Lol yes
So... Either something wrong with proxy container or networking issue.
Can you share docker compose file? .env file?
i didn't modify the compose file afaik
Ok.
and i only changed UPLOAD_LOCATION in the .env
it WAS working with this config
Have you tried stopping and starting the whole stack already?
yeah, i just set the box to reboot so i'll report back
Hmmk. I think logging is turned off in the proxy container, but maybe I should ask if we can enable that, especially for troubleshooting connection issues between the proxy and the server containers.
im not against it
The thing with a reboot is that some pending changes might have taken affect.
(not specifically to immich, just in general)
im counting on one of them to make immich magically work
no such luck this time though.
Do you want to try exposing the port on the API container and hitting it directly?
i'd be okay with Working as Intended.
What happen if you put in yourip:2283/api/server-info on your web browser?
Connection refused i think he said
"Firefox can’t establish a connection to the server at 192.168.1.105:2283."
🤔
And http not https, right?
correct
I meant just to troubleshoot the issue
we can try that
It sounds a lot like a firewall issue imo still
Do you know how to expose the port?
Does anything change after that?
no such
this machine isn't connected to the internet so i don't firewall it
Do you have other browser that you can try?
chrome :
Can you ping it?
Wait
The proxy mapping in the docker ps
It shows port 8080 is in use
But 2283 maps to internal port 80
Is 2283 supposed to map to 8080?
Yes
INTERESTING
Was that changed in docker compose at some point?
Hmm
I mean maybe the old compose used a different pretty or something
Or did Nginx conf change
It changed a long time ago
>_>
Did you change that and test?
GOOD CATCH
you are a good man
It works?
yessir
i would have never ever caught that
Lol
I surprise even myself sometimes
@Alex Tran give this man a raise.
For sure he deserves lotsaa beers
Haha, i don't drink but I'll take some 🍕🍕🍕
Thanks both of you (: im up and running again