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
  • #6690

Closed
Open
Created Apr 03, 2014 by Administrator@rootOwner

gitlab http pull request faild when upgrade from 6-4-stable to 6-6-stable

Created by: anonymelon

when I upgrade my gitlab from 6-4-stable to 6-6-stable, the http pull request faild and got the message:

remote: GitLab: You are not allowed to access master!
remote: error: hook declined to update refs/heads/master

and I find the log in gitlab-shell is :

E, [2014-04-03T11:58:09.497614 #26195] ERROR -- : API call <GET http://my-host/api/v3/internal/allowed?action=git-receive-pack&ref=master&project=jeremy.liao%2Ffortest&oldrev=1ef245383b965dc9bbbb66ea4ba02d7259aa6840&newrev=94fe4a8403cf4aad397c90aead98dccdc78dd67e&user_id=31> failed: 404 => <{"message":"404 Not found"}>.

and I have try the solution https://github.com/lsjostro/gitlab-shell/commit/b136e22d7e4ea34b35d805c380ba1fae2cf3c595, but it doesn't work. BTW, we use ldap validation. While I change it to ssh, it works as expected. Would you please help to check this issue, thanks.

Assignee
Assign to
Time tracking