Possible issue with na2.cdn.proxmox.com (95.133.229.241) refusing HTTPS connections from US East Coast

[dmackdaddy]

Title:
Possible issue with na2.cdn.proxmox.com (95.133.229.241) refusing HTTPS connections from US East Coast

Hi,

I believe I've isolated what appears to be a problem with one CDN edge serving download.proxmox.com.

Environment:

• Proxmox VE 9
• Debian Trixie
• No-subscription repository
• East Coast US (Florida)
• Spectrum ISP

Repository configuration is the standard:

https://download.proxmox.com/debian/pve

The enterprise repository is not configured.

Symptoms​

apt update intermittently reports either:

SSL connection failed: certificate verify failed
or

Could not connect to download.proxmox.com:443
Connection refused

DNS​

All resolvers (local, Cloudflare, Google) resolve to:

download.proxmox.com
-> download.cdn.proxmox.com
-> us.na.cdn.proxmox.com
-> na2.cdn.proxmox.com
-> 95.133.229.241

Connectivity​

The problem reproduces from multiple systems on the same network:

• macOS
• Ubuntu 24.04
• Proxmox VE host

All fail with:

curl -4 -v https://download.proxmox.com/debian/pve/

Trying 95.133.229.241:443...
Connection refused

Additional testing​

I tested other CDN nodes directly:

de3.cdn.proxmox.com
and

fr.cdn.proxmox.com
Both successfully complete HTTPS connections.

Only the NA node (95.133.229.241) appears to refuse connections.

Has anyone else seen this with na2.cdn.proxmox.com?

Is there a known issue with that CDN edge or a preferred temporary workaround until it is restored?

Thanks!

 

[leesteken]

This is intentional, and indeed unexpected given the existing threads about it. There is no HTTPS for the no-subscription (and test) repositories; use HTTP instead: https://pve.proxmox.com/pve-docs/pve-admin-guide.html#sysadmin_no_subscription_repo

 

[dmackdaddy]

Thanks! I was only having this issue in FL, seems to work fine in CA. Updating now!