[SOLVED] Unable to update Proxmox: "Network is unrechable" despite the web gui still being accessible

O

Oa4McvMTSo

New Member
Mar 2, 2026
6
0
1
My Proxmox server was mistakenly restarted over the weekend so I decided to take the opportunity to update the system. Unfortunately, I got this error as a response:


Code: 
TASK ERROR: command 'apt-get update' failed: exit code 100


Dropping into a shell, I tried to manually update the server and got this as output:

Code: 
Ign:1 http://deb.debian.org/debian bookworm InRelease
Ign:2 http://deb.debian.org/debian bookworm-updates InRelease
Err:3 http://deb.debian.org/debian bookworm Release
  Cannot initiate the connection to deb.debian.org:80 (2a04:4e42:d::644). - connect (101: Network is unreachable) Cannot initiate the connection to deb.debian.org:80 (146.75.126.132). - connect (101: Network is unreachable)
Err:4 http://deb.debian.org/debian bookworm-updates Release
  Cannot initiate the connection to deb.debian.org:80 (2a04:4e42:d::644). - connect (101: Network is unreachable) Cannot initiate the connection to deb.debian.org:80 (146.75.126.132). - connect (101: Network is unreachable)
Ign:5 http://security.debian.org/debian-security bookworm-security InRelease
Err:6 http://security.debian.org/debian-security bookworm-security Release
  Cannot initiate the connection to security.debian.org:80 (2a04:4e42:600::644). - connect (101: Network is unreachable) Cannot initiate the connection to security.debian.org:80 (151.101.66.132). - connect (101: Network is unreachable) Cannot initiate the connection to security.debian.org:80 (2a04:4e42:200::644). - connect (101: Network is unreachable) Cannot initiate the connection to security.debian.org:80 (151.101.130.132). - connect (101: Network is unreachable) Cannot initiate the connection to security.debian.org:80 (2a04:4e42::644). - connect (101: Network is unreachable) Cannot initiate the connection to security.debian.org:80 (151.101.2.132). - connect (101: Network is unreachable) Cannot initiate the connection to security.debian.org:80 (2a04:4e42:400::644). - connect (101: Network is unreachable) Cannot initiate the connection to security.debian.org:80 (151.101.194.132). - connect (101: Network is unreachable)
Ign:7 http://download.proxmox.com/debian/pve bookworm InRelease
Err:8 http://download.proxmox.com/debian/pve bookworm Release
  Cannot initiate the connection to download.proxmox.com:80 (2607:5300:400:7d00::80). - connect (101: Network is unreachable) Cannot initiate the connection to download.proxmox.com:80 (170.130.165.90). - connect (101: Network is unreachable)
Reading package lists... Done
E: The repository 'http://deb.debian.org/debian bookworm Release' no longer has a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
E: The repository 'http://deb.debian.org/debian bookworm-updates Release' no longer has a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
E: The repository 'http://security.debian.org/debian-security bookworm-security Release' no longer has a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
E: The repository 'http://download.proxmox.com/debian/pve bookworm Release' no longer has a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.


Trying to use `ping` on external IP addresses or domains is also giving me the network unreachable error, however I can ping the gateway successfully. I can also use `dig` to correctly resolve external domains.

None of the other devices on the same subnet are having issues pinging inside or outside the network, so this is not a firewall issue.

This looks like a DNS issue, but the dig output implies otherwise. What is going on here?
 
Last edited:
so I don't think this is a DNS issue anymore. VMs on the Proxmox machine can pull an IP from the gateway, but I cannot access them from other machines on the same subnet.
 
Could this be related to your issue?
M

[SOLVED] Post in thread 'apt update is not working'

Thank you for the warm welcome!
Thanks to @bbgeek17 @fabian for pointing out the MITM attack. I asked chatgpt about using a VPN, he said that I would need to change the connection so that all traffic goes through the VPN, but then I would lose SSH access and the web dashboard. So I don't understand what to do.

Thanks to @fstrankowski, I tried to use, and It didn't help me :(
Code: 
sudo find /etc/apt/sources.list.d/ -maxdepth 1 -type f -name '*.sources' \
-exec sed -i.bak 's/download\.proxmox\.com/185.219.221.167/g' {} +

The script gives me this:
Code: 
root@pve:~# bash...

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
 
alexskysilk said:
to make permanent, echo "add Acquire::ForceIPv4 true"
Click to expand...
Without "add", right?

I have this on some of my machines:
Code: 
~# cat /etc/apt/apt.conf.d/99force-ipv4
Acquire::ForceIPv4 "true";
 
  • Like
Reactions: alexskysilk
bbgeek17 said:
Could this be related to your issue?
M

[SOLVED] Post in thread 'apt update is not working'

Thank you for the warm welcome!
Thanks to @bbgeek17 @fabian for pointing out the MITM attack. I asked chatgpt about using a VPN, he said that I would need to change the connection so that all traffic goes through the VPN, but then I would lose SSH access and the web dashboard. So I don't understand what to do.

