Error 401 updating the system

[LkS45]

(...)
Err:7 https://enterprise.proxmox.com/debian/pve stretch/pve-enterprise amd64 Packages
401 Unauthorized
(...)
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 detals.
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.

Im using 5.0 beta1, the cpu is AMD FX-8350.

Thanks!

 

[dietmar]

Pve 5.0 beta1 is a beta release, so there is no enterprise repository.

 

[tom]

See also:

https://pve.proxmox.com/wiki/Downlo...rtual_Environment_5.x_beta_to_latest_5.x_beta

 

[robetus]

I also faced this problem and found the very simple solution. This applies to upgrading from BETA 5.0 to the release. First remove anything you have inside the
/etc/apt/sources.list.d/ directory that is related to proxmox. Then:

echo "deb http://download.proxmox.com/debian/pve stretch pve-no-subscription" > /etc/apt/sources.list.d/pve-install-repo.list

and

wget http://download.proxmox.com/debian/proxmox-ve-release-5.x.gpg -O /etc/apt/trusted.gpg.d/proxmox-ve-release-5.x.gpg

and finally

apt update && apt dist-upgrade

If you're still seeing BETA in the version inside the web console, clear your browser cache. This would've probably saved me an unnecessary reboot, but you may still need to reboot. Maybe someone else can tell us if we need to reboot after an upgrade.

 

[dietmar]

Maybe someone else can tell us if we need to reboot after an upgrade.

Yes (there is a new kernel).

 

[salty]

RE: "Do you already have a Commercial Support Subscription? - If not, Buy now and read the documentation.

I am preparing for an upcoming conference engagement where I will be speaking on the topic of infrastructure as code. In the past I have used VMWare in all of my examples but thought it might be cool to use an open source alternative this time. In researching the possibilities I ran across proxmox and was pretty excited. Unfortunately, my excitement is rapidly turning to disappointment as I keep finding evidence that proxmox seeks to make it as painful as possible to simply use the community edition with no subscription. The first thing I ran into was the annoying prompting that repeatedly occurs when you log into the web ui; a prompting that you can only get rid of by going into one of the underlying web application's JavaScript files and changing an "if condition". Then, when my installation went to update its packages, I find that the enterprise repository is configured by default despite the fact that it will repeatedly error unless you manually change it or purchase a subscription. Then, when I went to change from the enterprise repository to the community repository I started getting errors because it appears that the community repository is treated like a second class citizen; only supporting http downloads and/or having an invalid certificate (I haven't completely researched this last comment so take it with a grain of salt). However, one of the most frustrating aspects of all of this has been the fact that every response I see from a promox staff member contains a P.S. that says "Do you already have a Commercial Support Subscription? - If not, Buy now and read the documentation." This by itself wouldn't have been bad if it wouldn't have been accompanied by all of the annoying "get a subscription" subtexts that led me to these forums in the first place. Long story short, let your product do the talking. Make it easy for developers and infrastructure engineers to download and use the community edition without a bunch of annoying prompts and errors and/or manual configuration. I look at a lot of these types of products and that's what some of the most successful open source (e.g. Hashicorp) and increasingly commercial vendors are doing.

Also, as an aside, I considered the community plan to gain access to the full documentation and the enterprise repository. However, the per CPU licensing for this plan put me over the top. If I want to put together a legitimate example then I really need to setup at least a small cluster. To do this I have to purchase a multiple CPU license?

 

[t.lamprecht]

Don't bump old threads with off-topic rants.

The first thing I ran into was the annoying prompting that repeatedly occurs when you log into the web ui; a prompting that you can only get rid of by going into one of the underlying web application's JavaScript

You can also get rid of it by buying a subscription, so there's not only one way. If you find that the price of the equivalent of two beers a month is to much, you can naturally stay with VMWare, if their cheaper, or any other solution fitting your needs, it's your free choice.

community repository is treated like a second class citizen; only supporting http downloads and/or having an invalid certificate (I haven't completely researched this last comment so take it with a grain of salt).

As one can determine from the URL format (HTTP vs HTTPS) it's not an invalidate certificate, and as all our packages are GPG signed with our release key, and verified against its public key after downloading this has no security implications whatsoever (see: https://whydoesaptnotusehttps.com/ )

Long story short, let your product do the talking. Make it easy for developers and infrastructure engineers to download and use the community edition without a bunch of annoying prompts and errors and/or manual configuration.

I think that a single prompt on login or reading much referenced docs to it ( https://pve.proxmox.com/pve-docs/pve-admin-guide.html#sysadmin_package_repositories ) should not hinder any engineer to checkout the project.

access to the full documentation

The full documentation is in the open, https://pve.proxmox.com/pve-docs/ and also gets included with every installation, it's under the GNU Free Documentation License.

If I want to put together a legitimate example then I really need to setup at least a small cluster

For evaluation you can go fine without subscription, at least if you do not need enterprise support for the evaluation process. Further, multiple CPU subscriptions are requirements for physical host CPUs (i.e., multi-socket NUMA systems) not physical/virtual cores of host or guest.

Closing this one as off-topic, maybe see: https://forum.proxmox.com/threads/p...ptions-and-why-everybody-should-buy-one.9244/