Hello there! I'm having the same problem right now. It says that upgrade will take 3 days. I upgraded yesterday on another machine and was very fast. Maybe we have problems with the upgrade servers today?
# pveam download local debian-13-standard_13.1-2_amd64.tar.zst
downloading http://download.proxmox.com/images/system/debian-13-standard_13.1-2_amd64.tar.zst to /var/lib/vz/template/cache/debian-13-standard_13.1-2_amd64.tar.zst
--2025-10-24 22:42:32-- http://download.proxmox.com/images/system/debian-13-standard_13.1-2_amd64.tar.zst
Resolving download.proxmox.com (download.proxmox.com)... 66.70.154.82, 2a0b:7140:8:100::90
Connecting to download.proxmox.com (download.proxmox.com)|66.70.154.82|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 129710398 (124M) [application/octet-stream]
Saving to: '/var/lib/vz/template/cache/debian-13-standard_13.1-2_amd64.tar.zst.tmp_dwnl.113946'
0K ........ ........ ........ ........ 25% 184K 8m30s
# host -a download.proxmox.com
Trying "download.proxmox.com"
Host download.proxmox.com not found: 4(NOTIMP)
Received 38 bytes from 192.168.10.1#53 in 26 ms
# host download.proxmox.com
download.proxmox.com is an alias for download.cdn.proxmox.com.
download.cdn.proxmox.com is an alias for br.sa.cdn.proxmox.com.
br.sa.cdn.proxmox.com is an alias for na2.cdn.proxmox.com.
na2.cdn.proxmox.com has address 170.130.165.90
na2.cdn.proxmox.com has IPv6 address 2a0b:7140:8:100::90
# nslookup download.proxmox.com
Server: 192.168.10.1
Address: 192.168.10.1#53
Non-authoritative answer:
download.proxmox.com canonical name = download.cdn.proxmox.com.
download.cdn.proxmox.com canonical name = br.sa.cdn.proxmox.com.
br.sa.cdn.proxmox.com canonical name = na.cdn.proxmox.com.
Name: na.cdn.proxmox.com
Address: 66.70.154.82
Name: na.cdn.proxmox.com
Address: 2607:5300:400:7d00::80
# ping na.cdn.proxmox.com
PING na.cdn.proxmox.com (66.70.154.82) 56(84) bytes of data.
64 bytes from na.cdn.proxmox.com (66.70.154.82): icmp_seq=1 ttl=49 time=152 ms
64 bytes from na.cdn.proxmox.com (66.70.154.82): icmp_seq=2 ttl=49 time=146 ms
64 bytes from na.cdn.proxmox.com (66.70.154.82): icmp_seq=3 ttl=49 time=145 ms
64 bytes from na.cdn.proxmox.com (66.70.154.82): icmp_seq=4 ttl=49 time=146 ms
64 bytes from na.cdn.proxmox.com (66.70.154.82): icmp_seq=5 ttl=49 time=146 ms
^C
--- na.cdn.proxmox.com ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4002ms
rtt min/avg/max/mdev = 145.445/146.796/151.598/2.402 ms
42% [1 pve-qemu-kvm 17.7 MB/32.1 MB 55%] 2,467 B/s 3h 29min 58s
I noticed this one earlier:which CDN node are you connected to?
Connection timed out [IP: 117.120.5.231 80]
If you feel that is absolutely necessary towards solving the issue, I could DM/PM that to you personally.could you also tell us where you are located (and possibly your ISP?)
55% [1 pve-qemu-kvm 25.6 MB/32.1 MB 80%] 6,281 B/s 1h 1min 31s
I should be covered in the EMEA region.CDN nodes running in the APAC region
The IP address 117.120.5.231 is located in China and is associated with the organization CNC Group (China Netcom)
This is the APAC CDN node I talked about. Maybe the geolocation of your IP is outdated in the geoip DB we use, you could submit a correction request at the source of that:However, a lookup (Google) of that above posted IP 117.120.5.231 shows:
The IP address 117.120.5.231 is located in China and is associated with the organization CNC Group (China Netcom)That looks interesting/worrying?
We use essential cookies to make this site work, and optional cookies to enhance your experience.