Thanks to @fstrankowski, I tried to use, and It didn't help me :(
Code: 
sudo find /etc/apt/sources.list.d/ -maxdepth 1 -type f -name '*.sources' \
-exec sed -i.bak 's/download\.proxmox\.com/185.219.221.167/g' {} +

The script gives me this:
Code: 
root@pve:~# bash...

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
Click to expand...
I don't have my Proxmox server or gateway on a VPN so I don't think so.
 
alexskysilk said:
sudo apt-get -o Acquire::ForceIPv4=true update

to make permanent, echo "add Acquire::ForceIPv4 true" >> /etc/apt/apt.conf.d/99force-ipv4
Click to expand...
I attempted this and got the following output:

Code: 
Ign:1 http://deb.debian.org/debian bookworm InRelease
Ign:2 http://deb.debian.org/debian bookworm-updates InRelease             
Ign:3 http://security.debian.org/debian-security bookworm-security InRelease
Err:4 http://deb.debian.org/debian bookworm Release                       
  Cannot initiate the connection to deb.debian.org:80 (151.101.14.132). - connect (101: Network is unreachable)
Err:5 http://security.debian.org/debian-security bookworm-security Release                 
  Cannot initiate the connection to security.debian.org:80 (151.101.2.132). - connect (101: Network is unreachable) Cannot initiate the connection to security.debian.org:80 (151.101.66.132). - connect (101: Network is unreachable) Cannot initiate the connection to security.debian.org:80 (151.101.194.132). - connect (101: Network is unreachable) Cannot initiate the connection to security.debian.org:80 (151.101.130.132). - connect (101: Network is unreachable)
Err:6 http://deb.debian.org/debian bookworm-updates Release                               
  Cannot initiate the connection to deb.debian.org:80 (151.101.14.132). - connect (101: Network is unreachable)
Ign:7 http://download.proxmox.com/debian/pve bookworm InRelease
Err:8 http://download.proxmox.com/debian/pve bookworm Release
  Cannot initiate the connection to download.proxmox.com:80 (66.70.154.82). - connect (101: Network is unreachable)
Reading package lists... Done
E: The repository 'http://deb.debian.org/debian bookworm Release' no longer has a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
E: The repository 'http://security.debian.org/debian-security bookworm-security Release' no longer has a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
E: The repository 'http://deb.debian.org/debian bookworm-updates Release' no longer has a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
E: The repository 'http://download.proxmox.com/debian/pve bookworm Release' no longer has a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.

so I attempted `apt-get -o Acquire::ForceIPv4=true update --allow-releaseinfo-change` and got basically the same thing:

Code: 
Ign:1 http://security.debian.org/debian-security bookworm-security InRelease
Err:2 http://security.debian.org/debian-security bookworm-security Release     
  Cannot initiate the connection to security.debian.org:80 (151.101.130.132). - connect (101: Network is unreachable) Cannot initiate the connection to security.debian.org:80 (151.101.2.132). - connect (101: Network is unreachable) Cannot initiate the connection to security.debian.org:80 (151.101.66.132). - connect (101: Network is unreachable) Cannot initiate the connection to security.debian.org:80 (151.101.194.132). - connect (101: Network is unreachable)
Ign:3 http://deb.debian.org/debian bookworm InRelease                           
Ign:4 http://deb.debian.org/debian bookworm-updates InRelease                   
Err:5 http://deb.debian.org/debian bookworm Release
  Cannot initiate the connection to deb.debian.org:80 (146.75.126.132). - connect (101: Network is unreachable)
Err:6 http://deb.debian.org/debian bookworm-updates Release
  Cannot initiate the connection to deb.debian.org:80 (146.75.126.132). - connect (101: Network is unreachable)
Ign:7 http://download.proxmox.com/debian/pve bookworm InRelease
Err:8 http://download.proxmox.com/debian/pve bookworm Release
  Cannot initiate the connection to download.proxmox.com:80 (66.70.154.82). - connect (101: Network is unreachable)
Reading package lists... Done
E: The repository 'http://security.debian.org/debian-security bookworm-security Release' no longer has a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
E: The repository 'http://deb.debian.org/debian bookworm Release' no longer has a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
E: The repository 'http://deb.debian.org/debian bookworm-updates Release' no longer has a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
E: The repository 'http://download.proxmox.com/debian/pve bookworm Release' no longer has a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
 
So I solved it: I forgot I had erased the `Gateway` field in the default bridge when doing some testing with different bridges. I went back and manually specified my gateway's IP address, and immediately Proxmox is able to hit external addresses again and is currently updating.

Sorry for putting folks on a wild goose chase! I am curious, however: why can i only specify a gateway for a single bridge?
 
It didn't cross my mind at first because when I first applied the change, there was no obvious change in functionality, and other bridges were still dynamically pulling IP addresses from the gateway without needing it to be manually specified. Restarting the machine made the changes actually populate, I guess?
 
You must log in or register to reply here.
Top Bottom
Back