[SOLVED] Update scheitert: Connection refused bzw Network is unreachable

[whiterabbit]

Hallo. Seit heute bekomme ich seltsamerweise beim Update des Systems nur noch Fehlermeldungen:

()
starting apt-get update
Err:2 http://ftp.de.debian.org/debian bullseye InRelease
  Could not connect to ftp.de.debian.org:80 (141.76.2.4). - connect (111: Connection refused)
Err:3 http://ftp.de.debian.org/debian bullseye-updates InRelease
  Unable to connect to ftp.de.debian.org:http:
Err:4 http://security.debian.org bullseye-security InRelease
  Could not connect to debian.map.fastlydns.net:80 (199.232.138.132). - connect (111: Connection refused) Cannot initiate the connection to debian.map.fastlydns.net:80 (2a04:4e42:65::644). - connect (101: Network is unreachable) Could not connect to security.debian.org:80 (151.101.66.132). - connect (111: Connection refused) Cannot initiate the connection to security.debian.org:80 (2a04:4e42:200::644). - connect (101: Network is unreachable) Could not connect to security.debian.org:80 (151.101.2.132). - connect (111: Connection refused) 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.130.132). - connect (111: Connection refused) Cannot initiate the connection to security.debian.org:80 (2a04:4e42:600::644). - connect (101: Network is unreachable) Could not connect to security.debian.org:80 (151.101.194.132). - connect (111: Connection refused) Cannot initiate the connection to security.debian.org:80 (2a04:4e42:400::644). - connect (101: Network is unreachable)
Err:5 http://download.proxmox.com/debian/pve bullseye InRelease
  Could not connect to download.proxmox.com:80 (212.224.123.70). - connect (111: Connection refused) Cannot initiate the connection to download.proxmox.com:80 (2a01:7e0:0:424::249). - connect (101: Network is unreachable)
Reading package lists...
[...]
TASK OK

Was ist da los? Ein ping z.B. auf security.debian.org kommt problemlos an.
Der Server hat nur ein einziges Interface bzw nur eine vmbr0. Es ist ein aktuelles Proxmox 7.1.10

Spoiler: pveversion -v

pveversion -v
proxmox-ve: 7.1-1 (running kernel: 5.13.19-4-pve)
pve-manager: 7.1-10 (running version: 7.1-10/6ddebafe)
pve-kernel-helper: 7.1-10
pve-kernel-5.13: 7.1-7
pve-kernel-5.11: 7.0-10
pve-kernel-5.13.19-4-pve: 5.13.19-9
pve-kernel-5.13.19-3-pve: 5.13.19-7
pve-kernel-5.11.22-7-pve: 5.11.22-12
pve-kernel-5.11.22-4-pve: 5.11.22-9
ceph-fuse: 15.2.14-pve1
corosync: 3.1.5-pve2
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.22-pve2
libproxmox-acme-perl: 1.4.1
libproxmox-backup-qemu0: 1.2.0-1
libpve-access-control: 7.1-6
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.1-2
libpve-guest-common-perl: 4.0-3
libpve-http-server-perl: 4.1-1
libpve-storage-perl: 7.1-1
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 4.0.11-1
lxcfs: 4.0.11-pve1
novnc-pve: 1.3.0-1
proxmox-backup-client: 2.1.5-1
proxmox-backup-file-restore: 2.1.5-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.4-5
pve-cluster: 7.1-3
pve-container: 4.1-3
pve-docs: 7.1-2
pve-edk2-firmware: 3.20210831-2
pve-firewall: 4.2-5
pve-firmware: 3.3-5
pve-ha-manager: 3.3-3
pve-i18n: 2.6-2
pve-qemu-kvm: 6.1.1-1
pve-xtermjs: 4.16.0-1
qemu-server: 7.1-4
smartmontools: 7.2-1
spiceterm: 3.2-2
swtpm: 0.7.0~rc1+2
vncterm: 1.7-1
zfsutils-linux: 2.1.2-pve1

Hat jemand eine gute Idee?
Danke!

 

[whiterabbit]

Das Problem ist gelöst ... es lag nicht am Proxmox sondern an der Firewall, die vollgelaufen war ...
[solved]