Proxmox + Immich + Debian 12 VM - Immich becomes unreachable
Hey All!
I am trying to install the latest Immich with default docker compose and .env files on a debian 12 VM hosted on proxmox. I am able to get the service to launch and work, but after 5-10 min the service is unreachable from another host. But if i curl 127.0.0.1:2283 i am able to get index.html. I have completly turned off my firewall, reinstalled 3 seperate times on full new VMs same symptoms. No errors in the logs, and the services appear to all be functional. Just not accessible from another host. If i reboot the immich docker instance I will regain access from an external host for 5-10m and then it does it again
18 Replies
:wave: Hey @zire720,
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.Troubleshooting
Installed 3 different VMs
Ensured IPv4 routing was working
flushed all firewall rules
Added host info to .env
Downgraded versions
Changed where it looked for postgres
Worked with AI to validate Permissions on files
Changed interfaces from paravirtualized, e1000, and e1000e
Validated VM RAM and CPU against reqs
Watched all logs for any errors
Immich version 1.38 and 1.39.4
Proxmox 8.11
Debian 12 VM
8 CPU Cores 16GB RAM
e1000e virtual nic
Successfully submitted, a tag has been added to inform contributors. :white_check_mark:
Hello. this is likely a firewall or networking related issue
as you say you can still reach the container locally there is nothing wrong with the immich instance
I think you are focused on issues within the VM I would search for further issues such as on your LAN or the hypervisor.
There are 26 other VMS running on that proxmox. I uninstalled ufw and flushed up tables.
Additionally why was I able to access immich just fine for 5-10 min then it goes away
Seems strange if it's just a firewall rule
It could be a lot of things other than just a firewall, but since it works local to the VM that confirms that immich is working IMO
We don’t have any ip based auth or restrictions
Easily could be a firewall policy that’s getting set then purged, or a rule that’s allowing ESTABLISHED traffic
Or something else entirely
I guess the next step would be to confirm the immich homepage actually loads in that VM. So you’d need a browser for that
You could also check the logs
if it’s just curl that might not mean the instance is alive
It also works from another host though. But only for 5-10 min.
I literally change nothing
I can get to the admin initial setup page from an external host but only for 5-10m. After that only localhost can
Yes it's the full page based on the text. Can get a full index.html on localhost anytime, an external host only 5-10m
The page doesnt tell you much because its not necessarily loading the timeline. Its client side rendered
If I shutdown docker I can't pull the html anymore
Yep, thats normal
Ok I'm confused as to your goal with this statement
I guess if you cant even pull the index from another host thats info enough, but just pulling the index doesnt fully confirm immich is working
Either way, the html not loading from another client, really there is no way that immich could cause that, sorry
I have never heard of that being a thing and we have no mechanism for that in our code
Brand new VM only followed your install guide
Literally everything else works including my snmp config
Idk what to tell you mate
unless you can provide some actual logs or evidence with an issue in immich I am not sure what you expect us to be able to do
the fact that it works locally basically completely rules out an issue with immich. I understand you have other VMs but somethign must be different here
Literally nothing VMs are built via IAC with terraform. And only immich is unavailable
Any other logs I can pull
@zire720 check the bot post, within the VM you can use
docker compose logs for instance