Proxmox VE 7.1 released!

VR_Architect

New Member
Dec 13, 2021
12
1
1
55
Hi,

as you can see in the log, it is trying to fetch the correct file (APT is able to figure it out ;)), and the message indicates a connection error. Can you ping the IP/download the file manually?

Thank you for the help. I can ping the url from the server I can ping google.com so seems DNS is working (using 1.1.1.1). When it tries to get that file I see it flash 10min to download, but goes away.
 

Fabian_E

Proxmox Staff Member
Staff member
Aug 1, 2019
1,815
320
88
Thank you for the help. I can ping the url from the server I can ping google.com so seems DNS is working (using 1.1.1.1). When it tries to get that file I see it flash 10min to download, but goes away.
Not sure what you mean by flash? On apt's CLI output?

Which url/file should I try to manually download? The error doesn't show a full path.
It does show a full URL
Code:
E: Failed to fetch http://download.proxmox.com/debian/pve/dists/bullseye/pve-no-subscription/binary-amd64/proxmox-ve_7.1-1_all.deb  Connection failed [IP: 144.217.225.162 80]

Do you have any proxy configured? Did you change any settings for APT?
 

VR_Architect

New Member
Dec 13, 2021
12
1
1
55
Ping test from server:
Code:
root@FA011PVE:~# ping download.proxmox.com
PING na.cdn.proxmox.com (144.217.225.162) 56(84) bytes of data.
64 bytes from na.cdn.proxmox.com (144.217.225.162): icmp_seq=1 ttl=52 time=78.6 ms
64 bytes from na.cdn.proxmox.com (144.217.225.162): icmp_seq=2 ttl=52 time=78.5 ms
64 bytes from na.cdn.proxmox.com (144.217.225.162): icmp_seq=3 ttl=52 time=78.4 ms
64 bytes from na.cdn.proxmox.com (144.217.225.162): icmp_seq=4 ttl=52 time=78.8 ms

--- na.cdn.proxmox.com ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3001ms
rtt min/avg/max/mdev = 78.369/78.576/78.750/0.139 ms

wget test from server:
Code:
root@FA011PVE:~# wget http://download.proxmox.com/debian/pve/dists/bullseye/pve-no-subscription/binary-amd64/proxmox-ve_7.1-1_all.deb
--2021-12-14 08:51:32--  http://download.proxmox.com/debian/pve/dists/bullseye/pve-no-subscription/binary-amd64/proxmox-ve_7.1-1_all.deb
Resolving download.proxmox.com (download.proxmox.com)... 144.217.225.162, 2607:5300:203:7dc2::162
Connecting to download.proxmox.com (download.proxmox.com)|144.217.225.162|:80... connected.
HTTP request sent, awaiting response...

http get from PC on anther network works as expected. So maybe this is a routing thing? But why can I ping to the Proxmox server but not download? I also see the firewall logs (pfSense) with the request going out.
 

VR_Architect

New Member
Dec 13, 2021
12
1
1
55
I decided to reinstall one of the servers to the latest version 7.2 and after changing the repositories I ran apt-update. Note that the update can get the files from the ftp.debian.org and security.debian.org sites, but not the download.proxmox.com site. So my routing and connection to the internet is working.

Code:
root@FA010PVE:~# apt update
Get:1 http://security.debian.org/debian-security bullseye-security InRelease [44.1 kB]
Get:2 http://ftp.debian.org/debian bullseye InRelease [116 kB]
Get:3 http://security.debian.org/debian-security bullseye-security/main amd64 Packages [99.5 kB]
Get:4 http://security.debian.org/debian-security bullseye-security/main Translation-en [62.2 kB]
Get:5 http://ftp.debian.org/debian bullseye-updates InRelease [39.4 kB]
Get:6 http://ftp.debian.org/debian bullseye/main amd64 Packages [8,180 kB]
Get:7 http://ftp.debian.org/debian bullseye/main Translation-en [6,241 kB]
Get:8 http://ftp.debian.org/debian bullseye/contrib amd64 Packages [50.5 kB]
Get:9 http://ftp.debian.org/debian bullseye/contrib Translation-en [46.9 kB]
Get:10 http://ftp.debian.org/debian bullseye-updates/main amd64 Packages [2,592 B]
Get:11 http://ftp.debian.org/debian bullseye-updates/main Translation-en [2,343 B]
Err:12 http://download.proxmox.com/debian/pve bullseye InRelease
  Connection failed [IP: 144.217.225.162 80]
