GitLab

Created by: pdobrigkeit

Just followed the install guide. I am able to clone and commit via http without problems.

SSH connections seems to be working fine:

ssh -T [email protected]
Welcome to GitLab, Philipp Dobrigkeit!

But when I try to clone or push via ssh I get:

git push origin master
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

Also there is coming a TortoisePlink window asking me for a password for git@IP-ADDRESS

In the production.log I found the following:

Started GET "//api/v3/internal/discover?key_id=2" for 127.0.0.1 at 2013-11-21 18:19:04 +0100
Connecting to database specified by database.yml
Creating scope :opened. Overwriting existing method Issue.opened.
Creating scope :of_projects. Overwriting existing method MergeRequest.of_projects.
Creating scope :closed. Overwriting existing method MergeRequest.closed.
Creating scope :public. Overwriting existing method Snippet.public.
Creating scope :private. Overwriting existing method Snippet.private.
Creating scope :fresh. Overwriting existing method ProjectSnippet.fresh.
Creating scope :non_expired. Overwriting existing method ProjectSnippet.non_expired.
Creating scope :expired. Overwriting existing method ProjectSnippet.expired.
Connecting to database specified by database.yml
Started GET "/api/v3/internal/discover?key_id=2" for 127.0.0.1 at 2013-11-21 18:26:11 +0100
Creating scope :opened. Overwriting existing method Issue.opened.
Creating scope :of_projects. Overwriting existing method MergeRequest.of_projects.
Creating scope :closed. Overwriting existing method MergeRequest.closed.
Creating scope :public. Overwriting existing method Snippet.public.
Creating scope :private. Overwriting existing method Snippet.private.
Creating scope :fresh. Overwriting existing method ProjectSnippet.fresh.
Creating scope :non_expired. Overwriting existing method ProjectSnippet.non_expired.
Creating scope :expired. Overwriting existing method ProjectSnippet.expired.

Once with double slash, I changed the gitlab-shell/config.yml and removed the trailing slash, but no change, so I reverted that fix.

gitlab:check seems OK

sudo -u git -H 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.7.8 ? ... OK (1.7.9)
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
update hook up-to-date? ... yes
update hooks in repos are links: ...
Company / TestRepo ... ok
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
        /usr/bin/redis-cli: OK
gitlab-shell self-check successful

Checking GitLab Shell ... Finished

Checking Sidekiq ...

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

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 namespace: ...
Company / TestRepo ... yes
Projects have satellites? ...
Company / TestRepo ... 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

Any ideas?