Cannot start immich on Asustor NAS
Hello everyone,
I want to run immich on my Asustor LOCKERSTOR 6 Gen2 (AS6706T) NAS.
First it seemed like there is an issue with typesense, so I disabled typsense in the .env file and deleted the container from the docker-compose.yml.
When I start the container, I get some error messages about the duplicate key. I was posting that already in reddit:
https://www.reddit.com/r/immich/comments/14s7nzc/cannot_get_immich_started_due_to_docker/
I attached my docker-compose and my env file
Thank you and best regards
59 Replies
Hello, can you try
docker-compose down -vunknown shorthand flag: 'V' in -V
and then docker-compose up
sorry lowercase
-v
And restore the original docker-compose file except the typesense container that get commented out if you canI will do original docker-compose file and in the .env I will set TYPESENSE_ENABLED=false
yes and commented out Typesense if fine as well
Get the same error message
what is the log of the server container?
immich_server
now access the web
Wanted to access over:
http://192.168.1.100:2283/
No website shows:
Hmmm… can't reach this page 192.168.1.100 took too long to respond
immich_web shows:
Listening on 0.0.0.0:3000
that is internal port
the proxy is mapped to port 2283 so the traffic is routed correctly between the containers
what is your output of
docker psdocker ps
can you
curl http://your-ip:2283Are there 2 containers running?
the entry point is different for that image
OK
curl takes forever
hmm which mean it cannot reach the proxy
Works with 127.0.0.1
with the port?
yes
can you show the result?
perhaps you have firewall that blocks port 2283
I'm not aware of any firewall. I have only Traefik, but now I'm accessing local, so that shouldn't interfere
I could try another port
yeah try use a different port than 2283
Same result, with 127.0.0.1 it works with 192.168.1.100 it doesn't
pretty strange there
can you do
ip -c aAt least I'm not the only one who finds that strange 😅
Is the syntax correct?
It doesn't show
maybe
ipconfigip a works:
yeah it looks correct with
192.168.1.100
I am not sure what happened hereI'm pretty sure it's the Asustor NAS, they have some weird stuff 😅
which port did you change from 2283 to?
36346:8080
Totally random
try 52283
I will try
That's something different now:
immich_postgres still has the same error:
ok so you can access it now
what is your current docker-compose file?
Yes, now I can access.
Docker-compose is the original from github with changed port to 52283:8080
I still don't understand why port 52283 suddenly works, but thank you so much!
We are still haveing issue with the database thought, right?
I think Ausustor might have blocked a certain range of the ports
Yes, the immich_postgres still returns the following logs:
what is your current docker-compose file looks like?
docker-compose looks like this:
What is funny, I changed the compose (added volume immich_redis_data for redis), after I started I cannot reach immich anymore. Changed it back to the old version, same behavior. So it seems a little random that we could access before
try to use the original docker compose and just remove typesense
then perform
docker-compose down -v to remove all containers and volume that associated with this docker-compose file
then perform docker-compose pull and docker-compose up againAnd change the port to 52283?
yes
Did that, website doesn't return anything at http://192.168.1.100:52283 but returns immich at http://127.0.0.1:52283
what is
http://192.168.1.100:52283/api/server-info?immich_postgres has the following logs
Nothing either
I think as long as the server can connect to the database that should be fine
how about using 127.0.0.1?
root@myServer:/volume1/Docker/immich # curl http://127.0.0.1:52283/api/server-info
{"statusCode":401,"message":"Authentication required","error":"Unauthorized"}
ah so it can hit the server and the server can run just fine
you will have to figure out what happened with ausustor
>.<
How am I doing that? Ticket at Asustor?
probably
OK, thank you very much Alex. I will get in touch with Asustor
I always thought docker is docker, but makes sense that the host system can interfere