issues with apt-get update

grukevin200

New Member
May 30, 2021
6
0
1
34
there was a error before: TASK ERROR: command 'apt-get update' failed: exit code 100 so i watched a youtube video on this i changed the config file. now i get this

root@pve:~# apt-get update
Hit:1 http://security.debian.org stretch/updates InRelease
Ign:2 http://ftp.ca.debian.org/debian stretch InRelease
Hit:3 http://ftp.ca.debian.org/debian stretch-updates InRelease
Get:4 http://ftp.ca.debian.org/debian stretch Release [118 kB]
Hit:5 http://download.proxmox.com/debian/pve stretch InRelease
Get:6 http://ftp.ca.debian.org/debian stretch Release.gpg [2,410 B]
Err:7 https://enterprise.proxmox.com/debian/pve buster InRelease
401 Unauthorized [IP: 144.217.225.162 443]
Get:8 http://ftp.ca.debian.org/debian stretch/main amd64 Packages [7,080 kB]
Get:9 http://ftp.ca.debian.org/debian stretch/main Translation-en [5,377 kB]
Get:10 http://ftp.ca.debian.org/debian stretch/contrib amd64 Packages [50.7 kB]
Get:11 http://ftp.ca.debian.org/debian stretch/contrib Translation-en [45.8 kB]
Reading package lists... Done
E: Failed to fetch https://enterprise.proxmox.com/debian/pve/dists/buster/InRelease 401 Unauthorized [IP: 144.217.225.162 443]
E: The repository 'https://enterprise.proxmox.com/debian/pve buster InRelease' is not signed.
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.
root@pve:~#
 

Fabian_E

Proxmox Staff Member
Staff member
Aug 1, 2019
1,041
157
63
Hi,
to access the enterprise repository you need a valid subscription key. See here for more information about the package repositories. Some of your configured repositories use stretch and some use buster. Make sure all use the same! If you are still on PVE 5, use stretch and then follow the following upgrade guide.
 
  • Like
Reactions: Stoiko Ivanov

eduncan911

New Member
Mar 12, 2021
18
4
3
66
Is the expected upgrade time less than 60 days? 6.4 was released in April 2021. 6.3-2 is now broken.

So that would give us... 60 days to update to latest version, or otherwise it may break our system?

Fresh install of 6.3-2 yesterday. Zero config changes. Just installed, and tried mounting a few test drives.

Today tried to update for the first time today, and exact same error:

Code:
root@pve01:~# apt update
Hit:1 http://security.debian.org buster/updates InRelease
Hit:2 http://ftp.us.debian.org/debian buster InRelease
Get:3 http://ftp.us.debian.org/debian buster-updates InRelease [51.9 kB]
Err:4 https://enterprise.proxmox.com/debian/pve buster InRelease
  401  Unauthorized [IP: 144.217.225.162 443]
Reading package lists... Done
E: Failed to fetch https://enterprise.proxmox.com/debian/pve/dists/buster/InRelease  401  Unauthorized [IP: 144.217.225.162 443]
E: The repository 'https://enterprise.proxmox.com/debian/pve buster InRelease' is not signed.
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.

root@pve01:~# echo $?
100

It's worth nothing this returns a error code of 100, and stops all attempts of updating any part of the systems - of a fresh install of 6.3-2!

So, this isn't a "need an enterprise subscription" thing. As it breaks the entire updating process.

My guess is that something got "locked down" recently to require a subscription; however, it broke people's existing installs that have not upgraded to 6.4 yet - as they can no longer update.

cc @Fabian_E
 
Last edited:

Stoiko Ivanov

Proxmox Staff Member
Staff member
May 2, 2018
5,538
759
148
Is the expected upgrade time less than 60 days? 6.4 was released in April 2021. 6.3-2 is now broken.

So that would give us... 60 days to update to latest version, or otherwise it may break our system?
6.3-2 is not broken - the error message you're seeing:
Reading package lists... Done E: Failed to fetch https://enterprise.proxmox.com/debian/pve/dists/buster/InRelease 401 Unauthorized [IP: 144.217.225.162 443] E: The repository 'https://enterprise.proxmox.com/debian/pve buster InRelease' is not signed.
is due to the system not having a valid subscription:
* either get a valid subscription for accessing the enterprise repository OR
* configure the pve-no-subscription repository
https://pve.proxmox.com/wiki/Package_Repositories

just like @Fabian_E said

I hope this helps!
 

eduncan911

New Member
Mar 12, 2021
18
4
3
66
Ah that's right, I remember we have to disable that on new installs in order to get updates... Been a while since I installed Proxmox as I usually used Ansible. This past weekend I just used the old USB stick install manually.

Would love to purchase licenses to support you guys! But it's just too much for my tiny network.

For example, in the past I've setup 4x Proxmox nodes on some small SBCs (UP Board's UP Squared devices), usually for testing. Sometimes for long running k3s, etc. I also have three old dual X8 socket (LGA1366 Xeons from 2008-era) machines with dual CPUs running Proxmox.

By those counts, I would have to spend $1100 US per year for licensing. That's just too rich for my old old homelab, especially since $1000 could bring my homelab into a more modern age! I would gladly pay $90/yr for a "site-wide" homelab license - and I am sure many many other community members would pay that amount as well; but, I can't afford the "per CPU socket" prices.
 
Last edited:
  • Like
Reactions: Stoiko Ivanov

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!