Can't connect to web UI for post-install steps
Hi. I've followed Immich's install steps exactly, and the stack seems to deploy correctly, but I'm not getting access to the web application. That is, when I go to 192.168.50.158:2283 (my server's ip address) nothing is found ("Unable to connect.") Strangely, the list of containers in Portainer shows nothing published for anything in docker. (See screenshot.) There was one attempt when I did see a published port for immich_proxy, but after just a couple seconds, the link vanished.
Also, when I try to view the log for immich_proxy, I get an error message saying "Unable to retrieve container logs." But here's the entire log for immich_web:
Listening on 0.0.0.0:3000
FWIW, I'm trying to run it on a raspberry pi 4 w/ 8 gigs of ram.
Attached are my docker-compose.yml, environment.env, and a screenshot of the containers in Portainer. Thanks for any guidance...
(And thanks for patience--I'm new to Docker, Discord, and pretty much everything relevant. 🙂
16 Replies
Also, when I try to view the log for immich_proxy, I get an error message saying "Unable to retrieve container logs."If you remove this section from the proxy service: Then logging should work (and hopefully show an easy to fix error)
Maybe something wrong with Typesense again and not letting the server container start
This is RaspberryPi so I suspect they all have the same issue
K, using your advice, I got logging working for immich_proxy. It keeps repeating the same set of info--maybe it's trying to restart again and again?
Log file attached.
It can't find immich-server, which points to that container also having trouble starting
Ah. Ok. Here's the log for immich_server:
I saw Alex's message about the RPi maybe causing a similar issue to what happened before... Can anyone pls link me to the relevant thread? (Searching for "rpi" here brings up a couple hits, and I'm not sure which is the relevant one.)
That all looks fine, so not sure what's wrong then 🤔
So I located the thread that I think Alex was referencing (https://discord.com/channels/979116623879368755/1088582076133031946) and I disabled machine learning in both docker-compose.yml and environment.env, but that made no difference. If anybody has any ideas for how to tinker with immich_server, I'd love the suggestions! (I'm new and feeling rather blind here...) Thanks.
If the server is up and running and the proxy can't reach it, that would hint at a networking issue. What version of docker and docker compose are you using?
The machine learning container also doesn't have an IP, maybe that is related. Could you add a screenshot from the stack view instead of the containers view?
Docker version 23.0.3, build 3e7cbfd
Docker Compose version v2.17.2
FWIW, I'm running all this with OpenMediaVault--whatever Docker versions go with it are what I've got.
Oh, this stack is the one where I've commented out the machine learning container. (When I include machine learning, it all looks pretty similar--I could redeploy in that configuration and send another screen shot if that'd be helpful.)
Can you look into what network are being used? Is the proxy and the server on the same network?
Hmm.... immich_server is on a network based on the name I assigned the stack ("immich_hdd_test_default") but immich_proxy is not on that network. In fact, the proxy doesn't appear to be on any network.
Would that be a problem with my stack deployment, or is that likely a bigger problem with my overall Docker installation/configuration?
I have no idea, it is pretty strange. You can manually add it, or delete and recreate the stack to try to fix it.
I manually added immich_proxy to the same network as the other containers, and that action briefly gave the proxy a link in the "Published Ports" column. But when I tried loading the link, it didn't work, and within a minute, that link had vanished. Weird.
I think I'll just try blowing up the whole thing and starting from scratch...