I want to update my Raspberry Pi, but I was not successful. This is the message when I try to update my device:

> pi@raspberrypi ~ $ sudo apt-get update
     Errhttp://mirrordirector.raspbian.org wheezy Release.gpg   Could not
    > connect to (, connection timed out
    > Err http://archive.raspberrypi.org wheezy Release.gpg   Could not
    > connect to (, connection timed out
    > Err http://raspberrypi.collabora.com wheezy Release.gpg   Could not
    > connect to (, connection timed out
    > Err http://repository.wolfram.com stable Release.gpg   Could not
    > connect to (, connection timed out
    > Reading package lists... Done W: Failed to fetch
    > http://mirrordirector.raspbian.org/raspbian/dists/wheezy/Release.gpg 
    > Could not connect to (, connection
    > timed out
    > W: Failed to fetch
    > http://raspberrypi.collabora.com/dists/wheezy/Release.gpg  Could not
    > connect to (, connection timed out
    > W: Failed to fetch
    > http://archive.raspberrypi.org/debian/dists/wheezy/Release.gpg  Could
    > not connect to (, connection timed
    > out
    > W: Failed to fetch
    > http://repository.wolfram.com/raspbian/dists/stable/Release.gpg  Could
    > not connect to (, connection timed
    > out
    > W: Some index files failed to download. They have been ignored, or old
    > ones used instead

How can I solve this?

  • 1
    Looks like your networking isn't happy? Plugged in over Ethernet or wifi USB stick? Do you have bog-standard IP addressing over DHCP i.e. you have a home hub that automatically allocates IP addresses? Can you access the internet from your hub through the browser?
    – sarin
    Feb 19, 2015 at 9:13
  • 1
    Did it work before? Do other network connections work? Maybe the repo is just down now and it will work again in an hour or two.
    – Ghanima
    Feb 19, 2015 at 9:18
  • @sarin Plugged in over wifi USB stick and i have a statick IP addresses. Also i can ping to google.com and access the internet from the browser Feb 19, 2015 at 9:20
  • @Ghanima Yes, it worked but in 2 days didn't work. Feb 19, 2015 at 9:21
  • If your pi is plugged in and you can ping external addresses successfully then the issue feels like it's external. Although the error messages seem suspicious as all the sites are resolving to the same odd IP address despite having different domains. I would try hardwiring your ethernet and running the update just to rule out any wifi/usb issues (although they are unlikely given you can ping external hosts)
    – sarin
    Feb 19, 2015 at 9:31

2 Answers 2


Find out if you have a proxy server configured for APT (you output looks as if you are trying to use as a proxy):

  • In /etc/apt/apt.conf there may be something looking like this: Aquire::http::Proxy:: "";
  • In the shell, you may find export http_proxy= in one of the following files:


If you find a proxy config somewehere, make sure that it is up and forwariding connections. Remove the proxy configurations if you can access the external server directly

  • This an interesting theory (+1), but I don't think raspbian would have configured this IP as a proxy. It could be some kind of problem with DNS resolution.
    – goldilocks
    Feb 19, 2015 at 13:07
  • DNS would be another possibility. In this case, the port 8080 points straight toward „web proxy“ as a keyword and any IP address containing several „1“ digits may come up as proxy/hotspot/web gateway address. Thinking about it, this may also be a web gateway that redirects web access to a web page with a form to authenticate the IP address. It would then allow direct WWW access after the authentication has been done. Feb 19, 2015 at 13:57
  • Maybe you are right after all: Looks like the owner of the IP (KDDI, a Japanese telecommunications corp.) hosts a mirror for fedora, so they could be involved with debian or raspbian as well.
    – goldilocks
    Feb 19, 2015 at 14:08

This is either a proxy or DNS issue.

  • Try: nslookup mirrordirector.raspbian.org or if dnstools is not installed, try ping mirrordirector.raspbian.org and see what it resolves to.
  • If it resolves to it isn't a DNS problem, if it doesn't, something is messing with DNS.
  • If that doesn't narrow it down, try wget
    output should be

--2016-09-12 10:05:45-- http://mirrordirector.raspbian.org/favicon.ico Resolving mirrordirector.raspbian.org (mirrordirector.raspbian.org)..., 2001:41c9:1:3ce::11 Connecting to mirrordirector.raspbian.org (mirrordirector.raspbian.org)||:80... connected. HTTP request sent, awaiting response... 200 OK Length: 1150 (1.1K) [image/vnd.microsoft.icon] Saving to: `favicon.ico'

100%[===========================================================================>] 1,150 --.-K/s in 0s

2016-09-12 10:05:50 (9.54 MB/s) - `favicon.ico' saved [1150/1150]

  • If there is a proxy, you will see a redirect here or some sort of weirdness.
  • If neither of those narrow things down, try adding some other mirrors: sudo nano /etc/apt/sources.list

set to:

deb http://mirrordirector.raspbian.org/raspbian/ wheezy main contrib non-free rpi firmware
deb http://archive.raspbian.org/raspbian/ wheezy main contrib non-free
deb-src http://archive.raspbian.org/raspbian/ wheezy main contrib non-free
deb http://mirror.umd.edu/raspbian/raspbian/ wheezy main contrib non-free
deb http://reflection.oss.ou.edu/raspbian/raspbian/ wheezy main contrib non-free

and try sudo apt-get update again.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge that you have read and understand our privacy policy and code of conduct.

Not the answer you're looking for? Browse other questions tagged or ask your own question.