cannot connecto to (https) enterprise.proxmox.com/

jimmyjoe · Mar 21, 2018

pveupdate fails to run
command 'apt-get update' failed: exit code 100
running aptitude update produces an error connecting to https://enterprise.proxmox.com/
Is this a known issue?
Thank you

# aptitude update
Hit http://security.debian.org jessie/updates InRelease
Ign http://ftp.us.debian.org jessie InRelease
Get: 1 https://enterprise.proxmox.com jessie InRelease [188 B]
Ign https://enterprise.proxmox.com jessie InRelease
Get: 2 https://enterprise.proxmox.com jessie Release.gpg [188 B]
Hit http://ftp.us.debian.org jessie Release.gpg
Ign https://enterprise.proxmox.com jessie Release.gpg
Hit http://ftp.us.debian.org jessie Release
Get: 3 https://enterprise.proxmox.com jessie Release [188 B]
Ign https://enterprise.proxmox.com jessie Release
Get: 4 https://enterprise.proxmox.com jessie/pve-enterprise amd64 Packages/DiffIndex [188 B]
Ign https://enterprise.proxmox.com jessie/pve-enterprise amd64 Packages/DiffIndex
Get: 5 https://enterprise.proxmox.com jessie/pve-enterprise Translation-en [188 B]
Get: 6 https://enterprise.proxmox.com jessie/pve-enterprise amd64 Packages [188 B]
Get: 7 https://enterprise.proxmox.com jessie/pve-enterprise Translation-en [188 B]
Get: 8 https://enterprise.proxmox.com jessie/pve-enterprise amd64 Packages [188 B]
Get: 9 https://enterprise.proxmox.com jessie/pve-enterprise Translation-en [188 B]
Get: 10 https://enterprise.proxmox.com jessie/pve-enterprise amd64 Packages [188 B]
Hit http://security.debian.org jessie/updates/main amd64 Packages
Hit http://ftp.us.debian.org jessie/main amd64 Packages
Hit http://ftp.us.debian.org jessie/contrib amd64 Packages
Hit http://ftp.us.debian.org jessie/contrib Translation-en
Hit http://security.debian.org jessie/updates/contrib amd64 Packages
Hit http://security.debian.org jessie/updates/contrib Translation-en
Get: 11 https://enterprise.proxmox.com jessie/pve-enterprise Translation-en [188 B]
Get: 12 https://enterprise.proxmox.com jessie/pve-enterprise amd64 Packages [188 B]
Hit http://ftp.us.debian.org jessie/main Translation-en
Hit http://security.debian.org jessie/updates/main Translation-en
Get: 13 https://enterprise.proxmox.com jessie/pve-enterprise Translation-en [188 B]
Ign https://enterprise.proxmox.com jessie/pve-enterprise Translation-en
Get: 14 https://enterprise.proxmox.com jessie/pve-enterprise amd64 Packages [188 B]
Err https://enterprise.proxmox.com jessie/pve-enterprise amd64 Packages
HttpError401
100% [Working]W: Failed to fetch https://enterprise.proxmox.com/debian/dists/jessie/pve-enterprise/binary-amd64/Packages: HttpError401
E: Some index files failed to download. They have been ignored, or old ones used instead.
E: Couldn't rebuild package cache

Alwin · Mar 21, 2018

Do you have a subscription? If not, then this is expected (see the link).
https://pve.proxmox.com/wiki/Package_Repositories

jimmyjoe · Mar 21, 2018

Yes, this machine has susbscription. Actually have three Proxmox hosts (with subs.) in this subnet having the same issue for a few days now.

tom · Mar 21, 2018

please post your current version:

> pveversion -v

check your subscription status.

> pvesubscription get
(but do not post your key here)

Alwin · Mar 22, 2018

Are you using a firewall (web filter)?

jimmyjoe · Mar 22, 2018

UPDATE: I checked with our license purchasing person and the subscriptions for these hosts have been renewed through 2019-02-19. Something is stil amiss here. We do have an edge firewall filter of some kind. I can connect to https://enterprise.proxmox.com using curl from these hosts, so port 443 is open. I'll post the info requested in a previous thread.

pvesubscription shows nextduedate: 2018-02-18 on all hosts. We don't typically manage these hosts through the web browser so didn't notice the subscription running low... I'll have to edit PS1 and put a notice in the bash prompt.
Thanks for your time.

jimmyjoe · Mar 22, 2018

output of pveversion -v below.
curl output:
# curl https://enterprise.proxmox.com
<html>
<head><title>Index of /</title></head>
<body bgcolor="white">
<h1>Index of /</h1><hr><pre><a href="../">../</a>
<a href="debian/">debian/</a> 15-Dec-2017 08:19 -
</pre><hr></body>
</html>

