GitLab 5.0:通过SSH的Git推送失败,但没有HTTPS或直接SSH连接的错误

时间:2013-04-16 10:10:14

标签: git ssh gitlab

当我尝试git push时,我得到通常的错误

  

致命:无法从远程存储库中读取。

     

请确保您拥有正确的访问权限   存储库存在。

但是,推送和拉动通过HTTPS工作正常。

我认为这将是SSH的问题,但是连接似乎没有产生任何错误,它接受我的公钥,给我欢迎消息并退出0。

$ ssh -vT git@git.server.com
OpenSSH_5.9p1, OpenSSL 0.9.8r 8 Feb 2011
debug1: Reading configuration data /Users/adam/.ssh/config
debug1: Reading configuration data /etc/ssh_config
debug1: /etc/ssh_config line 20: Applying options for *
debug1: Connecting to git.server.com [420.420.555.555] port 22.
debug1: Connection established.
debug1: identity file /Users/adam/.ssh/id_rsa type 1
debug1: identity file /Users/adam/.ssh/id_rsa-cert type -1
debug1: Remote protocol version 2.0, remote software version OpenSSH_6.0p1 Debian-3ubuntu1
debug1: match: OpenSSH_6.0p1 Debian-3ubuntu1 pat OpenSSH*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_5.9
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: Server host key: RSA 96:cc:........
debug1: Host 'git.server.com' is known and matches the RSA host key.
debug1: Found key in /Users/adam/.ssh/known_hosts:2
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,password
debug1: Next authentication method: publickey
debug1: Offering RSA public key: /Users/adam/.ssh/id_rsa
debug1: Server accepts key: pkalg ssh-rsa blen 279
debug1: Authentication succeeded (publickey).
Authenticated to git.server.com ([257.257.257.257]:22).
debug1: channel 0: new [client-session]
debug1: Requesting no-more-sessions@openssh.com
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: Sending environment.
debug1: Sending env LANG = en_GB.UTF-8
Welcome to GitLab, !
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
Transferred: sent 2512, received 2968 bytes, in 0.5 seconds
Bytes per second: sent 5567.4, received 6578.0
debug1: Exit status 0

虽然

运行此命令失败
ssh git@git.server.com "ls /home/git/repositories/adam/my-repo.git"

1 个答案:

答案 0 :(得分:2)

看起来像当前的bug 3424

您需要确保:

  • Gitlab应用程序(与sidekiq消费者一起)和Redis已经开始
  • 配置正确

配置问题示例:

  

放松一下并查看我的所有配置文件后,我发现了我的问题,这当然是我的错误

     

在配置我的服务器时没有想到,在/etc/hosts文件中我将名称x.m.com添加到环回IP地址(127.0.0.1)。
  因此,在我的本地服务器上执行的任何网络调用将转到该IP而不是NginX实际绑定到GitLab服务器的IP。

其他例子:

  

通过更改nginx配置以侦听*:80而不是特定IP,我能够解决我的问题。显然由于防火墙内部和外部IP不同。

listen *:80 default_server;

issues/3384中详细讨论了最后一次配置错误。


上一版本5.1有助于OP Adam-E中的the comments报告,并执行以下步骤:

  
      
  • 将Apache2替换为nginx,
  •   
  • 彻底安装了刚刚发布的GitLab 5.1 stable和
  •   
  • 截断/home/git/.ssh/authorized_keys
  •   
  • 读了我的公钥。
  •   
     

从最后一步开始,它就开始工作了。