PVE 9: Subscription validation timeout - Error 596 Connection timed out (both CLI and Web UI)

Oct 6, 2025
3
0
1
Subject: PVE 9: Subscription validation timeout - Error 596 Connection timed out (both CLI and Web UI)

System Information:
- Proxmox VE 9

Problem Description:
I'm unable to validate my subscription key. Both the command line (pvesubscription set) and Web UI return timeout errors when attempting to contact the subscription service.

Error Messages:
Code:
# CLI Error:
root@pve:~# pvesubscription set pve1c-xxxxxxxxxxxxxx
Error checking subscription: timeout: global

# Web UI Error:
Error 596: Connection timed out

What I've already tested:

1. Network connectivity is working:
Code:
# DNS resolution works:
nslookup shop.proxmox.com
# Returns: 79.133.36.249 and 2a01:7e0:0:424::2

# HTTPS connectivity works:
curl -I https://shop.proxmox.com/
# Returns: HTTP/1.1 200 OK

# Internet connectivity confirmed:
ping -c 4 8.8.8.8  # Success

2. IPv4 and IPv6 traceroutes show connectivity to your network edge:
- Both IPv4 and IPv6 reach your hosting provider (first-colo.net / 2a01:7e0 network)
- Traffic times out at your network edge, not on my end

3. Attempted workarounds:
- Forced IPv4-only connections
- Temporarily disabled IPv6

Log Evidence:
When attempting subscription validation through Web UI, pveproxy workers crash due to timeout:
Code:
Oct 06 12:23:59 pve pveproxy[169201]: worker exit
Oct 06 12:23:59 pve pveproxy[1527]: worker 169201 finished

Timeline:
This issue may have started around the time I upgraded from PVE 8 to PVE 9, though I'm not certain if it's directly related.

Additional Notes:
- The subscription was successfully removed but cannot be re-added
- Error occurs consistently across multiple attempts over several days
- No firewall or proxy configuration changes were made

Questions:
1. Are there known issues with subscription validation in PVE 9?
2. Have the subscription service endpoints changed recently?
3. Is there a manual workaround to configure a valid subscription while this is resolved?

This appears to be either a regression in PVE 9's subscription handling or an issue with the subscription validation service itself. Any guidance would be appreciated.
 
I made the mistake of removing my key to try to re-add it, which I can't anymore, but before that it would show


Code:
root@pve:~# pvesubscription get
checktime: 1757961853
key: XXXXXXXXXXX
message: subscription information too old
nextduedate: 2026-09-10
productname: Proxmox VE Community Subscription 1 CPU/year
regdate: 2025-09-10 00:00:00
serverid: XXXXXXXXXXXXXXX
sockets: 1
status: invalid
url: https://www.proxmox.com/en/proxmox-virtual-environment/pricing

So I am not getting any update until this is fixed I assume