host .27
proxmox-ve: 4.4-107 (running kernel: 4.4.98-6-pve)
pve-manager: 4.4-22 (running version: 4.4-22/2728f613)
pve-kernel-4.4.98-2-pve: 4.4.98-101
pve-kernel-4.4.98-5-pve: 4.4.98-105
pve-kernel-4.4.95-1-pve: 4.4.95-99
pve-kernel-4.4.67-1-pve: 4.4.67-92
pve-kernel-4.4.98-6-pve: 4.4.98-107
pve-kernel-4.4.76-1-pve: 4.4.76-94
pve-kernel-4.4.83-1-pve: 4.4.83-96
pve-kernel-4.4.62-1-pve: 4.4.62-88
lvm2: 2.02.116-pve3
corosync-pve: 2.4.2-2~pve4+1
libqb0: 1.0.1-1
pve-cluster: 4.0-54
qemu-server: 4.0-115
pve-firmware: 1.1-11
libpve-common-perl: 4.0-96
libpve-access-control: 4.0-23
libpve-storage-perl: 4.0-76
pve-libspice-server1: 0.12.8-2
vncterm: 1.3-2
pve-docs: 4.4-4
pve-qemu-kvm: 2.9.1-9~pve4
pve-container: 1.0-104
pve-firewall: 2.0-33
pve-ha-manager: 1.0-41
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u3
lxc-pve: 2.0.7-4
lxcfs: 2.0.6-pve1
criu: 1.6.0-1
novnc-pve: 0.5-9
smartmontools: 6.5+svn4324-1~pve80
zfsutils: 0.6.5.9-pve15~bpo80

host .181
proxmox-ve: 4.4-107 (running kernel: 4.4.98-6-pve)
pve-manager: 4.4-22 (running version: 4.4-22/2728f613)
pve-kernel-4.4.98-2-pve: 4.4.98-101
pve-kernel-4.4.44-1-pve: 4.4.44-84
pve-kernel-4.4.98-5-pve: 4.4.98-105
pve-kernel-4.4.95-1-pve: 4.4.95-99
pve-kernel-4.4.67-1-pve: 4.4.67-92
pve-kernel-4.4.98-6-pve: 4.4.98-107
pve-kernel-4.4.76-1-pve: 4.4.76-94
pve-kernel-4.4.83-1-pve: 4.4.83-96
pve-kernel-4.4.40-1-pve: 4.4.40-82
pve-kernel-4.4.62-1-pve: 4.4.62-88
lvm2: 2.02.116-pve3
corosync-pve: 2.4.2-2~pve4+1
libqb0: 1.0.1-1
pve-cluster: 4.0-54
qemu-server: 4.0-115
pve-firmware: 1.1-11
libpve-common-perl: 4.0-96
libpve-access-control: 4.0-23
libpve-storage-perl: 4.0-76
pve-libspice-server1: 0.12.8-2
vncterm: 1.3-2
pve-docs: 4.4-4
pve-qemu-kvm: 2.9.1-9~pve4
pve-container: 1.0-104
pve-firewall: 2.0-33
pve-ha-manager: 1.0-41
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u3
lxc-pve: 2.0.7-4
lxcfs: 2.0.6-pve1
criu: 1.6.0-1
novnc-pve: 0.5-9
smartmontools: 6.5+svn4324-1~pve80
zfsutils: 0.6.5.9-pve15~bpo80

host .28
proxmox-ve: 4.4-107 (running kernel: 4.4.98-6-pve)
pve-manager: 4.4-22 (running version: 4.4-22/2728f613)
pve-kernel-4.4.98-2-pve: 4.4.98-101
pve-kernel-4.4.98-4-pve: 4.4.98-104
pve-kernel-4.4.44-1-pve: 4.4.44-84
pve-kernel-4.4.98-5-pve: 4.4.98-105
pve-kernel-4.4.95-1-pve: 4.4.95-99
pve-kernel-4.4.67-1-pve: 4.4.67-92
pve-kernel-4.4.98-6-pve: 4.4.98-107
pve-kernel-4.4.76-1-pve: 4.4.76-94
pve-kernel-4.4.83-1-pve: 4.4.83-96
pve-kernel-4.4.40-1-pve: 4.4.40-82
pve-kernel-4.4.62-1-pve: 4.4.62-88
lvm2: 2.02.116-pve3
corosync-pve: 2.4.2-2~pve4+1
libqb0: 1.0.1-1
pve-cluster: 4.0-54
qemu-server: 4.0-115
pve-firmware: 1.1-11
libpve-common-perl: 4.0-96
libpve-access-control: 4.0-23
libpve-storage-perl: 4.0-76
pve-libspice-server1: 0.12.8-2
vncterm: 1.3-2
pve-docs: 4.4-4
pve-qemu-kvm: 2.9.1-9~pve4
pve-container: 1.0-104
pve-firewall: 2.0-33
pve-ha-manager: 1.0-41
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u3
lxc-pve: 2.0.7-4
lxcfs: 2.0.6-pve1
criu: 1.6.0-1
novnc-pve: 0.5-9
smartmontools: 6.5+svn4324-1~pve80
zfsutils: 0.6.5.9-pve15~bpo80

