ssh - Gitlab不推分支，Access拒绝？

Befor将GitLab更新为v7，我推动了这个分支。现在 - 访问被拒绝：

$ git push origin my_branch
Access denied.
fatal: Could not read from remote repository.
Please make sure you have the correct access rights and the repository exists.

当我检查ssh_key时，Gitlab知道我：

$ ssh -T git@github.lcl.loc
Welcome to GitLab, Nikolay Nozdrin-Plotnitsky!

Gitlab检查： $ sudo -u git -H bundle exec rake gitlab：check RAILS_ENV = production 实例方法“锁定！”已经在ActiveRecord :: Base中定义，使用通用帮助器或设置StateMachine :: Machine.ignore_method_conflicts = true。检查环境......

Git configured for git user? ... yes

Checking Environment ... Finished

Checking GitLab Shell ...

GitLab Shell version >= 1.9.6 ? ... OK (2.0.1)
Repo base directory exists? ... yes
Repo base directory is a symlink? ... no
Repo base owned by git:git? ... yes
Repo base access is drwxrws---? ... yes
Satellites access is drwxr-x---? ... yes
update hook up-to-date? ... no
Could not find /home/git/gitlab-shell/hooks/update
  Try fixing it:
  Check the hooks_path in config/gitlab.yml
  Check your gitlab-shell installation
  For more information see:
  doc/install/installation.md in section "GitLab Shell"
update hooks in repos are links: ... can't check because of previous errors
Running /home/git/gitlab-shell/bin/check
Check GitLab API access: OK
Check directories and files:
        /home/git/repositories: OK
        /home/git/.ssh/authorized_keys: OK
Test redis-cli executable: redis-cli 2.4.14
Send ping to redis server: PONG
gitlab-shell self-check successful

Checking GitLab Shell ... Finished

Checking Sidekiq ...

Running? ... yes
Number of Sidekiq processes ... 1

Checking Sidekiq ... Finished

Checking LDAP ...

LDAP is disabled in config/gitlab.yml

Checking LDAP ... Finished

Checking GitLab ...

Database config exists? ... yes
Database is SQLite ... no
All migrations up? ... yes
Database contains orphaned UsersGroups? ... no
GitLab config exists? ... yes
GitLab config outdated? ... no
Log directory writable? ... yes
Tmp directory writable? ... yes
Init script exists? ... yes
Init script up-to-date? ... yes
projects have namespace: ...
LPO / MKZD ... yes
Projects have satellites? ...
LPO / MKZD ... yes
Redis version >= 2.0.0? ... yes
Your git bin path is "/usr/bin/git"
Git version >= 1.7.10 ? ... yes (1.7.10)

Checking GitLab ... Finished
$ sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production
Instance method "lock!" is already defined in ActiveRecord::Base, use generic helper instead or set StateMachine::Machine.ignore_method_conflicts = true.

System information
System:         Debian 7.4
Current User:   git
Using RVM:      no
Ruby Version:   2.1.2p95
Gem Version:    2.2.2
Bundler Version:1.7.4
Rake Version:   10.3.2
Sidekiq Version:2.17.0

GitLab information
Version:        7.0.0
Revision:       de9bf7d
Directory:      /home/git/gitlab
DB Adapter:     mysql2
URL:            https://GitHub.lcl.loc/gitlab
HTTP Clone URL: https://GitHub.lcl.loc/gitlab/some-project.git
SSH Clone URL:  git@GitHub.lcl.loc:some-project.git
Using LDAP:     no
Using Omniauth: no

GitLab Shell
Version:        2.0.1
Repositories:   /home/git/repositories/
Hooks:          /home/git/gitlab-shell/hooks/
Git:            /usr/bin/git

什么是问题？

救救我！抱歉我的英文

与issue 8106一样，您必须检查ssh密钥的性质（个人密钥或部署密钥）

有时，直接从服务器~git/authorized_keys删除密钥会有所帮助（如this issue中所述）：您重新生成一个新密钥。

如issue 8260中所述，请查看GitLab检查：

cd /home/git/gitlab
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production

问题OP confirms已在GitLab 7.4 + （7.4.2）中解决。
（遵循升级过程＆＃34; From 6.x or 7.x to 7.4＆＃34;）

Gitlab不推分支，Access拒绝？

1 个答案: