[SOLVED] enterprise.proxmox.com unreachable

ejmerkel

Well-Known Member
Sep 20, 2012
117
4
58
I am setting up a new node and have installed the valid subscription but when I try to do an apt update, I get enterprise.proxmox.com 144.217.225.162 connection timed out.

Is the proxmox enterprise repository down? Guessing it might be related to the OVH data center fires yesterday in Strasbourg?

Best regards,
Eric
 
All services are up and running.

We have multiple download servers in our cdn, also one in a OVH datacenter (in Roubaix, so not affected by the fire in Strasbourg).
 
I am still seeing the same issue today. The license says it is Active and next due date is in 2022 so pretty sure it is not a license issue. I forced a re-issue of the license and then tried the following:

Via the gui ...

Code:
starting apt-get update
Get:1 http://security.debian.org buster/updates InRelease [65.4 kB]
Hit:2 http://ftp.us.debian.org/debian buster InRelease
Hit:3 http://ftp.us.debian.org/debian buster-updates InRelease
Err:4 https://enterprise.proxmox.com/debian/pve buster InRelease
  Cannot initiate the connection to enterprise.proxmox.com:443 (2607:5300:203:7dc2::162). - connect (101: Network is unreachable) Could not connect to enterprise.proxmox.com:443 (144.217.225.162), connection timed out
Fetched 65.4 kB in 30s (2143 B/s)
Reading package lists...
W: Failed to fetch https://enterprise.proxmox.com/debian/pve/dists/buster/InRelease  Cannot initiate the connection to enterprise.proxmox.com:443 (2607:5300:203:7dc2::162). - connect (101: Network is unreachable) Could not connect to enterprise.proxmox.com:443 (144.217.225.162), connection timed out
W: Some index files failed to download. They have been ignored, or old ones used instead.
TASK OK

From the command line I tried forcing it to IPv4 thinking it might be an IPv6 issue.

Code:
# apt-get -o Acquire::ForceIPv4=true update
Hit:1 http://security.debian.org buster/updates InRelease
Hit:2 http://ftp.us.debian.org/debian buster InRelease
Hit:3 http://ftp.us.debian.org/debian buster-updates InRelease
Err:4 https://enterprise.proxmox.com/debian/pve buster InRelease
  Could not connect to enterprise.proxmox.com:443 (144.217.225.162), connection timed out
Reading package lists... Done                             
W: Failed to fetch https://enterprise.proxmox.com/debian/pve/dists/buster/InRelease  Could not connect to enterprise.proxmox.com:443 (144.217.225.162), connection timed out
W: Some index files failed to download. They have been ignored, or old ones used instead.

I cannot ping this server.

ping 144.217.225.162
PING 144.217.225.162 (144.217.225.162) 56(84) bytes of data.
^C
--- 144.217.225.162 ping statistics ---
40 packets transmitted, 0 received, 100% packet loss, time 39895ms

Is there a way to force it to try a different download server?

I do see there are some updates out there from the regular repository. Should I process those and try again?

Thanks!

Best regards,
Eric
 
For me that host works, but for at least 10 days, there is no new update for my system. Neither Linux or ProxMox update, everytime when i try (or system itself) there is no updates:

1615563685753.png

Little bit strange :)
 

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

Buy now!