Alwin · Mar 22, 2018

The server need to access the shop to validate the subscription. Maybe this is blocked.
https://shop.maurer-it.com/knowledgebase.php?action=displayarticle&id=4

jimmyjoe · Mar 22, 2018

This seems to connect via curl OK on all three hosts. We purchased our licenseses thorugh Symmcom.com (not shop.maurer-it.com) if it matters.

$ curl https://shop.maurer-it.com
<!DOCTYPE html>
<html lang="en">
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
<title>Portal Home - Maurer IT Systemloesungen KG</title>

<base href="https://shop.maurer-it.com/" />
...

Alwin · Mar 23, 2018

Including IP addresses? It doesn't matter, the subscription validation has the same endpoint.
You can use 'pvesubscription update' & 'pvesubscription get' on the console to check for the renewal. Once the update of the subscription works, the access to the repository should also be working.

jimmyjoe · Mar 23, 2018

Tried the commands suggested on host below, still not working. Is there some way to debug the pvesubscription command to see what it's doing?

host .28
# pvesubscription get
checktime: 1521789242
key: pve2c-xxxxxxxxxx
nextduedate: 2018-02-18
productname: Proxmox VE Community Subscription 2 CPUs/year
regdate: 2015-02-18 00:00:00
serverid: <redacted>
sockets: 2
status: Suspended
validdirectory: <redacted>

# pvesubscription update

# pvesubscription get
checktime: 1521810380
key: pve2c-xxxxxxxxxx
nextduedate: 2018-02-18
productname: Proxmox VE Community Subscription 2 CPUs/year
regdate: 2015-02-18 00:00:00
serverid: <redacted>
sockets: 2
status: Suspended
validdirectory: <redacted>

# aptitude update
...
Get: 14 https://enterprise.proxmox.com jessie/pve-enterprise amd64 Packages [188 B]
Err https://enterprise.proxmox.com jessie/pve-enterprise amd64 Packages
HttpError401
100% [Working]W: Failed to fetch https://enterprise.proxmox.com/debian/dists/jessie/pve-enterprise/binary-amd64/Packages: HttpError401
E: Some index files failed to download. They have been ignored, or old ones used instead.
E: Couldn't rebuild package cache

fabian · Mar 23, 2018

jimmyjoe said:
Tried the commands suggested on host below, still not working. Is there some way to debug the pvesubscription command to see what it's doing?

host .28
# pvesubscription get
checktime: 1521789242
key: pve2c-xxxxxxxxxx
nextduedate: 2018-02-18
productname: Proxmox VE Community Subscription 2 CPUs/year
regdate: 2015-02-18 00:00:00
serverid: <redacted>
sockets: 2
status: Suspended
validdirectory: <redacted>

# pvesubscription update

# pvesubscription get
checktime: 1521810380
key: pve2c-xxxxxxxxxx
nextduedate: 2018-02-18
productname: Proxmox VE Community Subscription 2 CPUs/year
regdate: 2015-02-18 00:00:00
serverid: <redacted>
sockets: 2
status: Suspended
validdirectory: <redacted>

# aptitude update
...
Get: 14 https://enterprise.proxmox.com jessie/pve-enterprise amd64 Packages [188 B]
Err https://enterprise.proxmox.com jessie/pve-enterprise amd64 Packages
HttpError401
100% [Working]W: Failed to fetch https://enterprise.proxmox.com/debian/dists/jessie/pve-enterprise/binary-amd64/Packages: HttpError401
E: Some index files failed to download. They have been ignored, or old ones used instead.
E: Couldn't rebuild package cache

I suggest opening a support ticket on https://my.proxmox.com (this is allowed for troubleshooting subscription / pve-enterprise related issues, even if your subscription level does otherwise not include support tickets).

tom · Mar 23, 2018

jimmyjoe said:
status: Suspended

If you keys is suspended, there is a reason - most times unpaid invoices.

=> contact your reseller or our support for more info.

jimmyjoe · Mar 23, 2018

Will do. Thanks.

Search

Search

cannot connecto to (https) enterprise.proxmox.com/

jimmyjoe

Active Member

Alwin

Proxmox Retired Staff

jimmyjoe

Active Member

tom

Proxmox Staff Member

Alwin

Proxmox Retired Staff

jimmyjoe

Active Member

jimmyjoe

Active Member

Alwin

Proxmox Retired Staff

jimmyjoe

Active Member

Alwin

Proxmox Retired Staff

jimmyjoe

Active Member

fabian

Proxmox Staff Member

tom

Proxmox Staff Member

jimmyjoe

Active Member