Err:13 http://download.proxmox.com/debian/ceph-pacific bullseye InRelease
  Connection failed [IP: 144.217.225.162 80]
Fetched 14.9 MB in 2min 1s (123 kB/s)
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
All packages are up to date.
W: Failed to fetch http://download.proxmox.com/debian/pve/dists/bullseye/InRelease  Connection failed [IP: 144.217.225.162 80]
W: Failed to fetch http://download.proxmox.com/debian/ceph-pacific/dists/bullseye/InRelease  Connection failed [IP: 144.217.225.162 80]
W: Some index files failed to download. They have been ignored, or old ones used instead.

Hangs in a wget from the server:
Code:
root@FA010PVE:~# wget http://download.proxmox.com/debian/pve/dists/bullseye/InRelease
--2021-12-14 09:26:10--  http://download.proxmox.com/debian/pve/dists/bullseye/InRelease
Resolving download.proxmox.com (download.proxmox.com)... 144.217.225.162, 2607:5300:203:7dc2::162
Connecting to download.proxmox.com (download.proxmox.com)|144.217.225.162|:80... connected.
HTTP request sent, awaiting response...
 
Last edited:

t.lamprecht

Proxmox Staff Member
Staff member
Jul 28, 2015
5,214
1,520
164
South Tyrol/Italy
shop.proxmox.com
I decided to reinstall one of the servers to the latest version 7.2 and after changing the repositories I ran apt-update. Note that the update can get the files from the ftp.debian.org and security.debian.org sites, but not the download.proxmox.com site. So my routing and connection to the internet is working.

Works all fine here, you're resolving to the North American host in our mirror CDN, the access request and error rate seems normal there, we got a steady amount of requests coming in; monitoring doesn't show any issue or load spike whatsoever and I can download the InRelease file from the mirror you resolve too just fine, also from external hosts that have no relation to our companies network.

This definitively smells like an issue on your end, proxies, firewalls and the like can all be selectively applied, please check there and if you cannot fix this I'd ask you to open a new thread here, as this has nothing to do with the Proxmox VE 7.1 release itself.
 
  • Like
Reactions: Stoiko Ivanov

VR_Architect

New Member
Dec 13, 2021
12
1
1
55

tom

Proxmox Staff Member
Staff member
Aug 29, 2006
15,522
908
163
trying to install 7 version on debian 11
Please open a new thread for this, include the output of "apt update".
 

vesalius

Active Member
Aug 19, 2020
121
30
28
how can i uprade to 7.1 from 7.0 with the free version?
3.1. Package Repositories
Within the WebGui of each node under Updates/Repository enable the Proxmox VE No-Subscription Repository and disable the Proxmox VE Enterprise Repository

3.2. System Software Updates

Then use the Web-Gui under Updates to Refresh then Update each node or use the following CLI commands:

Code:
# apt-get update
# apt-get dist-upgrade
 

Hyien

Member
Jun 18, 2021
65
0
6
32
i presume this removes /etc/apt/sources.list.d/pve-enterprise.list ?
but that would just update the debian components?
 

vesalius

Active Member
Aug 19, 2020
121
30
28
This updates proxmox as well. You will now have the freely available http://download.proxmox.com/debian/pve bullseye pve-no-subscription added to /etc/apt/sources.list. This is how essentially everyone using proxmox without a subscription update and keeps things current.
 

oro.zen

New Member
Oct 18, 2021
1
0
1
40
Lublin, PL
www.facebook.com
https://www.facebook.com/101062565697343/photos/a.101139225689677/142354791568120/

