Immich remote IP not working
I have installed Immich using the Docker Compose method presented on the website, following every step as instructed. I have been able to start my server successfully on my home device, and can access the server by using "sudo docker inspect immich_server" in Terminal to determine the Docker Container's local IP address, then entering the following into a web browser: "http://<container local IP address>:2283". I can then use the instructions from the website's Quick Start- Try the Web UI section to complete my admin registration. However, I have been unable to access my server via "http://<device IP address>:2283/api", on either my mobile app or web browsers on my home device. I have tried killing the created server and re-creating it, to no avail. Any help to determine my problem is appreciated.
Info:
Home device OS: Ubuntu 24.04.1 LTS
Mobile device OS: GrapheneOS build number 2024121200
Immich version: v1.123.0 on both devices
docker-compose.yml , .env, and all log files attached
6 Replies
:wave: Hey @Skye,
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. :ballot_box_with_check: verified I'm on the latest release(note that mobile app releases may take some time).
2. :ballot_box_with_check: read applicable release notes.
3. :ballot_box_with_check: reviewed the FAQs for known issues.
4. :ballot_box_with_check: reviewed Github for known issues.
5. :ballot_box_with_check: tried accessing Immich via local ip (without a custom reverse proxy).
6. :ballot_box_with_check: uploaded the relevant information (see below).
7. :ballot_box_with_check: 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.
Successfully submitted, a tag has been added to inform contributors. :white_check_mark:To clarify - you can reach Immich from the machine it's running on, but not from others?
Check the host's firewall and make sure it's allowing access to port 2283
please post lots of screenshots of the exact IPs you are trying and from what device
@purplealien please open your own thread
Alright I fixed the issue. Here's what I did, for future reference if people experience something similar:
-used "sudo ufw enable" and "sudo ufw allow 2283" to enable that port
-used "hostname -I" to get my IP address from my command line, which was different from the IP address I got when using online IP finder tools.
I hadn't tried either of these. Thank you for your prompt assistance!
This thread has been closed. To re-open, use the button below.