Inaccessible
I've followed the guide to install immich via docker compose however when I navigate to the IP:PORT, it can't be reached. How should I troubleshoot this?
15 Replies
:wave: Hey @DarthVapor,
Thanks for reaching out to us. Please carefully read this message and follow the recommended actions. This will help us be more effective in our support effort and leave more time for building Immich :immich:.
References
- Container Logs:
docker compose logs docs
- Container Status: docker ps -a docs
- Reverse Proxy: https://immich.app/docs/administration/reverse-proxy
- Code Formatting https://support.discord.com/hc/en-us/articles/210298617-Markdown-Text-101-Chat-Formatting-Bold-Italic-Underline#h_01GY0DAKGXDEHE263BCAYEGFJA
Checklist
I have...
1. :blue_square: verified I'm on the latest release(note that mobile app releases may take some time).
2. :blue_square: read applicable release notes.
3. :blue_square: reviewed the FAQs for known issues.
4. :blue_square: reviewed Github for known issues.
5. :blue_square: tried accessing Immich via local ip (without a custom reverse proxy).
6. :blue_square: uploaded the relevant information (see below).
7. :blue_square: 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)
Information
In order to be able to effectively help you, we need you to provide clear information to show what the problem is. The exact details needed vary per case, but here is a list of things to consider:
- Your docker-compose.yml and .env files.
- Logs from all the containers and their status (see above).
- All the troubleshooting steps you've tried so far.
- Any recent changes you've made to Immich or your system.
- Details about your system (both software/OS and hardware).
- Details about your storage (filesystems, type of disks, output of commands like fdisk -l and df -h).
- The version of the Immich server, mobile app, and other relevant pieces.
- Any other information that you think might be relevant.
Please paste files and logs with proper code formatting, and especially avoid blurry screenshots.
Without the right information we can't work out what the problem is. Help us help you ;)
If this ticket can be closed you can use the /close command, and re-open it later if needed.It appears to not be able to connect to the DB in the logs.
Have you actually renamed the example.env file to
.env?Yes
Okay, then please continue sending logs :)
Also, judging by the file system structure I'm guessing you're on unraid? If so, having your db at
/mnt/user/appdata is like a very bad idea
Postgres should absolutely get its own folder
And not just write whereverYes, it's unraid. Are you implying it should be in a folder? I kind of assumed it would create one in there.
You're mounting the postgres
/var/lib/postgresql/data files to /mnt/user/appdata so no, the files will just get dumped in there😦
If you look there I'd assume you have a bunch of random files
Well the good news is it didn't create a bunch of files there. However, I will change that.
Then you haven't even started your db
Or it had permissions isssues to write files, in which case... lucky you!
lol
Well that's correct, in the logs it was saying that it couldn't connect to the DB.
Alright, it finally worked. Not sure what changed. Thanks for the assist.
This thread has been closed. To re-open, use the button below.