33 Replies
:wave: Hey @idontknow,
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.What are you seeing?
Spinner icon?
not reachable
Check the server logs
all good from what i can see
Looks good
Aee you sure the ip is correct?
yep
What system are you running on?
lxc ubuntu in proxmox
Can you run ip -c a?
Then confirm the container ip?
in portainer the ip is "172.18.0.6"
FYI I had the same ML learning issue like everyone else, so I updated the stack, and updates the images for both ML and Sever
idk if that makes any difference or not
what address do you put in on the browser?
should be
http://10.71.30.136:2283http://10.71.30.136:2283/can you ping 10.71.30.136 from your machine?
yep
even tried to ssh just now to be safe
what is your docker-compose.yml looks like?
used the default from the immich
noticed the redis, and db image is different from the latest now, but that should be fine i am guessing
wrong port
need to be 2283:2283
it changes a while back
wtf, it was working for 1.130.3 lol
are you sure you are in the correct folder? lol
pulled straight from portainer
i updated now to 2283, but I swear it was working this morning haha
doesn't sound right man =))
you should check your system
Version History
Installed 1.131.3 on Apr 1, 2025
Installed 1.130.3 on Mar 30, 2025
not joking lol
portainer maybe pulling April 1st prank on ya
bruh -_-, i even tried to restore my lxc image backup 2x
any who, it is working, appreciate the help
no problem