Github - Fatal Authentication Failed - But Can I Still Connect?

Question

My github is not connecting. I tried two different computers and I get the same error, so I'm doing something wrong. When I run git push , I get a request for my username / password, as expected. Enter them, and yes, I’m typing them correctly. Then he says:

 fatal: Authentication failed 

However, when I type ssh -T [e-mail] , it tells me my passphrase and after entering it greets me on github. I tried adding the SSH key again, and all it says is that the SSH key is already included in the account. Did someone let me know what I was missing?

When I try to log in, it shows:

Password for http://(UserName)@www.github.com:

Is it correct?

Additional info: Here is the output of ssh-vT git @ github.com:

 $ ssh-add -l Could not open a connection to your authentication agent. 

_

 $ ssh -vT [e-mail] OpenSSH_4.6p1, OpenSSL 0.9.8e 23 Feb 2007 debug1: Connecting to github.com [192.30.252.129] port 22. debug1: Connection established. debug1: identity file /l/.ssh/identity type -1 debug1: identity file /l/.ssh/id_rsa type 1 debug1: identity file /l/.ssh/id_dsa type -1 debug1: Remote protocol version 2.0, remote software version OpenSSH_5.9p1 Debia n-5ubuntu1+github5 debug1: match: OpenSSH_5.9p1 Debian-5ubuntu1+github5 pat OpenSSH* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_4.6 debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: server->client aes128-cbc hmac-md5 none debug1: kex: client->server aes128-cbc hmac-md5 none debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP debug1: SSH2_MSG_KEX_DH_GEX_INIT sent debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY debug1: Host 'github.com' is known and matches the RSA host key. debug1: Found key in /l/.ssh/known_hosts:1 debug1: ssh_rsa_verify: signature correct debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS received debug1: SSH2_MSG_SERVICE_REQUEST sent debug1: SSH2_MSG_SERVICE_ACCEPT received debug1: Authentications that can continue: publickey debug1: Next authentication method: publickey debug1: Trying private key: /l/.ssh/identity debug1: Offering public key: /l/.ssh/id_rsa debug1: Server accepts key: pkalg ssh-rsa blen 277 debug1: read PEM private key done: type RSA debug1: Authentication succeeded (publickey). debug1: channel 0: new [client-session] debug1: Entering interactive session. debug1: Remote: Forced command. debug1: Remote: Port forwarding disabled. debug1: Remote: X11 forwarding disabled. debug1: Remote: Agent forwarding disabled. debug1: Remote: Pty allocation disabled. debug1: Remote: Forced command. debug1: Remote: Port forwarding disabled. debug1: Remote: X11 forwarding disabled. debug1: Remote: Agent forwarding disabled. debug1: Remote: Pty allocation disabled. debug1: client_input_channel_req: channel 0 rtype exit-status reply 0 Hi ____! You've successfully authenticated, but GitHub does not provide shell ac cess. debug1: channel 0: free: client-session, nchannels 1 debug1: Transferred: stdin 0, stdout 0, stderr 0 bytes in 0.1 seconds debug1: Bytes per second: stdin 0.0, stdout 0.0, stderr 0.0 debug1: Exit status 1 

Answer 1

Try ssh instead of linking to github via http. do git remote set-url origin <ssh url> and then try to do git push

The ssh url should be something like [e-mail]...

Answer 2

You can try...

1 Edit the remote repository

 git remote set-url origin your-remote-repository-ssh-url 

2 Press your code.

 git push origin ... 

Where do you find your ssh url?

1 On the repositories page

2 Click the ssh link and copy your ssh-url

Answer 3

If you have this problem, you have two solutions:

• If you insist on using HTTPS to connect to Github, you will need to get a personal access token from your Github account instead of your password.
• You need to switch to SSH and use it to login.

In both cases, check out this stack overflow question and its a great first answer on how to implement them.