ssh: Could not resolve hostname github.com: Name or service not known; fatal: The remote end hung up unexpectedly

Git

Git Problem Overview


The process of setting up a GitHub account works just fine but it doesn't work when I try pushing my repository to GitHub. The error message it shows is as follows:

ssh: Could not resolve hostname github.com: Name or service not known
fatal: The remote end hung up unexpectedly

I have tried changing RSA keys and all but still getting error.

What causes this error?

Git Solutions


Solution 1 - Git

Recently, I have seen this problem too. Below, you have my solution:

  1. ping github.com, if ping failed. it is DNS error.
  2. sudo vim /etc/resolv.conf, the add: nameserver 8.8.8.8 nameserver 8.8.4.4

Or it can be a genuine network issue. Restart your network-manager using sudo service network-manager restart or fix it up

Solution 2 - Git

I have just received this error after switching from HTTPS to SSH (for my origin remote). To fix, I simply ran the following command (for each repo):

ssh -T [email protected]

Upon receiving a successful response, I could fetch/push to the repo with ssh.

I took that command from Git's Testing your SSH connection guide, which is part of the greater Connecting to GitHub with with SSH guide.

Solution 3 - Git

Github is currently (on 22nd of feb 2012, again on 5th of sept 2016) having some problems with pushing/pulling over ssh. I'm experiencing the same problems.

Pulling over https is working thought.

You can try pushing over https by following this guide: https://help.github.com/articles/using-ssh-over-the-https-port/

This would only help if https is not affected. you can try if https://status.github.com/ shows signs of things slowing down. enter image description here Graphs where the mean response time goes up means there are issues (or possibly a DDOS) at github, and not at your end.

If github is currently being DDOS'ed they may choose to enable DDOS protection from a 3rd party. This would mean they change their dns records and/or servers if these are part of the DDOS.

Flushing your dns, changing your dns server or restarting your network (which will possibly flush your dns cache) as stated in the other answer might help in fixing the issue for you if github is mitigating a DDOS.

Or if you have problems with your ssh setup you can find the ssh faq here: http://help.github.com/ssh-issues/

Other ways to flush your dns, in windows in your terminal

ipconfig /flushdns

on macos

dscacheutil -flushcache

on linux

service nscd restart

or simply rebooting ;)

Solution 4 - Git

In my case I had misspelled something when manually adding the remote origin with git remote add origin ....

It's worth checking your remote is correct with git remote -v

Solution 5 - Git

Each of this could help

  1. Confirm if you are still connected using ssh. Type this: ssh -T [email protected]

If you get the message that you were successfully authenticated and that github doesn't suppoet shell access then you can trying pushing your code again.

2)Create a new ssh key, add it to github and test it using ssh -T [email protected]

Solution 6 - Git

If you use Windows 10 and you are facing this error, try using ssh -T [email protected] to authenticate again to Github. It worked like charm for me.

Solution 7 - Git

Sometimes restarting your machine is also a good idea. When I faced the same issue after restarting the system, it told me that your private key is locked and github cant access that.. so enter your password to do that.. I entered the password and then the issue was resolved.

Solution 8 - Git

You can check which the key is being used by trying to connect to [email protected]:

$ ssh -vT [email protected]
> ...
> debug1: identity file /Users/you/.ssh/id_rsa type -1
> debug1: identity file /Users/you/.ssh/id_rsa-cert type -1
> debug1: identity file /Users/you/.ssh/id_dsa type -1
> debug1: identity file /Users/you/.ssh/id_dsa-cert type -1
> ...
> debug1: Authentications that can continue: publickey
> debug1: Next authentication method: publickey
> debug1: Trying private key: /Users/you/.ssh/id_rsa
> debug1: Trying private key: /Users/you/.ssh/id_dsa
> debug1: No more authentication methods to try.
> Permission denied (publickey).

In that example, we did not have any keys for SSH to use. The "-1" at the end of the "identity file" lines means SSH couldn't find a file to use. Later on, the "Trying private key" lines also indicate that no file was found. If a file existed, those lines would be "1" and "Offering public key", respectively:

$ ssh -vT [email protected]
> ...
> debug1: identity file /Users/you/.ssh/id_rsa type 1
> ...
> debug1: Authentications that can continue: publickey
> debug1: Next authentication method: publickey
> debug1: Offering RSA public key: /Users/you/.ssh/id_rsa
Verify the public key is attached to your account

You must provide your public key to GitHub to establish a secure connection.

  1. Open Terminal.

  2. Start SSH agent in the background.

    $ eval "$(ssh-agent -s)" > Agent pid 59566

  3. Find and take a note of your public key fingerprint.

    $ ssh-add -l -E sha256 > 2048 SHA256:274ffWxgaxq/tSINAykStUL7XWyRNcRTlcST1Ei7gBQ /Users/USERNAME/.ssh/id_rsa (RSA)

  4. In the upper-right corner of any github page, click your profile photo, then click Settings.

  5. In the user settings sidebar, click SSH and GPG keys.

  6. Compare the list of SSH keys with the output from the ssh-add command.

  7. If you don't see your public key in GitHub, you'll need to add your SSH key to GitHub to associate it with your computer.

Follow this link for details

Solution 9 - Git

I was having this exact issue and all that I had to do was to restart my desktop

Solution 10 - Git

On centos 7

  1. check ip address using command ifconfig. you will get information like this

     ens33: flags=****<UP,BROADCAST,RUNNING,MULTICAST>  mtu ****
    
     inet ***.***.***.***  netmask ***.***.***.0  broadcast ***.***.***.***
    
  2. add inet ip address and hostname in file /etc/hosts

a. open file vi /etc/hosts

b. add ip and host like ip_address hostname hostname

  1. reboot

It will attach ip and host.

Solution 11 - Git

I was having the same issue, tried all the methods nothing worked.

then realized my VPN was on.

if you too have a VPN turned on try switching off your VPN and retry.

I was using Cloudflare VPN.

Solution 12 - Git

If ping github.com gives below error: ping: cannot resolve github.com: Unknown host

Kindly wait for couple of minutes and then try again.

Attributions

All content for this solution is sourced from the original question on Stackoverflow.

The content on this page is licensed under the Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) license.

Content TypeOriginal AuthorOriginal Content on Stackoverflow
QuestionNeel PathakView Question on Stackoverflow
Solution 1 - GitQiangksView Answer on Stackoverflow
Solution 2 - GitToddView Answer on Stackoverflow
Solution 3 - GitJens TimmermanView Answer on Stackoverflow
Solution 4 - GitSkylar BrownView Answer on Stackoverflow
Solution 5 - GitOnyejiaku Theodore KelechukwuView Answer on Stackoverflow
Solution 6 - GitKhaled AdraniView Answer on Stackoverflow
Solution 7 - GitNamrataView Answer on Stackoverflow
Solution 8 - GitexanView Answer on Stackoverflow
Solution 9 - GitCarlosView Answer on Stackoverflow
Solution 10 - GitBirbal SainView Answer on Stackoverflow
Solution 11 - GitFaizan Ul HaqView Answer on Stackoverflow
Solution 12 - GitVipin MittalView Answer on Stackoverflow