Immich ServerEndpoint Error
So i am hosting Immich on Windows via Rancher Desktop (Basically Uses WSL) and it is running properly when i am accessing it from Host Machine. I tried connecting to it via my android device by using http://host-machine-ip:2283 but it waits for few seconds and then give
Server is Not Reachable
Error and Also tried accessing via browser on mobile but didn't worked.
My Compose and .env files are Defaults (Timezone changed to Asia/Kolkata)
My Wifi Network worked with Plex Media server before but not this time
21 Replies
:wave: Hey @Jaggu762,
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.Hi, this is probably due to a windows firewall issue or similar. Not related to immich
I asked ChatGPT it also asked me this and gave command to allow 2283 port
Yeah most of us have no idea about windows networking or firewall.
Might need to do some googling etc
ok
so should i let the ticket open for now
that's actually correct
You can, someone might have an idea,
you have to map a local host port with a wsl port to be able to access it over the network. and that's what that command do
Netsh commands for interface portproxy
Use the netsh interface portproxy commands to act as proxies between IPv4 and IPv6 networks and applications.
so the command i gave above its the same i think
...
connectaddress should be your wsl IP tho
ok
not 127.0.0.1
thx
btw
I upload many files to Immich
about 2k
and its filling up ram
so what to do?

most probably is just cached ram, it shouldn't be a problem, check your windows task manager details.
you can limit the memory a container can use, but I don't think it's necessary
so files are stored and its just cached to give faster experience?
and after restart it will be normal
no, files are stored on disk, cached ram is used by the OS to reduce swapping and speed up access time. it's released when needed
thanks for the help
it completed
SOLVED
This thread has been closed. To re-open, use the button below.