Help with apt update on Proxmox Host

schancksb

New Member
Dec 24, 2021
2
0
1
25
Chile
Hey everyone, I'm having some issues while trying to update my proxmox host, everytime I run sudo apt update from the cli (SSH) I get this error message.

Code:
Err:1 http://download.proxmox.com/debian/pve bullseye InRelease                                                                                                                           
  Cannot initiate the connection to download.proxmox.com:80 (2607:5300:203:7dc2::162). - connect (101: Network is unreachable) Could not connect to download.proxmox.com:80 (144.217.225.162). - connect (113: No route to host)
Err:2 http://deb.debian.org/debian bullseye InRelease                                                                                                                                     
  Cannot initiate the connection to debian.map.fastlydns.net:80 (2a04:4e42:33::644). - connect (101: Network is unreachable) Could not connect to debian.map.fastlydns.net:80 (151.101.218.132). - connect (113: No route to host) Cannot initiate the connection to deb.debian.org:80 (2a04:4e42:5c::644). - connect (101: Network is unreachable) Could not connect to deb.debian.org:80 (199.232.114.132). - connect (113: No route to host)
Ign:3 http://deb.debian.org/debian bullseye-updates InRelease                                                 
Err:4 http://security.debian.org bullseye-security InRelease
  Cannot initiate the connection to debian.map.fastlydns.net:80 (2a04:4e42:33::644). - connect (101: Network is unreachable) Could not connect to debian.map.fastlydns.net:80 (151.101.218.132). - connect (113: No route to host) 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 (2a04:4e42::644). - 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 (2a04:4e42:400::644). - connect (101: Network is unreachable) Could not connect to security.debian.org:80 (151.101.66.132). - connect (113: No route to host) Could not connect to security.debian.org:80 (151.101.130.132). - connect (113: No route to host) Could not connect to security.debian.org:80 (151.101.194.132). - connect (113: No route to host) Could not connect to security.debian.org:80 (151.101.2.132). - connect (113: No route to host)
Err:5 http://deb.debian.org/debian bullseye-updates Release
  Cannot initiate the connection to deb.debian.org:80 (2a04:4e42:5c::644). - connect (101: Network is unreachable)
Reading package lists... Done
E: The repository 'http://deb.debian.org/debian bullseye-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.

From the web UI (node/updates/refresh) a similar one:
Code:
starting apt-get update
Err:1 http://download.proxmox.com/debian/pve bullseye InRelease
  Cannot initiate the connection to download.proxmox.com:80 (2607:5300:203:7dc2::162). - connect (101: Network is unreachable) Could not connect to download.proxmox.com:80 (144.217.225.162). - connect (113: No route to host)
Ign:2 http://deb.debian.org/debian bullseye InRelease
Ign:3 http://deb.debian.org/debian bullseye-updates InRelease
Err:4 http://deb.debian.org/debian bullseye Release
  Cannot initiate the connection to deb.debian.org:80 (2a04:4e42:33::644). - connect (101: Network is unreachable)
Err:5 http://deb.debian.org/debian bullseye-updates Release
  Cannot initiate the connection to deb.debian.org:80 (2a04:4e42:33::644). - connect (101: Network is unreachable)
Err:6 http://security.debian.org bullseye-security InRelease
  Cannot initiate the connection to debian.map.fastlydns.net:80 (2a04:4e42:33::644). - connect (101: Network is unreachable) Could not connect to debian.map.fastlydns.net:80 (151.101.218.132). - connect (113: No route to host) 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 (2a04:4e42:400::644). - 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 (2a04:4e42::644). - connect (101: Network is unreachable) Could not connect to security.debian.org:80 (151.101.194.132). - connect (113: No route to host) Could not connect to security.debian.org:80 (151.101.2.132). - connect (113: No route to host) Could not connect to security.debian.org:80 (151.101.66.132). - connect (113: No route to host) Could not connect to security.debian.org:80 (151.101.130.132). - connect (113: No route to host)
Reading package lists...
E: The repository 'http://deb.debian.org/debian bullseye Release' no longer has a Release file.
E: The repository 'http://deb.debian.org/debian bullseye-updates Release' no longer has a Release file.
TASK ERROR: command 'apt-get update' failed: exit code 100
It seems like the host does not have internet access since pinging any website or public IP gets an Destination host unreachable error. But it can ping local IP's and I can access it through SSH.
The weird thing is that every VM and container runing on Proxmox has internet access, and I've tried a lot of things from different post in this forum, and honestly I don't know what to try next.
It's important to note that the firewall is disabled at a datacenter level (and node level as well)
I'll leave the output of cat /etc/network/interfaces, cat /etc/apt/sources.list and a few screenshots:

cat /etc/network/interfaces
Code:
# network interface settings; autogenerated
# Please do NOT modify this file directly, unless you know what
# you're doing.
#
# If you want to manage parts of the network configuration manually,
# please utilize the 'source' or 'source-directory' directives to do
# so.
# PVE will preserve these directives, but will NOT read its network
# configuration from sourced files, so do not attempt to move any of
# the PVE managed interfaces into external files!

auto lo
iface lo inet loopback

auto enp3s0
iface enp3s0 inet manual
        gateway 192.168.100.1

auto vmbr0
iface vmbr0 inet static
        address 192.168.100.201/24
        bridge-ports enp3s0
        bridge-stp off
        bridge-fd 0

cat /etc/apt/sources.list
Code:
deb http://deb.debian.org/debian bullseye main contrib

deb http://deb.debian.org/debian bullseye-updates main contrib

# security updates
deb http://security.debian.org bullseye-security main contrib

deb http://download.proxmox.com/debian/pve bullseye pve-no-subscription

Network config Proxmox Web UI
1642973424836.png

Repositories Proxmox Web UI
1642973482886.png
I'll remain attentive to any question about my setup and/or issue.
Thanks everyone for your time and help.
Best regards
 
Your network config should look like this (so gateway to vmbr0 and not your NIC):
Code:
auto lo
iface lo inet loopback

auto enp3s0
iface enp3s0 inet manual

auto vmbr0
iface vmbr0 inet static
        address 192.168.100.201/24
        gateway 192.168.100.1
        bridge-ports enp3s0
        bridge-stp off
        bridge-fd 0
 
Last edited:
  • Like
Reactions: Quincicle
Your network config should look like this (so gateway to vmbr0 and not your NIC):
Code:
auto lo
iface lo inet loopback

auto enp3s0
iface enp3s0 inet manual

auto vmbr0
iface vmbr0 inet static
        address 192.168.100.201/24
        gateway 192.168.100.1
        bridge-ports enp3s0
        bridge-stp off
        bridge-fd 0
Thanks a lot, this solved the issue, I've been banging me head a lot lately trying to figure this one out, and it was that easy haha. Thanks again
 
Your network config should look like this (so gateway to vmbr0 and not your NIC):
Code:
auto lo
iface lo inet loopback

auto enp3s0
iface enp3s0 inet manual

auto vmbr0
iface vmbr0 inet static
        address 192.168.100.201/24
        gateway 192.168.100.1
        bridge-ports enp3s0
        bridge-stp off
        bridge-fd 0
Hi Dunuin,
I followed your post and with the network configuration Proxmox image given by @schanckbs the problem was solved for me today.

Kind regards,
 
  • Like
Reactions: Dunuin

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!