Gitlab не толкать ветку, доступ запрещен?

Question

Befor update GitLab to 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 мерзавец -H расслоение EXEC грабли gitlab: проверить RAILS_ENV = производство Экземпляр метод "замок!" уже определен в 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 

Что такое проблема?

Помогите мне! и извините за мой английский

Answer 1

Как и в 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).
(после процесса обновления «From 6.x or 7.x to 7.4»)