Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm relatively new to server management and I have a home development server running a LAMP stack on Ubuntu Server version 12.10.

I'm trying to download a git repository using Putty via the following command:


However when doing this the server is unable to connect and times out.

What I've noticed though is if then try to ping it responds as normal, and then if I try the above command again it works fine for a few minutes again until it starts to time out all over again.

The only other site I've noticed this occur on is

share|improve this question

closed as off topic by mdpc, Shane Madden, Michael Hampton, mgorven, Tom O'Connor Dec 26 '12 at 12:34

Questions on Server Fault are expected to relate to server, networking, or related infrastructure administration within the scope defined by the community. Consider editing the question or leaving comments for improvement if you believe the question can be reworded to fit within the scope. Read more about reopening questions here.If this question can be reworded to fit the rules in the help center, please edit the question.

I don't see anything wrong with your wget command (works for me!). Maybe you should review your firewall settings. – Grumpy Dec 24 '12 at 5:54
"I'm trying to download a git repository via SSH" - no, you're not. You are trying to download via https. Wget doesn't do ssh. – EEAA Dec 24 '12 at 6:28
@EEAA Thank you for pointing that out, this has now been corrected. – Big Joe Dec 24 '12 at 15:03
Were you trying to do this during github's maintenance the other day? – Michael Hampton Dec 24 '12 at 16:03
up vote 0 down vote accepted

After a bit of digging I seem to have found the problem, it looks like it's a nameserver issue as described here

Changing my server's DNS to use Google's (located in /etc/network/interfaces) appeared to solve the problem after a restart using sudo /etc/init.d/networking restart.

share|improve this answer

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