Immich•3y ago

500 ENOTFOUND immich_server

I can't seem to get past variations of this message no matter what I try. And I can't seem to find information on what to look for as the cause. Any help?

jrasm91•3/10/23, 4:03 AM

Can you post your docker compose details and env file?

sunbrolynkOP•3/10/23, 4:12 AM

https://pastebin.pl/view/25c7971d

Untitled - Pastebin

Pastebin.pl is a website where you can store code/text online for a set period of time and share to anybody on earth

sunbrolynkOP•3/10/23, 4:13 AM

https://pastebin.pl/view/14bb3aed

Untitled - Pastebin

Pastebin.pl is a website where you can store code/text online for a set period of time and share to anybody on earth

bo0tzz•3/10/23, 10:11 AM

Can you check the docker logs to see if the immich-server container is starting properly?

jrasm91•3/10/23, 11:00 AM

I am also a little confused by the screenshot. Why are you accessing port 3000, should you not be using port 2283 and the IP of the immich proxy container?

sunbrolynkOP•3/10/23, 1:47 PM

When I first launched it it was up at 2283, but same exact issue., except it gave me a docker network address instead of "immich_server" I moved it to "host networking" and now have this and it's at 3000 no response at 2283

sunbrolynkOP•3/10/23, 1:48 PM

Server log gives the same enotfound but for postgres

sunbrolynkOP•3/10/23, 1:49 PM

Postgres says it's up and ready to accept connections

bo0tzz•3/10/23, 1:49 PM

The postgres error will be the main problem

bo0tzz•3/10/23, 1:49 PM

Sounds like there's probably something wrong in the networking setup

bo0tzz•3/10/23, 1:50 PM

Can you undo the host network stuff and go back to the default setup?

sunbrolynkOP•3/10/23, 1:51 PM

I can, but not till this afternoon currently. And as I said it gave the same error on 2283 but with a docker network address instead of immich_server

sunbrolynkOP•3/10/23, 3:24 PM

I have some extra time right now so giving it a shot. I should be accessing it at http://<server-ip>:2283 correct?

jrasm91•3/10/23, 3:24 PM

Yeah.

jrasm91•3/10/23, 3:25 PM

But you should probably look at the logs for the server and postgres

sunbrolynkOP•3/10/23, 3:25 PM

Will do

sunbrolynkOP•3/10/23, 3:26 PM

sunbrolynkOP•3/10/23, 3:26 PM

Both logs show good to go.

sunbrolynkOP•3/10/23, 3:27 PM

Postgres shows no errors and says ready to accept incoming connections

sunbrolynkOP•3/10/23, 3:27 PM

Server shows no errors and says machine learning enabled as last comment

sunbrolynkOP•3/10/23, 3:27 PM

Right above days listening on port 3001

sunbrolynkOP•3/10/23, 3:28 PM

Wierd now it's up

sunbrolynkOP•3/10/23, 3:29 PM

Maybe i just tried too soon, not sure why it wasn't working previously though. I had kt running for about 24 hours before trying host

sunbrolynkOP•3/10/23, 3:31 PM

All good now. Thanks you!