Woohoo, Proxmox VE 5.0 has been released, this version is based on Debian 9. (Linux Kernel 4.10) It includes allot of new features, but sadly updates are still pointing to the enterprise repository for updates. This results in ugly error message when trying apt-get update such as :
W: The repository 'https://enterprise.proxmox.com/debian/pve stretch Release' does not have a Release file. N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use. N: See apt-secure(8) manpage for repository creation and user configuration details. E: Failed to fetch https://enterprise.proxmox.com/debian/pve/dists/stretch/pve-enterprise/binary-amd64/Packages 401 Unauthorized E: Some index files failed to download. They have been ignored, or old ones used instead.
To fix this, its similar to V3.X and V4.X. We need to add one repository : nano /etc/apt/sources.list
add :
deb http://download.proxmox.com/debian stretch pve-no-subscription
Then disable or remove
rm -f /etc/apt/sources.list.d/pve-enterprise.list
(for disable add a # in front of the first line starting with deb)
Now you can run those updates 🙂 take note only apt-get update and apt-get dist-upgrade are supported by Proxmox !
Now I dislike the way Proxmox pushes people to take a subscription and there pricing method, but it is an amazing piece of free software! Well done Proxmox devs !
Thank you for this.
1 October, 2017 at 22:27you’re welcome!
2 October, 2017 at 15:18Thanks!!!
12 March, 2018 at 11:48i try this steps but proxmox not update when i do apt-get update.
I must to run anohter commmand?
this is my output:
apt-get update
Obj:1 http://security.debian.org/debian-security stretch/updates InRelease
Ign:2 http://debian.mirrors.ovh.net/debian stretch InRelease
Des:3 http://debian.mirrors.ovh.net/debian stretch-updates InRelease [91,0 kB]
Obj:4 http://download.proxmox.com/debian stretch InRelease
Des:5 http://debian.mirrors.ovh.net/debian stretch Release [118 kB]
Obj:6 http://download.proxmox.com/debian/pve stretch InRelease
Descargados 209 kB en 0s (608 kB/s)
Leyendo lista de paquetes… Hecho
20 October, 2017 at 20:14Yes : apt-get dist-upgrade
20 October, 2017 at 20:37thanks! really i can do it!
20 October, 2017 at 22:03Thanks mate!
After a complete rebuild I couldn’t remember what to edit, quick Google search brought me your way.
Take care!
–Bob
30 November, 2017 at 11:21Welcome 😉
30 November, 2017 at 12:00For minor upgrades like the following, after the dist-upgrade, is a reboot needed or a restart of which services?
lxc-pve:amd64/stretch 2.1.0-2 upgradeable to 2.1.1-2
lxcfs:amd64/stretch 2.0.7-pve4 upgradeable to 2.0.8-1
proxmox-ve:all/stretch 5.1-25 upgradeable to 5.1-28
pve-cluster:amd64/stretch 5.0-15 upgradeable to 5.0-17
pve-firewall:amd64/stretch 3.0-3 upgradeable to 3.0-4
pve-ha-manager:amd64/stretch 2.0-3 upgradeable to 2.0-4
pve-kernel-4.13.4-1-pve:amd64/stretch 4.13.4-25 upgradeable to 4.13.4-26
pve-manager:amd64/stretch 5.1-35 upgradeable to 5.1-38
pve-qemu-kvm:amd64/stretch 2.9.1-2 upgradeable to 2.9.1-3
Thank you.
1 December, 2017 at 11:03Unless I have issues I don’t reboot. But a pve-kernel and pve-manager is pretty big changes, I would restart to be sure everything works. (officially I assume a reboot would be recommended)
3 December, 2017 at 11:47Thanks it did work for me after browsing the net for 7 days trying to get correct information thanks a lot
10 November, 2018 at 00:40Thanks a lot it’s work..!
I <3 you 😉
10 November, 2018 at 23:34Thank you
24 November, 2018 at 22:33[…] Proxmox VE 5.0 fix updates / upgrades […]
2 February, 2019 at 17:51Proxmox 5.3-9 already has the non-enterprise repo in
/etc/apt/sources.list.d/pve-install-repo.list
so there’s no need to add it in
/etc/apt/sources.list
Doing it anyway will just lead to a system warning that the same repo is duplicated.
11 February, 2019 at 09:23Well then it changed recently, cause I had to add them manually back in 2017 🙂 So I’m happy they added it by default, if that is the new way !
11 February, 2019 at 11:54They did not add this, I installed proxmox on my first server around 2 weeks ago, and I had changed it.
Thanks for this <3
18 February, 2019 at 21:28