3

当我尝试 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"
4

1 回答 1

2

这看起来像当前的错误 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中有详细讨论。

正如OP Adam-E在评论中报告的那样，最后一个版本 5.1提供了以下帮助：

  • 将 Apache2 换成 nginx，
  • 对刚刚发布的 GitLab 5.1 stable 进行了全新安装，并且
  • 截断/home/git/.ssh/authorized_keys和
  • 读了我的公钥。

从最后一步开始，它开始工作。

于 2013-04-16T10:59:22.833 回答