Subscription key invalid behind a proxy

[gondouin]

Hi !
I took 5 licences for 5 servers. 4 are ok but the 5th said me "Invalid response from server: 501 Not Implemented (500)" when I Verify the subscription key. The only difference between the servers is that this one is behind a proxy.
apt-get update said error 401 (normal).
We have looked the log of firewall but there's nothing special.
Is someone have meet the same problem ?

Regards,

 

[dietmar]

You configured the proxy in datacenter options?

 

[gondouin]

Yes, of course.
Others repositories are working. Only the key verification fail, so the enterprise repository say "forbidden".
Maybe there's a special port (closed) to verify the key ?

 

[maurin]

Hello,

I see a similar bug. I think that my subscribtions are now up and I checked that, trought my proxy, I can access un-securised repositories.

Which kind of other informations may I provide you to help for debug ?

# cat /etc/apt/apt.conf.d/76pveproxy | perl -ane 's/Acquire::http::Proxy/Acquire::https::Proxy/ && print' > /etc/apt/apt.conf.d/77pveproxySylM
# aptitude update
[...]
Get: 1 https://enterprise.proxmox.com wheezy Release.gpg [490 B]
Ign https://enterprise.proxmox.com wheezy Release.gpg  
[...]
Ign https://enterprise.proxmox.com wheezy Release
Err https://enterprise.proxmox.com wheezy/pve-enterprise amd64 Packages
  The requested URL returned error: 401
Ign https://enterprise.proxmox.com wheezy/pve-enterprise Translation-en_US
Ign https://enterprise.proxmox.com wheezy/pve-enterprise Translation-en
4% [Working]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.
E: Couldn't rebuild package cache
[...]

Sylvain MAURIN

 

[tom]

did you wait one hour after you activated the key on your host? if not, try again.

 

[maurin]

I actived our keys sept.12th, and got this error. As I knew that my administration had still not paid your invoice, I took patience until my back-office officer do her job done.
I got a "suspension" mail sept.26th from your part as you still got our money.

It is only last tuesday that Martin confirmed that we paid you (Ouf!) and I waited until yesterday to try again my check by apt and web interface.

As I am an "communauty user I came to forums to seek a solution today.

 

[tom]

pls open a request via https://shop.maurer-it.com/contact.php - there were issues with http proxy (already fixed) but in some case there are manual steps needed to get it running again.

 

[curlingcanteen]

pls open a request via https://shop.maurer-it.com/contact.php - there were issues with http proxy (already fixed) but in some case there are manual steps needed to get it running again.

Unfortunately apt-proxy doesn't seem to be very well-documented. I'm a community user too, trying to add a proxy for the http://pve.proxmox.com/wiki/Package_repositories#Proxmox_VE_No-Subscription_Repository but apt just hangs:

root@node-prox-c:~# apt-get update
Hit http://apt-proxy.server.edu wheezy Release.gpg
[...]
Ign https://apt-proxy.server.edu wheezy Release.gpg
Ign https://apt-proxy.server.edu wheezy Release
Err https://apt-proxy.server.edu wheezy/pve-no-subscription amd64 Packages
  SSL connection timeout at 119886Ign https://apt-proxy.server.edu wheezy/pve-no-subscription Translation-en_US
100% [Working]^C

I don't suppose you'd be willing to share with the community what the issues with http proxy were and what we need to do to fix them?

 

[tom]

...

I don't suppose you'd be willing to share with the community what the issues with http proxy were and what we need to do to fix them?

the issue was a bug in apt-transport-https - but as you do not use our enterprise proxy you do not need authentication and you issue is not related.

more details:
http://download.proxmox.com/debian/...-amd64/apt-transport-https_0.9.7.10.changelog

and the package:
http://download.proxmox.com/debian/...-amd64/apt-transport-https_0.9.7.10_amd64.deb

 

[curlingcanteen]

the issue was a bug in apt-transport-https - but as you do not use our enterprise proxy you do not need authentication and you issue is not related.

Gotcha. Thanks for clarifying. I'll open another post for help with apt-cache.