Does this traceroute to download.proxmox.com look right?

VR_Architect

New Member
Dec 13, 2021
12
1
1
55
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?
Code:
root@FA010PVE:~# traceroute google.com
traceroute to google.com (172.217.3.78), 30 hops max, 60 byte packets
 1  10.0.0.1 (10.0.0.1)  0.124 ms  0.099 ms  0.083 ms
 2  192.168.0.1 (192.168.0.1)  0.979 ms  1.515 ms  1.720 ms
 3  71-208-31-254.ftmy.qwest.net (71.208.31.254)  599.736 ms  600.034 ms  602.675 ms
 4  75.160.84.9 (75.160.84.9)  600.165 ms  600.473 ms  600.270 ms
 5  nap-edge-04.inet.qwest.net (67.14.29.170)  608.603 ms  608.473 ms  608.702 ms
 6  65.123.232.94 (65.123.232.94)  609.047 ms  1067.237 ms  1077.704 ms
 7  108.170.249.1 (108.170.249.1)  591.583 ms  466.369 ms 108.170.249.17 (108.170.249.17)  469.091 ms
 8  142.250.58.103 (142.250.58.103)  470.492 ms 142.250.60.143 (142.250.60.143)  471.786 ms  474.697 ms
 9  mia07s54-in-f14.1e100.net (172.217.3.78)  471.550 ms  472.909 ms  474.547 ms

Code:
root@FA010PVE:~# traceroute download.proxmox.com
traceroute to download.proxmox.com (144.217.225.162), 30 hops max, 60 byte packets
 1  10.0.0.1 (10.0.0.1)  0.137 ms  0.116 ms  0.099 ms
 2  192.168.0.1 (192.168.0.1)  1.388 ms  0.753 ms  2.707 ms
 3  71-208-31-254.ftmy.qwest.net (71.208.31.254)  125.937 ms  128.812 ms  125.972 ms
 4  75.160.84.9 (75.160.84.9)  129.012 ms  129.689 ms  129.508 ms
 5  4.68.127.81 (4.68.127.81)  129.798 ms  132.628 ms  132.402 ms
 6  * * *
 7  be100-104.nwk-1-a9.nj.us (192.99.146.253)  183.157 ms  176.332 ms be100-155.nwk-5-a9.nj.us (198.27.73.29)  179.851 ms
 8  be102.bhs-g1-nc5.qc.ca (198.27.73.204)  185.585 ms be102.bhs-g2-nc5.qc.ca (192.99.146.138)  180.080 ms  185.802 ms
 9  * * *
10  * * *
11  * * *
12  * * *
13  * * *
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *
 

fabian

Proxmox Staff Member
Staff member
Jan 7, 2016
7,187
1,315
164
the trace looks okay (although your uplink seems to be quite high latency wise ;)).
 

VR_Architect

New Member
Dec 13, 2021
12
1
1
55
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 issues. Only an issue when trying to get it from the Proxmox servers (all of 20 them). The Proxmox servers are behind a dedicated on-metal pfSense firewall which is behind an ISP DSL modem. The servers have access to the internet and DNS. Just reinstalled version 7.1.2, and ntp install from another repository with no issues but still not able to access the Proxmox repository.


apt update results. Note the other repositories worked fine.
Code:
root@FA010PVE:~# apt update
Get:1 http://security.debian.org/debian-security bullseye-security InRelease [44.1 kB]
Get:2 http://ftp.debian.org/debian bullseye InRelease [116 kB]
Get:3 http://security.debian.org/debian-security bullseye-security/main amd64 Packages [99.5 kB]
Get:4 http://security.debian.org/debian-security bullseye-security/main Translation-en [62.2 kB]
Get:5 http://ftp.debian.org/debian bullseye-updates InRelease [39.4 kB]
Get:6 http://ftp.debian.org/debian bullseye/main amd64 Packages [8,180 kB]
Get:7 http://ftp.debian.org/debian bullseye/main Translation-en [6,241 kB]
Get:8 http://ftp.debian.org/debian bullseye/contrib amd64 Packages [50.5 kB]
Get:9 http://ftp.debian.org/debian bullseye/contrib Translation-en [46.9 kB]
Get:10 http://ftp.debian.org/debian bullseye-updates/main amd64 Packages [2,592 B]
Get:11 http://ftp.debian.org/debian bullseye-updates/main Translation-en [2,343 B]
Err:12 http://download.proxmox.com/debian/pve bullseye InRelease
  Connection failed [IP: 144.217.225.162 80]
