【问题标题】:Unable to push code on github?无法在 github 上推送代码?
【发布时间】:2011-09-14 19:10:47
【问题描述】:

我已成功将一个应用程序代码推送到 github。 我已经设置了 ssh 密钥并将其添加到 github。

但后来我开始开发另一个应用程序并尝试使用以下方法将其推送到 github:

git remote add github git@github.com:user_name/demo_app.git
git push -u github master

然后我得到以下错误:

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

我也尝试过更改远程 Git 存储库的名称,但也没有用。

我尝试 $ssh -v git@github.com 来获取更多信息,这就是我得到的。

-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 git@github.com
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 no-more-sessions@openssh.com
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 eow@openssh.com 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

在设置 ssh 密钥时,我被要求输入密码,但我没有将其留空。

任何建议都将不胜感激。

【问题讨论】:

  • “另一个应用程序”?您是否已经分叉了这个其他应用程序,并且您的 GitHub 帐户页面上是否将其存储库列为您的存储库之一?
  • @Vonc - 是的,我也列出了其他应用程序的存储库..
  • @Ivan - 我写错了那行......我实际上使用了这个: git remote add github git@github.com:user_name/demo_app.git

标签: git-push


【解决方案1】:

您似乎正在尝试推送到您不拥有的存储库。要推送到另一个用户的存储库,您需要在 GitHub 网站上对其进行 fork。这将使您的帐户可以访问该存储库上的分支。

确保在本地存储库上创建匹配的分支,然后从该分支推送。为了推送到“主”分支,您需要添加为协作者或提出拉取请求,以便所有者可以将您的工作合并到主分支。

【讨论】:

    【解决方案2】:

    我认为问题出在这里:

    git remote add github github@github.com:user_name/demo_app.git
    

    这应该是

    git remote add github git@github.com:USERNAME/REPONAME.git
    

    github@github.com:...应该是git@github.com:...
    试试这个:

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

    【讨论】:

      【解决方案3】:

      我曾经遇到过同样的问题

       git remote add github git@github.com:user_name/demo_app.git
       git push -u github master
      

      然后我将远程 URL 更改为像这样使用 https

       git remote add github https://user_name@github.com/user_name/demo_app.git
       git push -u github master
      

      而且它工作正常。

      【讨论】:

        【解决方案4】:

        出现此问题的原因有几个:

        • 错字:在添加遥控器时任何地方出现错字都会导致问题。
        • 错误的 SSH 密钥:如果您的 ssh 密钥更改并且您再次访问存储库,则可能会发生这种情况。
        • Access Revoke:如果您对项目的访问权限被撤销,您会收到此错误。
        • SSH 密钥不正确 - 确保 \n 不是从 ssh 密钥复制粘贴的。

        【讨论】:

          【解决方案5】:

          如果您不拥有存储库,请确保您是贡献者。让管理员在设置下添加您。

          【讨论】:

            【解决方案6】:

            您可以尝试在 git config 上手动替换它:

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

            将网址替换为:url = git@github.com:username/reponame.git

            【讨论】:

            【解决方案7】:

            我在使用 bitbucket 时遇到了这个问题,

            可能会帮助其他人知道: 我发现最适合我的解决方案是将推送分成更小的块。从提交中删除大屏幕截图文件(10mb+)

            安全性最终不是问题更多关于 bin 文件的限制

            【讨论】:

              猜你喜欢
              • 1970-01-01
              • 1970-01-01
              • 2021-06-24
              • 2019-07-16
              • 2020-07-17
              • 1970-01-01
              • 2018-02-27
              • 2012-03-10
              相关资源
              最近更新 更多