title: Can't clone gitlab's repo via ssh, via http - OK
body: <p>I'm new to gitlab and CI so i had tons of questions but some of them solved via google, SO, git mans, but not the last ...</p>
  
  <p>I can't clone repo via ssh =(</p>
  
  <p>If i try to clone repo via http:</p>
  
  <pre><code>lesha@lesha-SeoTeam:/var/www$ git clone http://gitlab.vbox/root/virtualboxgitlab.git
  Cloning into 'virtualboxgitlab'...
  Username for 'http://gitlab.vbox': root
  Password for 'http://root@gitlab.vbox':
  warning: You appear to have cloned an empty repository.
  </code></pre>
  
  <p>That's OK!</p>
  
  <p>But via ssh ...</p>
  
  <pre><code>lesha@lesha-SeoTeam:/var/www$ git clone git@gitlab.vbox:root/virtualboxgitlab.git
  Cloning into virtualbox 'gitlab'
  git@gitlab.vbox's password:&lt;br /&gt;   
  </code></pre>
  
  <p>It prompts me git's password which I didn't create during install (as I had in man)</p>
  
  <pre><code>rsa keys
  </code></pre>
  
  <p>I added my key via gitlab's web (to account root, actually I didn't create any other accounts)</p>
  
  <p>And also I added key by "cat my_rsa.pub >> authorized_keys"</p>
  
  <p>I read few posts here about ssh troubles, but most have gitolite installed</p>
  
  <p>I installed gitlab 5.3 without gitolite (as in manual), may be I should ?</p>
  
  <p>Also I tried <code>ssh -vT git@gitlab.vbox</code> and it outputs :</p>
  
  <pre><code>....
  debug1: Server host key: ECDSA 48:83:ba:b3:37:72:a0:dc:ca:2c:a3:b8:78:a1:c4:ad
  debug1: Host 'gitlab.vbox' is known and matches the ECDSA host key.
  debug1: Found key in /home/lesha/.ssh/known_hosts:2
  debug1: ssh_ecdsa_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: /home/lesha/.ssh/id_rsa
  debug1: Authentications that can continue: publickey,password
  debug1: Trying private key: /home/lesha/.ssh/id_dsa
  debug1: Trying private key: /home/lesha/.ssh/id_ecdsa
  debug1: Next authentication method: password
  git@gitlab.vbox's password:
  
  
  root@seotm-server:/home/git/.ssh# ls -l
  итого 4
  -rw------- 1 git git 922 Июл 18 21:05 authorized_keys
  </code></pre>
  
  <p>environmetnt: 
  debian 7, nginx + passenger, gitlab 5.3, ruby 2.0.0p247 , without gitolite, puma against unicorn</p>
  
  <p>please help!=) i'm stuck ...</p>
  
  <hr>
  
  <p>some additions (20.07.2013):</p>
  
  <p>I created user git as in manual install</p>
  
  <pre><code>sudo adduser --disabled-login --gecos 'GitLab' git
  </code></pre>
  
  <p>The next day, I tried to kill git and re-add simply by <code>useradd</code> command, after that my keys are working but i'm still not happy because:</p>
  
  <pre><code>lesha@lesha-SeoTeam:/var/www$ git clone git@gitlab.vbox:root/virtualboxgitlab.git
  Cloning into 'virtualboxgitlab'...
  fatal: 'root/virtualboxgitlab.git' does not appear to be a git repository
  fatal: The remote end hung up unexpectedly
  </code></pre>
  
  <p>and http works as well as previous:</p>
  
  <pre><code>lesha@lesha-SeoTeam:/var/www$ git clone http://gitlab.vbox/root/virtualboxgitlab.git
  Cloning into 'virtualboxgitlab'...
  Username for 'http://gitlab.vbox': root
  Password for 'http://root@gitlab.vbox': 
  warning: You appear to have cloned an empty repository.
  </code></pre>
  
  <p>So, now I don't have auth problems but have another one.</p>
  
  <p>How would you troubleshoot this issue from there?</p>