GITHUB setup - no address associated with name

Question

I\'m trying to setup GitHub on my system and I have done all the installation and key setup process:

But during test everything phase getting the following error by

Answer 1

I had the same error message. In my case my netbook's wifi switch got bumped and I didn't notice I had no internet connection. So make sure you have internet access if you're getting this error! (duh!)

Answer 2

I have a client who developed this problem after a Windows 10 update. After a great amount of web searches and trouble shooting, I noticed that his Windows User ID contained spaces, and the error message had said, "S no address associated with name". I noticed that after the space in his name was his middle initial, "S". So I postulated that the user ID was being passed without quotes and was terminating at the first space.

To test my theory, I created a new user ID with no spaces and ran NX Client 3.5.0-7 and it worked.

This also corrected a problem that sprung up with X2Go.

The short answer is, you must not have any spaces in your user name or both NX Client and X2Go will fail.

Answer 3

If you are working behind proxy, try config ssh to work with the proxy, I encountered the same problem at first and used corkscrew to solve it: http://www.mtu.net/~engstrom/ssh-proxy.php

Answer 4

It means it doesn't found your HOME/.ssh/id_rsa and id_rsa.pub, and is looking for a HOME/.ssh/config file which could have defined the name 'github.com', as illustrated here.

That usually means you don't have defined what HOME is (which isn't defined by default on Windows, see this answer)

Answer 5

I also faced the same problem and the error was that: I was using the wrong URI, it should be like:

ssh -T git@bitbucket.org

and not as what was copied for cloning

ssh -T git@bitbucket.org:username/repo.git

Answer 6

I tried almost everything found on Google related to this question, and nothing seemed to work. I remembered that Windows has made some updates on 'Windows Defender'. I may seem irrelevant but it is not;

What worked for me was running Git as Administrator, which i never did before.