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

Closed
Open
Created Apr 09, 2014 by Administrator@rootOwner

Git push fails over HTTP transport after upgrade from 6.6 to 6.7

Created by: leaves3113

Hi, all. After upgrade 6.6 to 6.7 not work push over http, but over shh all good. Git push example:

Counting objects: 4, done.
Delta compression using up to 2 threads.
Compressing objects: 100% (2/2), done.
Writing objects: 100% (3/3), 268 bytes, done.
Total 3 (delta 0), reused 0 (delta 0)
remote: GitLab: You are not allowed to access master!
remote: error: hook declined to update refs/heads/master
To http://server/leaves/test.git
 ! [remote rejected] master -> master (hook declined)
error: failed to push some refs to 'http://server/leaves/test.git'

In gitlab-shell logs:

E, [2014-04-09T16:10:49.210599 #13699] ERROR -- : API call <GET http://server//api/v3/internal/allowed?action=git-receive-pack&ref=master&project=leaves%2Ftest&oldrev=0ef6a068cc7bb1b3e1606e29787f0ec6f0dd69d3&newrev=5d87c4d567c826759be76e4732c6f6b2647e619e&user_id=2> failed: 404 => <{"message":"404 Not found"}>.

What maybe wrong?

Thanks.

Assignee
Assign to
Time tracking