Unfortunately. Upgrading to 5.13 has some problems with amdpgu and LAN.

Patient is a ASUS PN51-E1 with Ryzen5 and so far this update has knocked it down.

Upgrading to version 5.15 helped, but so far the effect is that the server rises without symptoms or bugs. I am waiting for quick fixes, because so far my test lab is very "testing", which is not what I expected from such a great system.
 

Olaf Brenn

Active Member
Jul 3, 2017
43
2
28
49
Hi there, I am not sure if this issue appears somewere else. I updated my Proxmox from 6.4 to 7.1 today. Worked fine but I do get the following error
root@pve2:/etc/apt/sources.list.d# apt upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following packages have been kept back:
libpython2-stdlib libpython2.7-minimal libpython2.7-stdlib python-six python2 python2-minimal python2.7 python2.7-minimal python3-six
0 upgraded, 0 newly installed, 0 to remove and 9 not upgraded.

There is no way to solve this. All other source list are disabled except the source.list as follows:


deb http://ftp.us.debian.org/debian bullseye main contrib
deb http://ftp.us.debian.org/debian bullseye-updates main contrib
# security updates
deb http://security.debian.org/debian-security bullseye-security main contrib
# PVE pve-no-subscription repository provided by proxmox.com,
# NOT recommended for production use
deb http://download.proxmox.com/debian/pve bullseye pve-no-subscription

deb [arch=amd64] http://download.proxmox.com/debian/pve bullseye pve-no-subscription

Is there any idea how to get rid of that packages?
Thanks

Olaf

P.S.
apt list --upgradable
libpython2-stdlib/stable 2.7.18-3 amd64 [upgradable from: 2.7.16-1]
libpython2.7-minimal/stable 2.7.18-8 amd64 [upgradable from: 2.7.16-2+deb10u1]
libpython2.7-stdlib/stable 2.7.18-8 amd64 [upgradable from: 2.7.16-2+deb10u1]
python-six/stable 1.16.0-2 all [upgradable from: 1.12.0-1]
python2-minimal/stable 2.7.18-3 amd64 [upgradable from: 2.7.16-1]
python2.7-minimal/stable 2.7.18-8 amd64 [upgradable from: 2.7.16-2+deb10u1]
python2.7/stable 2.7.18-8 amd64 [upgradable from: 2.7.16-2+deb10u1]
python2/stable 2.7.18-3 amd64 [upgradable from: 2.7.16-1]
python3-six/stable 1.16.0-2 all [upgradable from: 1.12.0-1]
 
Last edited:

Dunuin

Famous Member
Jun 30, 2020
6,113
1,410
149
Germany
Never ever use apt upgrade with proxmox products. Always use apt dist-upgrade or apt full-upgrade. Thats because apt upgrade won't install required dependancies. Then you got updated packages with broken dependancies and you screwed up your PVE installation.
 
  • Like
Reactions: Spirog and vesalius

t.lamprecht

Proxmox Staff Member
Staff member
Jul 28, 2015
5,214
1,520
164
South Tyrol/Italy
shop.proxmox.com
Never ever use apt upgrade with proxmox products. Always use apt dist-upgrade or apt full-upgrade. Thats because apt upgrade won't install required dependancies. Then you got updated packages with broken dependancies and you screwed up your PVE installation.
The recommendation to always use full-upgrade is 100% correct, so just for slight clarifications: while apt (not apt-get) installs new dependencies, it will never remove packages due to getting obsolete and being in conflict with the upgrade (e.g., like python2 due to EOL here is).
apt full-upgrade is always required for major upgrades in Debian in general and for upgrades in Proxmox products, which are following a rolling release model.

In general, please just follow our battle proven upgrade guide as closely as possible, we create it for good reason and it can avoid some pitfalls:
https://pve.proxmox.com/wiki/Upgrade_from_6.x_to_7.0
 
Last edited:
  • Like
Reactions: Neobin

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 your own in 60 seconds.

Buy now!