#Immich is unreachable

1 messages · Page 1 of 1 (latest)

flat thistle
#

Hi! I've set up immich in portainer as described in the installation section (with the port changed). I've opened up the port on my server and using http://<server-ip>:port I can't reach the instance. All the services in the stack are running normally. Here are my compose and env variables:

barren mothBOT
#

:wave: Hey @flat thistle,

Thanks for reaching out to us. Please follow the recommended actions below; this will help us be more effective in our support effort and leave more time for building Immich immich.

References

Checklist

  1. :ballot_box_with_check: I have verified I'm on the latest release(note that mobile app releases may take some time).
  2. :ballot_box_with_check: I have read applicable release notes.
  3. :ballot_box_with_check: I have reviewed the FAQs for known issues.
  4. :ballot_box_with_check: I have reviewed Github for known issues.
  5. :ballot_box_with_check: I have tried accessing Immich via local ip (without a custom reverse proxy).
  6. :ballot_box_with_check: I have uploaded the relevant logs, docker compose, and .env files using the buttons below or the /upload command.
  7. :ballot_box_with_check: I have tried an incognito window, disabled extensions, cleared mobile app cache, logged out and back in, different browsers, etc. as applicable

(an item can be marked as "complete" by reacting with the appropriate number)

If this ticket can be closed you can use the /close command, and re-open it later if needed.

flat thistle
barren mothBOT
split spruce
#

Did you change the postgres password after the datbase had already been spun up once? It says your password is wrong for the postgres user

flat thistle
#

That is what it was... I've removed the pg volume and restarted the stack and it's up and running

#

Thank you!

small monolith
#

Ive been having the same issues as him except the postgres password does not seem to be my issue.

#

I went through all the troubleshooting I could find online but I cant seem to narrow down the issue

#

here are my .env and compose yml

formal bear
#

It seems like you have permission with the location where you put the database

#

my advice is to put the database on the OS drive, not network drive

small monolith
small monolith
#

ok update: just changed the location with the .env file to be on the OS drive, and did sudo docker compose down -v --> sudo systemctl restart docker --> sudo docker compose up -d (in the immich folder)

#

it works

#

thank you so much

#

Im pretty sure this is in FAQ (iirc) but do database files grow over time or not? my OS drive is a tiny 32 gb sd card and its not pentiful compared to the external 4 TB hard drive

formal bear
small monolith
#

thank you so much for your help, Ive been pulling my hairs out trying to figure this issue out for 3 days before finally submitting a ticket

formal bear
#

No problem!