How to update immich through portainer in proxmox
I'm having trouble updating to latest immich with portainer something about no route to host. Am i missing a setup or something?
58 Replies
Er
No route to host
Are u sure your DNS IS okay ?
Wdym
It's in my local home server
Looks like a network failure. Does it continue to happen now if you try it again? Can you access https://ghcr.io/v2 (404 page) on another machine on the same network? Can you access it from the portainer machine via curl, wget, etc.?
Yes but from this server, like says jrasm, Can you Access internet ?
What is the reply of
curl https://ghcr.io/ ?On my phone I see the 404 page
Let me try in a sec
@Onelots.
UH
Do you have some firewall preventing connection from the container?
What OS are you running this on?
also if no firewall on the machine I would run a "traceroute google.com" and "traceroute 8.8.8.8" and see how far you are getting, its either something wrong with your network or your DNS
if your traceroute makes it to 8.8.8.8 but not google.com you probably have a DNS issue, if the traceroute cant make it to either definitely a networking/firewall issue
I think Debian
I also used this script if that helps https://tteck.github.io/Proxmox/
Proxmox VE Helper Scripts | Scripts for Streamlining Your Homelab w...
Scripts for Streamlining Your Homelab with Proxmox VE
oh yeah and for windows the command is tracert lol
do you have portainer running in a VM or LXC container?
or on the PVE host itself
lxc
is it easier to run in a vm
yes I run my docker environment in a VM for that reason, and OOF 3000+ ms to your first hop is very bad
so looks like networking
hmm is it cuz its in an lxc? my home server is wired with the router
and that traceroute was from within LXC itself?
or was it from the docker container?
cause if docker.local is pointing to the IP of the LXC container itself, it is looping or has a bad gateway it looks like, itself should not be a hop
yea in the lxc container that has docker portainer stuff
hmm, what is result of "ip route" command
this?
so assuming 192.168.1.1 is your router, the default gateway looks normal, what looks super interesting to me is the route for 192.168.0.0/15, as this looks incorrect for me cause the largest possible space for the 192.168 private IP subnetwork is 192.168.0.0/16, so /15 is possibly including random public IPs
so I am not sure if that would actually break anything as you can see here it would includie 192.169.0.0/16 as well by adding the /15, which is technnically not correct from what I understand
ahh that is why, is there a reason you need /15?
I was following a youtube tutorial
so should it be /16 ?
change that to /16, which technically it doesnt even have to be that big, if you connect to other VPN gateways or stuff like that ever using the whole /16 could probably break that
my bet would be your actual subnet size/netmask for your LAN network is more like 191.168.1.0/24, which is 192.168.1.1-192.168.1.254
updated
nice networking is weird and that could possibly help with whatever was going on, if you have a windows computer connected to the same router you can find out what your subnet/netmask actually is using ipconfig command
this part?
this is what mine looks like, the subnet mask 255.255.255.0 translates to /24 so I would set 192.168.88.100/24 as an LXC IP
did i mess up setting up proxmox?
yessir
so everything you have configured as a /15, I myself personally would change to /24
oh from 16 to 24 then
also try setting your container to /24 just to test for now
yes it is possible having a broken route due to the /15 and subnet not matching your routers network is breaking connectivity for your container
and depending on what kind of router you are using you can log in and configure this subnet as well but most people do use /24 subnets which translates to 255.255.255.0 subnet mask
alright changed it
now to test
ping google.com
curl https://ghcr.io/
GitHub
GitHub Packages: Your packages, at home with their code
With GitHub Packages you can safely publish and consume packages within your organization or with the entire world.
same issue 😦
i see this
maybe il lreboot
dang, and that is interesting, maybe ipv6 is working and ipv4 is not?
yes reboot would be good to try lol
also make sure you can ping 192.168.1.1 since that is your gateway
lol your issue could be directly illustrating how ipv6 basically eliminates NAT issues, since every device in the world can have a unique ip with ipv6
uh
so that would be the root cause of the issue here, if you can regain connectivity with your gateway it will solve the issue
what is NAT. I'm not really tech savy in networking
is it possible another device in your network could have gotten a IP from your router that is the same?
which would be an ip conflict
Network Address Translation, it is the main way IPV4 addressed devices can communicate with the internet/outside networks
should i just change it the url then?
it can get very complicated lol
do the command
traceroute 192.168.1.1
just to see what it shows
hmm so its going the right direction, it should be hitting 192.168.1.1 using its .182 IP, I do know the 3000ms thing is basically the packets are looping within the device since they cant get out and then timing out around 3000ms
i guess make sure your proxmox host network settings are correct as well
I wouldnt have thought that would affect the containers/VMs though since it is a bridge
but worth making sure its correct to your router/gateway settings
subnet mask 255.255.255.0 = /24 at end is really all you gotta remember lol
dont worry abut the networking jargon, subnet mask is a fancy way of saying the size of a network (what range of IPs?)
aha, so is your router/gateway actually 192.168.1.254? (last IP of the /24 range instead of first, sometimes it is configured this way)
you can check using ipconfig from your windows machine but I am willing to bet it is
yeah if your proxmox has internet and all that but that container does not, you should change gateway to 192.168.1.254
oh
til
curl isnt showing an error anymore
thanks so much @ProCloudSurfer
updated immich now
hooray!! np glad to hear
wellp til my actually gateway
@ProCloudSurfer so on your setup, u run immich through docker too?
sorry just saw this, yes running immich using a plain old docker compose file, I do use portainer for a nice GUI view of everything but configuring text file for the docker compose felt like the easiest way with immich's multi container setup
It's better to use portainer only to monitor or have a pretty gui
But the best practice is to use docker compose
