Horrifically slow download speeds for download.proxmox.com?

[Tmanok]

Hi Everyone, Hey PVE Staff,

Is it just me, or are the web servers for download.proxmox.com unbelievably slow? I'm updating a PBS instance after several months and realizing it will take hours.... This is naturally, inconveniently interfering with a maintenance window. Shame on me for not updating it sooner perhaps. But I am shocked by how slow this is. 20-40KB/s... :O

This is from a business fiber connection on Vancouver Island. I am used to seeing >10MB/s (80Mbps) on downloads even from popular servers, maybe 1MB/s from European servers. Dear PVE Developers / Staff: Please let me know if the no-subscription repository requires a North American mirror, I will volunteer one (i.e. for free) in 2027 outside of the Cascadia Earthquake zone in Kelowna.

Thanks!


Tmanok

 

[t.lamprecht]

Please check which specific IP of download.proxmox.com your PVE host resolves too, e.g. just using ping or dig or the like, as with that we can determine if your source IP gets correctly geoip-mapped and thus actually uses one of our north american CDN mirror hosts.

 

[h@rald]

Had a similar experience when trying to download updates for our cluster in China.
I ended up singeling out the IP address for the Proxmox CDN in Singapore and added that IP address to the /etc/hosts file. (each host)
I basically pinned the single IP in Singapore to download.proxmox.com.
Yes, its going to be a problem if the CDN decides to host from a differen IP, but this was a good way for me to make sure we always use that repository.

Tip, I now use the proxmox-offline-mirror tool to grab all the updates of the internet (debian and proxmox) and accumulate them locally, I serve them back to the LAN using Nginx and all my Proxmox nodes use this internal repository to update themselves.
This way updates are only downloaded once, and it does not really matter how long it takes to download.
Updating the Proxmox nodes goes as fast as your LAN will go, since they use the internal repo.
This makes the maintenance window for updating a proxmox node as small as it could possibly be.
I loose more time enabling and disabling maintenance mode via CLI then I do actually updating
(Lets get that 'maintenance mode' button in the GUI, pretty please...)