Have Subscription for Enterprise Repo but get 401

mattym

Renowned Member
Mar 8, 2011
30
0
71
hi,

I have a valid key for updates from the enterprise repo. I have just upgraded from 2.3 to 3.1 using the script which was originally for upgrading 2.3 to 3.0.

When I try and run -

./pve-upgrade-2.3-to-3.0 --purge
I get -

W: Failed to fetch https://enterprise.proxmox.com/debian/dists/wheezy/pve-enterprise/binary-amd64/Packages The requested URL returned error: 401


E: Some index files failed to download. They have been ignored, or old ones used instead.
update package list failed

also tried apt-get update && apt-get dist-upgrade but get the same 401.

my subscription key is installed and says active.

Any ideas?

thanks

matt
 
On your first line you said you have just upgraded from 2.3 to 3.1, but then you are trying to run the upgrade program again. So did you already upgrade or no?

Error 401 only means the data you are trying to access requires authentication like username/password. Could you post your sources.list entries?
 
hi,

I was following the guide from 2.3 to 3.0 and it installed 3.1. Yes it probably is up to date but I shouldnt see a 401 if I have a valid subscription? I assume I still need to run -

./pve-upgrade-2.3-to-3.0 --purge

sources.list >

deb http://ftp.uk.debian.org/debian wheezy main contrib


# PVE packages provided by proxmox.com
deb http://download.proxmox.com/debian wheezy pve


# security updates
deb http://security.debian.org/ wheezy/updates main contrib


cat /etc/apt/sources.list.d/pve-enterprise.list
deb https://enterprise.proxmox.com/debian wheezy pve-enterprise

thanks

matt
 
hi,

looks like its working now, must take some time to pickup the subscription or something and sync up with the enterprise repository access at Proxmox.

thanks

matt
 
this isnt working now though because I carried on and removed apache2 after the purge wouldnt run -

/etc/init.d/apache2 stop
open3: exec of /etc/init.d/apache2 stop failed at ./pve-upgrade-2.3-to-3.0 line 92

:(
 
After you successfully upgraded to 3.1 , running ./pve-upgrade-2.3-to-3.0 --purge probably was not necessary. --purge takes out anything you have manually installed or configured as far as i know. Not sure why you tried to remove apache2 manually though. The best procedure would have been upgrade 2.3 to 3 using upgrade script, then 3.0 to 3.1 using #apt-get dist upgrade. Try to remove apache2 then reinstall again. Not sure how this will affect the Proxmox web GUI though. Somebody may be able to confirm it.
 
ok thanks. As for the upgrade I didnt have a lot of choice, I ran the script expecting to go to version 3.0 but it went straight to 3.1. As for manually removing apache that was part of the wiki for going 2.3 to 3.0, it had a few extra steps.

If I dont have to worry about the purge then its fine as it is I guess? All seems to be working ok.

thanks
 

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 yours easily in our online shop.

Buy now!