Medibuntu

packages.medibuntu.org(88.191.82.11) unreachable

Asked by Lincoln Sternn

packages.medibuntu.org (88.191.82.11) is unreachable from 69.81.21.116. I can connect to medibuntu.org(87.98.242.110), but not the packages server.

Here is the relevent information from running "apt-get update":

Err http://packages.medibuntu.org hardy Release.gpg
  Could not connect to packages.medibuntu.org:80 (88.191.82.11), connection timed out
Err http://packages.medibuntu.org hardy/free Translation-en_US
  Unable to connect to packages.medibuntu.org http:
Err http://packages.medibuntu.org hardy/non-free Translation-en_US
  Unable to connect to packages.medibuntu.org http:
Reading package lists... Done
W: Failed to fetch http://packages.medibuntu.org/dists/hardy/Release.gpg Could not connect to packages.medibuntu.org:80 (88.191.82.11), connection timed out

W: Failed to fetch http://packages.medibuntu.org/dists/hardy/free/i18n/Translation-en_US.bz2 Unable to connect to packages.medibuntu.org http:

W: Failed to fetch http://packages.medibuntu.org/dists/hardy/non-free/i18n/Translation-en_US.bz2 Unable to connect to packages.medibuntu.org http:

Question information

Language:
English Edit question
Status:
Solved
For:
Medibuntu Edit question
Assignee:
No assignee Edit question
Solved by:
Lincoln Sternn
Solved:
Last query:
Last reply:
Revision history for this message
Maxence DUNNEWIND (maxenced) said : 		#1

One of the server seems to be saturated. I update the cluster config at the moment, it should solve the problem. Let me know if you still have the problem in a few minutes/hours.

Cheers,

Maxence

Revision history for this message
Lincoln Sternn (sternnspam) said : 		#2

I am still timing out when attempting to connect to packages.medibuntu.org.

Revision history for this message
Lincoln Sternn (sternnspam) said : 		#3

I am still unable to connect directly to packages.medibuntu.org from my public IP of 69.81.21.116. I can connect if I go through a web proxy (www.hidemyass.com). Am I within a blocked range of IP addresses?

Revision history for this message
Lincoln Sternn (sternnspam) said : 		#4

I have resolved the problem. The packages server was within a range of IPs that my firewall was blocking.

Revision history for this message
tx (372046933-qq) said : 		#5

I wonder why the following happened simultaneously
PING package.medibuntu.org (218.83.175.155) 56(84) bytes of data.
64 bytes from 218.83.175.155: icmp_seq=1 ttl=250 time=247 ms
64 bytes from 218.83.175.155: icmp_seq=2 ttl=250 time=89.7 ms
64 bytes from 218.83.175.155: icmp_seq=3 ttl=250 time=35.2 ms

W: Failed to fetch http://packages.medibuntu.org/dists/lucid/Release.gpg Could not connect to packages.medibuntu.org:80 (88.191.82.11). - connect (110: Connection timed out)

Revision history for this message
rifter (rifter0x0000) said : 		#6

The servers are down; Covered in the following bug: https://bugs.launchpad.net/medibuntu/+bug/565810

You can use the official backend: https://bugs.launchpad.net/medibuntu/+bug/565810/comments/12
Or a mirror:
https://bugs.launchpad.net/medibuntu/+bug/565810/comments/6
https://bugs.launchpad.net/medibuntu/+bug/565810/comments/7
https://bugs.launchpad.net/medibuntu/+bug/565810/comments/8