Subscription status: "invalid: subscription information too old"

[rsiera]

My subscription page says that the Subscription status is "invalid: subscription information too old".
When I click the "Check" button, after a while the message "Connection error - Timeout." appears.
Where can I find more information what is going on?

 

[Moayad]

Hi,

Can you please check the DNS on the PVE side if everything is ok?

 

[rsiera]

Your suggestion, together with the support of the shop team, brought me on the right path.
Ping to shop.proxmox.com resulted in an IP6 address which indeed does not work on our LAN. We do not support IP6.

The support team confirmed:

with the change of our subscription-check introduced in October 2022, the code
does not fall back to IPv4 on setups that have IPv6 addresses configured,
but where the outbound connections on IPv6 does not work.

Either configure your host to correctly be able to access shop.proxmox.com via IPv6
or disable IPv6 on the affected node:
I assume can use the docs from Proxmox VE https://pve.proxmox.com/pve-docs/chapter-sysadmin.html#_disabling_ipv6_on_the_node

The manual was a little too cryptic for me, but I followed these instructions and that work perfectly.

 

[iprigger]

Hi All,

I have the same issue on one node:

checktime: 1780104636
key: pveXc-XXXXXXXX
message: subscription information too old
nextduedate: 2026-08-28
productname: Proxmox VE Community Subscription 1 CPU/year
regdate: 2013-08-28 00:00:00
serverid: ******************8B6E72
sockets: 1
status: invalid
url: https://www.proxmox.com/en/proxmox-virtual-environment/pricing

IPv6 is configured and working.

Tobias

 

[iprigger]

Hi All,

I have the same issue on one node:

checktime: 1780104636
key: pveXc-XXXXXXXX
message: subscription information too old
nextduedate: 2026-08-28
productname: Proxmox VE Community Subscription 1 CPU/year
regdate: 2013-08-28 00:00:00
serverid: ******************8B6E72
sockets: 1
status: invalid
url: https://www.proxmox.com/en/proxmox-virtual-environment/pricing

IPv6 is configured and working.

Tobias

Just as a heads-up: Removing the license, resetting it and re-adding it did the trick.

No idea as of why this happened.

Tobias