Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • G gitlabhq1
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 21
    • Issues 21
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 12
    • Merge requests 12
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • gpt
  • large_projects
  • gitlabhq1
  • Issues
  • #4286

Closed
Open
Created Jun 12, 2013 by Administrator@rootOwner

gitlab 5.2 : git clone by ssh failed, But by http is ok

Created by: unanao

Summary:

 gitlab 5.2 clone  by ssh failed.  But by http is ok . I have put the public key to the server 

Steps to reproduce:

  git clone git@server_ip:unanao/good-luck.git . 

Expected behavior:

 
Observed behavior
unanao@ThinkpadT430i:~/tmp/42-gitlab/ssh$ git clone git@server_ip:unanao/good-luck.git .
Cloning into '.'...
Enter passphrase for key '/home/unanao/.ssh/id_rsa': 
Permission denied (publickey).
fatal: The remote end hung up unexpectedly

Output of checks


Results of GitLab Application Check 
git@AY121227102640e084565:~/gitlab$ bundle exec rake gitlab:check RAILS_ENV=production
Checking Environment ...

Git configured for git user? ... yes
Has python2? ... yes
python2 is supported version? ... yes

Checking Environment ... Finished

Checking GitLab Shell ...

GitLab Shell version >= 1.4.0 ? ... OK (1.4.0)
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
post-receive hook up-to-date? ... yes
post-receive hooks in repos are links: ... 
bancai ... repository is empty
document ... repository is empty
unanao / test ... repository is empty
unanao / good-luck ... repository is empty

Checking GitLab Shell ... Finished

Checking Sidekiq ...

Running? ... yes

Checking Sidekiq ... Finished

Checking GitLab ...

Database config exists? ... yes
Database is SQLite ... no
All migrations up? ... yes
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 satellites? ... 
bancai ... can't create, repository is empty
document ... can't create, repository is empty
unanao / test ... can't create, repository is empty
unanao / good-luck ... can't create, repository is empty
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

Version of GitLab you are running;


System information
System:     Debian 6.0.7
Current User:   git
Using RVM:  no
Ruby Version:   1.9.3p392
Gem Version:    1.8.23
Bundler Version:1.3.5
Rake Version:   10.0.4

GitLab information
Version:    5.2.1
Revision:   26ed59f
Directory:  /home/git/gitlab
DB Adapter: mysql2
URL:        http://server_ip:8888
HTTP Clone URL: http://server_ip:8888/some-project.git
SSH Clone URL:  git@server_ip:some-project.git
Using LDAP: no
Using Omniauth: no

GitLab Shell
Version:    1.4.0
Repositories:   /home/git/repositories/
Hooks:      /home/git/gitlab-shell/hooks/
Git:        /usr/bin/git
Assignee
Assign to
Time tracking