apt-get update connection failed

S

surfsaint

New Member
Dec 13, 2022
6
0
1
Hello,

I can't seem to update proxmox, I have configured proxmox sources with pve-no-subscription. I have also disabled IPv6. I am able to get to eh download.proxmox.com via the browser on the same network this server is on. I have also disabled the firewall on the server. Am I missing something?


apt-get update
Hit:1 http://deb.debian.org/debian bullseye InRelease
Hit:2 http://deb.debian.org/debian bullseye-updates InRelease
Hit:3 http://security.debian.org/debian-security bullseye-security InRelease
Hit:4 http://deb.debian.org/debian bullseye-backports InRelease
Err:5 http://download.proxmox.com/debian/pve bullseye InRelease
Connection failed [IP: 144.217.225.162 80]
Reading package lists... Done
W: Failed to fetch http://download.proxmox.com/debian/pve/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.

Thanks for the help and guidance,

-Frazer
 
I updated my host file with

51.91.38.34 download.proxmox.com

and apt-get update started to work... is there something wrong with the server at 144.217.225.162?
 
@surfsaint if the problem persists, try tracerouting the server to see where the connection stops.. it might be routing issue between your ISP and ours (or some other network issue on your end).
 
YungErrorHunter said:
Accessing http://144.217.225.162 works for me in the browser.
If you run curl 'http://144.217.225.162' within a shell of your proxmox server, does it work and show the root directory?
Click to expand...
Hi,

Yes, i am able to get to the root directory

