stuck at "sign up"
Hello-
Using the portainer instructions and followed the set up, including replacing all .env with stack.env, was able to reach initial "sign up" page and upon entering info and clicking to continue, nothing happens.
env:
DB_HOSTNAME=immich_postgres
DB_USERNAME=postgres
DB_PASSWORD=postgres
DB_DATABASE_NAME=immich
REDIS_HOSTNAME=immich_redis
UPLOAD_LOCATION=/share/Docker/Immich/Upload
PUBLIC_LOGIN_PAGE_MESSAGE=Welcome!
IMMICH_WEB_URL=http://immich-web:3000
IMMICH_SERVER_URL=http://immich-server:3001
IMMICH_MACHINE_LEARNING_URL=http://immich-machine-learning:3003
Thanks for any help!
27 Replies
What is the log on the server?
Here it is...
Hmm maybe try these three
without the final forward slash
/
I don't see anything wrong with the setupSweet - that did it. Thank you!
Hmm good to know, first instance of this 🤔
Thank you for reporting
I'll report back any other issues...I'm learning as I go 🙂
No problem, let me know if you run into any strange
I attempted to redeploy my stack (pulling the latest update), updated the app and now I can't log in again.
Bring down the stack and bring it up again
shoot - I scrapped the whole thing and started over from scratch...it's still not even bringing up the initial sign up/login.
Can you provide the logs of the server? It would be hard to trouble shoot if the only datapoint we have is “it’s broken” 😝
fair point - thanks for the reminer 🙂
Server seems fine, could be an issue with your proxy setup?
It isn't providing any logs, what information would be important to review?
What is your proxy setup looks like?
I'm going to guess this is what you are looking for:
No I mean do you have any other proxy setup besides the one included in the application?
I do have other containers, but I don't have any other proxy containers set up. My published ports are unique to each container.
Can you post your current Immich setup?
Do you mean these?
Can you provide the exact value you use for Portainer and .env file? of course please redact any secrect
after you pull the new version, have you perform
docker-compose down then docker-compose up again?I'm sorry for my ignorance, what do you mean by "exact value"?
Can you capture the screenshot of your portainer setup?
Also can you try to bring down and whole stack and bring it back up again. Sometimes pulling without bring down and bring up the stack can cause issue because of the state of the container might not be restarting proberly
😀
Well, stay tuned. I couldn't get the stack to stop (it would populate several errors), so I just restarted my NAS (twice), then stopped and restarted the stack (successfully) and now I'm logged in.
Yeah I think the problem was the image was pull but the stack wasn’t restarted properly 😅
Im glad it works!
when all else fails - turn it off and back on again!
Thanks for your patience and help!
No problem!