Skip to content

GitLab

  • Menu
    • Projects Groups Snippets
      Help
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
  • #6628

Closed
Open
Created 11 years ago by Administrator@rootOwner
  • New issue

  • Report abuse

  • New issue

  • Report abuse

git via ssh always asks for git password

Closed

git via ssh always asks for git password

Created by: anrizal

Hello,

I experience this issue as only in one server. I've setup gitlab in other server and ecountered no problem. This is what I have done so far

  1. I checked the git/.ssh/authorized_keys and the public key is there
  2. run rake check the result is as folllows

Git configured for git user? ... yes

Checking Environment ... Finished

Checking GitLab Shell ...

GitLab Shell version >= 1.7.9 ? ... OK (1.9.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 update hook up-to-date? ... yes update hooks in repos are links: ... rizal / test ... repository is empty 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.2.12 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 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: ... rizal / test ... yes Projects have satellites? ... rizal / test ... can't create, repository is empty Redis version >= 2.0.0? ... yes Your git bin path is "/usr/local/bin/git" Git version >= 1.7.10 ? ... yes (1.8.5)

Checking GitLab ... Finished

  1. I check the sidekiq.log, and I dont see any issue. the log tails as follows

2014-03-26T14:56:08Z 8144 TID-oxxev2sdc Sidekiq::Extensions::DelayedMailer JID-0a7cf60d71a1d4ee61f0b890 INFO: done: 0.103 sec 2014-03-26T15:08:15Z 8144 TID-oxxev2sdc GitlabShellWorker JID-db61dd3001b166dfb08bcf7e INFO: start 2014-03-26T15:08:16Z 8144 TID-oxxev2sdc GitlabShellWorker JID-db61dd3001b166dfb08bcf7e INFO: done: 0.449 sec 2014-03-26T15:08:23Z 8144 TID-oxxev2sdc Sidekiq::Extensions::DelayedMailer JID-d2080f28da0e29dafdb79085 INFO: start 2014-03-26T15:08:23Z 8144 TID-oxxev2sdc Sidekiq::Extensions::DelayedMailer JID-d2080f28da0e29dafdb79085 INFO: done: 0.098 sec 2014-03-26T15:08:43Z 8144 TID-oxxev2sdc GitlabShellWorker JID-42dd9be68462754420c4a9d1 INFO: start Initialized empty Git repository in /home/git/repositories/rizal/test.git/ 2014-03-26T15:08:44Z 8144 TID-oxxev2sdc GitlabShellWorker JID-42dd9be68462754420c4a9d1 INFO: done: 0.501 sec 2014-03-26T15:08:53Z 8144 TID-oxxev2sdc Sidekiq::Extensions::DelayedMailer JID-05ba8f63f0562e4cda7f7d8c INFO: start 2014-03-26T15:08:53Z 8144 TID-oxxev2sdc Sidekiq::Extensions::DelayedMailer JID-05ba8f63f0562e4cda7f7d8c INFO: done: 0.11 sec

  1. The permission is correct, below is the permision for authorized_keys drwx------ 2 git git 4096 Mar 26 13:59 . drwxr-xr-x 7 git git 4096 Mar 26 16:16 .. -rw-r--r-- 1 git git 1042 Mar 26 16:08 authorized_keys
  2. my sshd_config has following settings PubkeyAuthentication yes AuthorizedKeysFile %h/.ssh/authorized_keys

AddressFamily inet AllowGroups root sudo git

  1. the only special thing about this server is that I have custom pg_hba.conf , but I dont think it is related.
  2. cloning using http is fine and has no problem

Is there anything else that I should look for.

Appreciate the help and the hint

Thank you

  1. Oh no!

    You are trying to upload something other than an image. Please upload a .png, .jpg, .jpeg, .gif, .bmp, .tiff or .ico.

    Incoming!

    Drop your designs to start your upload.

Linked issues
0


  • Administrator
    Administrator @root · 11 years ago
    Owner

    Created by: Wachiwi

    Which OS do you use? In some distributions you need to configure SELinux properly.

    By Administrator on 2014-03-26T16:28:14 (imported from GitLab project)

  • Administrator
    Administrator @root · 11 years ago
    Owner

    Created by: anrizal

    I use Ubuntu 12.04 Server bare installation. I have Ubuntu 12.04 in my other machine as well (but no problem). Also, this box is inside a firewall. only needed port is opened.

    By Administrator on 2014-03-27T08:00:32 (imported from GitLab project)

  • Administrator
    Administrator @root · 11 years ago
    Owner

    Created by: Wachiwi

    @anrizal So your issue is fixed?

    By Administrator on 2014-03-27T08:34:42 (imported from GitLab project)

  • Administrator
    Administrator @root · 11 years ago
    Owner

    Created by: anrizal

    unfortunately not. I've also checked my sshd_config and I have the settings below available as well. but I still have problem.

    PubkeyAuthentication yes AuthorizedKeysFile %h/.ssh/authorized_keys

    By Administrator on 2014-03-27T08:41:59 (imported from GitLab project)

  • Administrator
    Administrator @root · 11 years ago
    Owner

    Created by: anrizal

    I have this setting as well in sshd_config

    AddressFamily inet AllowGroups root sudo git

    By Administrator on 2014-03-27T08:56:17 (imported from GitLab project)

  • Administrator
    Administrator @root · 11 years ago
    Owner

    Created by: anrizal

    ok it is fixed. the problem is with the ssh private key, somehow it got corrupted. The solution was simply to generate new key pairs

    By Administrator on 2014-03-27T11:03:02 (imported from GitLab project)

  • Administrator
    Administrator @root · 11 years ago
    Owner

    Created by: Wachiwi

    /cc @Razer6

    By Administrator on 2014-03-27T11:56:14 (imported from GitLab project)

  • You're only seeing other activity in the feed. To add a comment, switch to one of the following options.
Please register or sign in to reply
0 Assignees
None
Assign to
Milestone
No milestone
None
None
Time tracking
No estimate or time spent
Due date
None
None
0
Labels
None
Assign labels
  • No matching results
  • Manage project labels
Confidentiality
Not confidential
Not confidential

You are going to turn on confidentiality. Only team members with at least Reporter access will be able to see and leave comments on the issue.

Lock issue
Unlocked
1
1 participant
user avatar
Reference: gpt/large_projects/gitlabhq1#6628

Menu

Projects Groups Snippets
Help