Err:13 http://download.proxmox.com/debian/ceph-pacific bullseye InRelease
  Connection failed [IP: 144.217.225.162 80]
Fetched 14.9 MB in 2min 1s (123 kB/s)
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
All packages are up to date.
W: Failed to fetch http://download.proxmox.com/debian/pve/dists/bullseye/InRelease  Connection failed [IP: 144.217.225.162 80]
W: Failed to fetch http://download.proxmox.com/debian/ceph-pacific/dists/bullseye/InRelease  Connection failed [IP: 144.217.225.162 80]
W: Some index files failed to download. They have been ignored, or old ones used instead.

Curl with verbose:
Code:
root@FA023PVE:~# curl --verbose http://download.proxmox.com/debian/pve/dists/bullseye/InRelease
*   Trying 144.217.225.162:80...
* Connected to download.proxmox.com (144.217.225.162) port 80 (#0)
> GET /debian/pve/dists/bullseye/InRelease HTTP/1.1
> Host: download.proxmox.com
> User-Agent: curl/7.74.0
> Accept: */*
> 
* Recv failure: Connection reset by peer
* Closing connection 0
curl: (56) Recv failure: Connection reset by peer

WGET Results:
Code:
root@FA010PVE:~# wget http://download.proxmox.com/debian/pve/dists/bullseye/InRelease
--2021-12-14 09:26:10--  http://download.proxmox.com/debian/pve/dists/bullseye/InRelease
Resolving download.proxmox.com (download.proxmox.com)... 144.217.225.162, 2607:5300:203:7dc2::162
Connecting to download.proxmox.com (download.proxmox.com)|144.217.225.162|:80... connected.
HTTP request sent, awaiting response...

Ping Results:
Code:
root@FA010PVE:~# ping download.proxmox.com
PING na.cdn.proxmox.com (144.217.225.162) 56(84) bytes of data.
64 bytes from na.cdn.proxmox.com (144.217.225.162): icmp_seq=1 ttl=52 time=78.8 ms
64 bytes from na.cdn.proxmox.com (144.217.225.162): icmp_seq=2 ttl=52 time=78.6 ms

--- na.cdn.proxmox.com ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1002ms
rtt min/avg/max/mdev = 78.601/78.706/78.811/0.105 ms

/etc/apt/sources.list contents:
Code:
root@FA010PVE:~# cat /etc/apt/sources.list
#deb http://ftp.us.debian.org/debian bullseye main contrib
#deb http://ftp.us.debian.org/debian bullseye-updates main contrib
# security updates
#deb http://security.debian.org bullseye-security main contrib

deb http://ftp.debian.org/debian bullseye main contrib
deb http://ftp.debian.org/debian bullseye-updates main contrib
deb http://download.proxmox.com/debian/pve bullseye pve-no-subscription
# security updates
deb http://security.debian.org/debian-security bullseye-security main contrib
deb http://download.proxmox.com/debian/ceph-pacific bullseye main

/etc/apt/sources.list.d/pve-enterprise.list contents:
Code:
root@FA010PVE:~# cat /etc/apt/sources.list.d/pve-enterprise.list
#deb https://enterprise.proxmox.com/debian/pve bullseye pve-enterprise

1639573731768.png

I even added a firewall rule permit any traffic to the Proxmox repository IP address.
1639573764739.png


Thanks for the help everyone. I am hoping to move these server to a data center next week for production use.
 
Last edited:

VR_Architect

New Member
Dec 13, 2021
12
1
1
55
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 and all is good now. Now I can move to production.

My testing approach for others:
- connect serverA and serverB to a dumb hub and ssh between: worked
- connect serverA and serverB to a port on a single switch with a mtu 9000 (and all other switches turned off): worked
- looked as ip address on serverA/B to get mtu value, set mtu on switch to 1500 to match: failed
- remembered vlan's require some headroom so set mtu on switch to mtu 1525: worked
- so removed the mtu setting completely to leave at default value: worked

I am not sure why the mtu values are the same on the servers and switch it doesn't work. Seems like it should have. Oh well, lesson learned. This also fixed my issue with get the Proxmox repositories to work.

Hope this helps others.
 
  • Like
Reactions: Spirog

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get your own in 60 seconds.

Buy now!