Gitlab:没有提供用户或密钥

hip*_*sla 5 git version-control gitlab

我试图将主分支从客户端推送到安装了gitlab的服务器.但是,我收到以下错误信息:

[root@warehouse git-sample]# git push origin master
git@192.168.7.82's password: 
Counting objects: 3, done.
Writing objects: 100% (3/3), 224 bytes | 0 bytes/s, done.
Total 3 (delta 0), reused 0 (delta 0)
remote: GitLab: No user or key was provided.
To git@192.168.7.82:ite-pon/git-sample.git
 ! [remote rejected] master -> master (pre-receive hook declined)
error: failed to push some refs to 'git@192.168.7.82:ite-pon/git-sample.git'
Run Code Online (Sandbox Code Playgroud)

看起来gitlab在项目中设置了预接收挂钩,但阻止了推送操作.

有没有人有任何想法来处理这个问题?谢~~ :)

////////////////////////////////////////////////// ////////////////////////////////////////////////// //////////////////////////////////////////////////

以下是服务器和客户端的详细配置和信息:

服务器:GitLab&Git&Repository Info

[root@warehouse git-sample.git]# pwd
/opt/gitlab/apps/gitlab/repositories/ite-pon/git-sample.git
Run Code Online (Sandbox Code Playgroud)
  1. Gitlab记录客户端的ssh pub密钥(没有足够的声誉发送img :()

  2. 设置管理员(客户端用户)作为此项目的主服务器,以及域的所有者.

服务器:配置

[root@warehouse repositories]# grep git /etc/passwd
git:x:502:502:Git:/opt/gitlab/apps/gitlab/repositories:/opt/gitlab/git/bin/git-shell
Run Code Online (Sandbox Code Playgroud)

客户:工作区信息

[root@warehouse git-sample]# pwd
/root/workspaces/git-sample/git-sample
[root@warehouse git-sample]# ls
readme.txt
[root@warehouse git-sample]# git branch
  dev
* master
[root@warehouse git-sample]# git remote -v
origin  git@192.168.7.82:ite-pon/git-sample.git (fetch)
origin  git@192.168.7.82:ite-pon/git-sample.git (push)
Run Code Online (Sandbox Code Playgroud)

客户端:SSH和Git Info

[root@warehouse git-sample]# git config --global user.name
Administrator
[root@warehouse git-sample]# git config --global user.email
admin@gitlab.xxxxxxxxxxx.com
[root@warehouse git-sample.git]# ls -l ~/.ssh/id_rsa.pub 
-rw-r--r-- 1 root root 413 7?   1 15:51 /root/.ssh/id_rsa.pub
Run Code Online (Sandbox Code Playgroud)

sor*_*rin 3

您似乎遇到了刚刚在https://gitlab.com/gitlab-org/gitlab-ce/issues/2156上记录的错误- 解决方法是从服务器上的authorized_keys 文件中删除密钥。