curl 'http://144.217.225.162'
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1">
<title>unknown Website Blocked</title>
<style>
body {
font-family: Arial, Helvetica, sans-serif;
font-size: 12px;
 
surfsaint said:
unknown Website Blocked
Click to expand...
No, you are not. You should find out whats blocking the website. Maybe you got some filtering DNS server like pihole/adguard running or a hardware firewall with blocklists?
 
Last edited:
fabian said:
@surfsaint if the problem persists, try tracerouting the server to see where the connection stops.. it might be routing issue between your ISP and ours (or some other network issue on your end).
Click to expand...
hello,

here is the traceroute from the server. it goes out of our network. I have the traceroute of the IP (51.91.38.34) that works below too..

traceroute 144.217.225.162
traceroute to 144.217.225.162 (144.217.225.162), 30 hops max, 60 byte packets
1 172.28.115.1 (172.28.115.1) 3.062 ms 3.124 ms 3.260 ms
2 172.28.119.242 (172.28.119.242) 0.129 ms 0.121 ms 0.113 ms
3 172.28.119.249 (172.28.119.249) 5.399 ms 5.495 ms 5.596 ms
4 172.30.251.121 (172.30.251.121) 0.552 ms 0.654 ms
5 172.30.251.113 (172.30.251.113) 0.784 ms
6 172.30.1.77 (172.30.1.77) 0.530 ms 172.30.1.73 (172.30.1.73) 0.652 ms 0.803 ms
7 172.30.250.81 (172.30.250.81) 1.257 ms 1.283 ms
8 172.30.250.85 (172.30.250.85) 1.196 ms
9 192.168.7.233 (192.168.7.233) 1.779 ms 1.514 ms 1.657 ms
10 206.121.35.29 (206.121.35.29) 8.023 ms 7.470 ms 7.291 ms
11 12.122.116.54 (12.122.116.54) 12.175 ms 12.129 ms 12.052 ms
12 12.122.116.1 (12.122.116.1) 7.456 ms 11.913 ms 8.514 ms
13 gar3.rcmva.ip.att.net (12.122.135.173) 7.441 ms 4.585 ms 4.575 ms
14 wshdc401me9.ip.att.net (12.122.85.21) 4.408 ms 5.971 ms 5.995 ms
15 cr1.wswdc.ip.att.net (12.122.113.54) 5.123 ms 5.132 ms wshdc81crs.ip.att.net (12.122.85.22) 7.705 ms
16 wswdc22crs.ip.att.net (12.122.135.250) 5.016 ms cr82.wshdc.ip.att.net (12.122.135.174) 11.849 ms wswdc22crs.ip.att.net (12.122.135.250) 4.506 ms
17 12.122.113.41 (12.122.113.41) 7.374 ms gar3.rcmva.ip.att.net (12.122.134.185) 6.659 ms 6.453 ms
18 195.22.206.54 (195.22.206.54) 5.728 ms 6.021 ms 6.084 ms
19 195.22.206.1 (195.22.206.1) 6.543 ms 6.211 ms 6.118 ms
20 be107.was-dc10-pb2-nc5.va.us (142.44.208.252) 5.800 ms 5.659 ms 5.541 ms
21 * * *
22 * * *
23 * * *
24 * * *
25 be102.bhs-g2-nc5.qc.ca (192.99.146.138) 55.629 ms 19.251 ms be102.bhs-g1-nc5.qc.ca (198.27.73.204) 18.382 ms
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *


traceroute 51.91.38.34
traceroute to 51.91.38.34 (51.91.38.34), 30 hops max, 60 byte packets
1 ufs70-1.roh.kp.org (172.28.115.1) 3.071 ms 3.145 ms 3.256 ms
2 172.28.119.242 (172.28.119.242) 0.141 ms 0.131 ms 0.123 ms
3 172.28.119.249 (172.28.119.249) 3.417 ms 3.473 ms 3.575 ms
4 172.30.251.125 (172.30.251.125) 0.508 ms
5 172.30.251.121 (172.30.251.121) 0.634 ms
6 172.30.251.117 (172.30.251.117) 0.590 ms
7 172.30.1.77 (172.30.1.77) 0.488 ms 172.30.1.69 (172.30.1.69) 0.512 ms 172.30.1.65 (172.30.1.65) 0.663 ms
8 172.30.250.85 (172.30.250.85) 1.225 ms 172.30.250.81 (172.30.250.81) 1.219 ms 172.30.250.85 (172.30.250.85) 1.174 ms
9 192.168.7.233 (192.168.7.233) 1.941 ms 2.040 ms 1.838 ms
10 206.121.35.29 (206.121.35.29) 3.526 ms 3.581 ms 3.531 ms
11 12.122.116.54 (12.122.116.54) 7.462 ms 7.479 ms 7.304 ms
12 12.122.116.1 (12.122.116.1) 9.324 ms 11.399 ms 7.418 ms
13 gar3.rcmva.ip.att.net (12.122.135.173) 9.734 ms 11.925 ms 9.752 ms
14 wshdc401me9.ip.att.net (12.122.85.21) 4.509 ms 4.577 ms 4.683 ms
15 wshdc81crs.ip.att.net (12.122.85.22) 4.057 ms cr1.wswdc.ip.att.net (12.122.113.54) 6.926 ms wshdc81crs.ip.att.net (12.122.85.22) 6.512 ms
16 wswdc22crs.ip.att.net (12.122.135.250) 5.932 ms cr82.wshdc.ip.att.net (12.122.135.174) 4.476 ms wswdc22crs.ip.att.net (12.122.135.250) 9.694 ms
17 gar3.rcmva.ip.att.net (12.122.134.185) 6.129 ms 12.122.113.41 (12.122.113.41) 5.942 ms gar3.rcmva.ip.att.net (12.122.134.185) 8.064 ms
18 195.22.206.54 (195.22.206.54) 5.398 ms 5.346 ms 5.463 ms
19 195.22.206.1 (195.22.206.1) 9.799 ms 8.230 ms 7.192 ms
20 be107.was-dc10-pb2-nc5.va.us (142.44.208.252) 5.883 ms 5.848 ms 5.695 ms
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
 
Dunuin said:
No, you are not. You should find out whats blocking the website. Maybe you got some filtering DNS server like pihole/adguard running or a hardware firewall with blocklists?
Click to expand...
sorry, i didn't notice the Blocked site, but how come the other IP that works.... also is blocked... This is the IP i was able to do the update from. There's more to both outputs, i just truncated. thanks.


curl 'http://51.91.38.34'
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1">
<title>unknown Website Blocked</title>
<style>
body {
font-family: Arial, Helvetica, sans-serif;
font-size: 12px;
 
Last edited:
do you have a proxy or some sort of "network security" box configured?
 
We have a firewall, but that is open to connect and was able to connect previously. I was just not able to connect recently, last time I connected was a few months ago.
 
well the response you get is clearly tampered with by some system, and it's not our CDN..
 
You must log in or register to reply here.

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!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

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 yours easily in our online shop.

Buy now!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom
Back