Failed to push the code on github?

Question

I successfully clicked one application code on github. I installed the ssh key and added it to github.

But then I started working on another application and tried to push it on github using:

git remote add github [e-mail] :user_name/demo_app.git git push -u github master 

Then I got the following error:

 Permission denied (publickey). fatal: The remote end hung up unexpectedly 

I also tried changing the name of the remote Git repository, but that didn't work either.

I tried $ ssh -v git @ github.com to get more info, and this is what I got.

 -bash: cd: ../.ssh: No such file or directory abhimanyu@sourcebits-Ubuntu :~/Aptana_Studio_3_Workspace/demo_app$ cd ~/.ssh abhimanyu@sourcebits-Ubuntu :~/.ssh$ cd ~ abhimanyu@sourcebits-Ubuntu :~$ ssh -v [e-mail] OpenSSH_5.5p1 Debian-4ubuntu4, OpenSSL 0.9.8o 01 Jun 2010 debug1: Reading configuration data /etc/ssh/ssh_config debug1: Applying options for * debug1: Connecting to github.com [207.97.227.239] port 22. debug1: Connection established. debug1: identity file /home/abhimanyu/.ssh/id_rsa type 1 debug1: Checking blacklist file /usr/share/ssh/blacklist.RSA-2048 debug1: Checking blacklist file /etc/ssh/blacklist.RSA-2048 debug1: identity file /home/abhimanyu/.ssh/id_rsa-cert type -1 debug1: identity file /home/abhimanyu/.ssh/id_dsa type -1 debug1: identity file /home/abhimanyu/.ssh/id_dsa-cert type -1 debug1: Remote protocol version 2.0, remote software version OpenSSH_5.1p1 Debian- 5github2 debug1: match: OpenSSH_5.1p1 Debian-5github2 pat OpenSSH* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_5.5p1 Debian-4ubuntu4 debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: server->client aes128-ctr hmac-md5 none debug1: kex: client->server aes128-ctr 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 /home/abhimanyu/.ssh/known_hosts:9 debug1: ssh_rsa_verify: signature correct debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS received debug1: Roaming not allowed by server debug1: SSH2_MSG_SERVICE_REQUEST sent debug1: SSH2_MSG_SERVICE_ACCEPT received debug1: Authentications that can continue: publickey debug1: Next authentication method: publickey debug1: Offering public key: /home/abhimanyu/.ssh/id_rsa debug1: Remote: Forced command: gerve abhimanyu86 debug1: Remote: Port forwarding disabled. debug1: Remote: X11 forwarding disabled. debug1: Remote: Agent forwarding disabled. debug1: Remote: Pty allocation disabled. debug1: Server accepts key: pkalg ssh-rsa blen 279 debug1: Remote: Forced command: gerve abhimanyu86 debug1: Remote: Port forwarding disabled. debug1: Remote: X11 forwarding disabled. debug1: Remote: Agent forwarding disabled. debug1: Remote: Pty allocation disabled. debug1: Authentication succeeded (publickey). debug1: channel 0: new [client-session] debug1: Requesting [e-mail] debug1: Entering interactive session. debug1: Sending environment. debug1: Sending env LANG = en_IN PTY allocation request failed on channel 0 Hi user_name! You've successfully authenticated, but GitHub does not provide shell access. debug1: client_input_channel_req: channel 0 rtype exit-status reply 0 debug1: client_input_channel_req: channel 0 rtype [e-mail] reply 0 debug1: channel 0: free: client-session, nchannels 1 Connection to github.com closed. Transferred: sent 2648, received 2904 bytes, in 0.5 seconds Bytes per second: sent 5858.0, received 6424.3 debug1: Exit status 1 

While I was setting the ssh key, I was asked to enter a passphrase, and I did not leave it blank.

Any suggestion would be appreciated.

Answer 1

There are several reasons why you might get this problem:

• Typo : having a typo anywhere when adding a remote device can cause a problem.
• Invalid SSH key . This can happen if your ssh key has changed and you are accessing the repo again.
• Access to review . If your access to the project is canceled, you may receive this error.
• Invalid SSH key . Make sure \ n is not copied using the ssh key.

Answer 2

It looks like you are trying to click on a repository that you do not have. To click on another user repository, you need to unlock it on the GitHub website. This will give your account access to the branch in this repository.

Be sure to create the appropriate branch in the local repository, and then click from this branch. To go to the master branch, you need to either add as a co-author or make a transfer request so that the owner can combine your work with the main branch.

Answer 3

I think the problem is here:

 git remote add github [e-mail] :user_name/demo_app.git 

It should be

 git remote add github [e-mail] :USERNAME/REPONAME.git 

This is [e-mail] :... should be [e-mail] :...
Try the following:

 # change the remote url git remote set-url github git@github :user_name/demo_app.git # and then try pushing again git push github master 

Answer 4

I have the same problem with

  git remote add github [e-mail] :user_name/demo_app.git git push -u github master 

Then I change the remote url to use https, like this

  git remote add github https:// [e-mail] /user_name/demo_app.git git push -u github master 

And it works correctly.

Answer 5

If you do not own the repository, make sure that you are the author. Ask the administrator to add you to the settings.

Answer 6

You can try replacing it manually with git config:

$ vi (or any other text editor) .git/config

Replace URL: url = [e-mail] :username/reponame.git

Answer 7

I had this problem with bitbucket,

May help others find out: I found that the solution that works best for me broke the push into smaller pieces. Removing large screen capture files (10mb +) from commits

After all, security was not a problem with bin file restrictions.