I have OVS and LACP working with bonds but the manual says RSTP doesn't work with bonds. Yet, the manual confusingly says LACP is preferred. So I have not tried RSTP.
I solved the issue. The mtu's (1500) were matched between the Dell switches and Proxmox servers, but didn't work. When I increased to mtu 1525 on the switches everything worked. As a ping doesn't fill the 1500 limit it didn't show the issue. So I removed all mtu configurations from the switches...
My download speed is about 9Mb and upload is 0.5Mb. Just wondering is the upload speed important? I was able to update 4 servers last month on this same connection. Curl shows the connection being closed by the peer (see below).
I was able to get the file via a browser from my desktop with no...
My pfSense is a physical separate server. I am able to run updates to other repositories just not the Proxmox one. I was able to install ifupdown2 and ntp fine. I did a remote IP resolution for the repository and got 51.91.38.34 (fr.cdn.proxmox.com). On my server the IP is 144.217.225.162
I...
I am having issues getting the repository for Proxmox to work for me when all other repositories seem to work fine. I did a traceroute from the server to google.com and to download.proxmox.com as a shot in the dark. Does the hops look correct?
root@FA010PVE:~# traceroute google.com
traceroute...
I decided to reinstall one of the servers to the latest version 7.2 and after changing the repositories I ran apt-update. Note that the update can get the files from the ftp.debian.org and security.debian.org sites, but not the download.proxmox.com site. So my routing and connection to the...
Thank you for the help. I can ping the url from the server I can ping google.com so seems DNS is working (using 1.1.1.1). When it tries to get that file I see it flash 10min to download, but goes away.
Trying to upgrade from 7.0 to 7.1 and it is failing on reading the headers from proxmox website. I have the correct non-subscription deb's. I noticed if I use the browser to go to the repository url, the amd64 folder is called "binary-amd64". Could this be the issue? The folder should be called...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.