Can't push to my project
I'm the owner of private repo. My repo has 'master' branch as protected, but developers can push to it. Once my devs started to push their changes to master branch, I've noticed that I'm not able to push my changes any more. The output looks like the following:
private-repo$ git push
Counting objects: 3, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (2/2), done.
Writing objects: 100% (3/3), 261 bytes | 0 bytes/s, done.
Total 3 (delta 1), reused 0 (delta 0)
remote: GitLab: No such project
To git@gitlab.com:[my-username]/private-repo.git
! [remote rejected] master -> master (pre-receive hook declined)
error: failed to push some refs to 'git@gitlab.com:[my-username]/private-repo.git'My Gitlab dashboard shows me that I'm still the project owner. I can create branch and tags from UI. I've tried to use branches, created in UI, but no luck -can't push. I can even clone my project again. But it's not possible to push anything to any branch. Please help.
Activity
Hey I am having the same issue
🙊 , any luck yet?private-repo$ git push
Counting objects: 5, done.
Writing objects: 100% (3/3), 264 bytes | 0 bytes/s, done.
Total 3 (delta 0), reused 0 (delta 0)
remote: GitLab: No such project
! [remote rejected] master -> master (pre-receive hook declined)
error: failed to push some refs to 'http://[url-to-repo]/private.git'
/cc @DouweM do you have an idea what's going wrong here?
@haynes I think I have an idea.
@haynes Or on second thought, I do not.
@rptracker-dev @fadsel Do you have any other relevant info you could share? Is this only occurring for protected branches? Only for the master branch? Only with developers-can-push enabled? Only with a master account? Is this happening always, or only with selected repo's? What makes those repo's different? Answers to those questions should help us get a little further :)
mentioned in issue #1241 (closed)
@DouweM, Here are some details:
- I created project in Jan 2015,
- Initially, I looked at protected branch and found out default master as protected.
- I added some devs with 'allow push' checkbox set
- I pushed some changes at Jan,26
- After that, one of devs pushed his changes in master (from Feb 4 to March,16). I didn't make changes after his first commit
- I tried to push my changes on March,16 with no luck, getting "Gitlab: No such project error"
- After that, I unprotect master branch. Problem still exists
- I re-cloned the project, and tried to push again. Problem still exists
- I added branch to my project via UI, pulled changes and tried to push new changes. Got the same error.
- In the same time, my dev has full access to the repo with no problems.
So, the problem is only with project owner and push action. Is it possible to restore full access to my project? Sure, I can create new project and transfer code to it, but we have some wiki pages and issues, which is also necessary to migrate also. So, please advice. Let me know, if you need more details.
BTW, today, I found out that activity tab on my project becomes empty(yesterday it shows pushes and create/remove branch events).
-
@DouweM, I collected some more debug information, after adding the following into ~/.ssh/config:
host gitlab user git hostname gitlab.com LogLevel DEBUG3 identityfile ~/.ssh/id_rsa.pub PreferredAuthentications publickeyThen I modify gitlab remote to be the following:
[remote "gitlab"] url = gitlab:[my-username]/private-repo.git fetch = +refs/heads/*:refs/remotes/gitlab/*The output is the following(I ommitted some output before ssh authenitcation):
debug1: Authentication succeeded (publickey). Authenticated to gitlab.com ([54.93.71.23]:22). debug2: fd 4 setting O_NONBLOCK debug2: fd 5 setting O_NONBLOCK debug1: channel 0: new [client-session] debug3: ssh_session2_open: channel_new: 0 debug2: channel 0: send open debug1: Requesting no-more-sessions@openssh.com debug1: Entering interactive session. debug1: Remote: Forced command. debug1: Remote: Port forwarding disabled. debug1: Remote: X11 forwarding disabled. debug1: Remote: Agent forwarding disabled. debug1: Remote: Pty allocation disabled. debug1: Remote: Forced command. debug1: Remote: Port forwarding disabled. debug1: Remote: X11 forwarding disabled. debug1: Remote: Agent forwarding disabled. debug1: Remote: Pty allocation disabled. debug2: callback start debug2: fd 3 setting TCP_NODELAY debug3: packet_set_tos: set IP_TOS 0x08 debug2: client_session2_setup: id 0 debug1: Sending environment. debug3: Ignored env XDG_VTNR debug3: Ignored env XDG_SESSION_ID debug3: Ignored env CLUTTER_IM_MODULE debug3: Ignored env SESSION debug3: Ignored env GPG_AGENT_INFO debug3: Ignored env TERM debug3: Ignored env SHELL debug3: Ignored env XDG_MENU_PREFIX debug3: Ignored env VTE_VERSION debug3: Ignored env GJS_DEBUG_OUTPUT debug3: Ignored env WINDOWID debug3: Ignored env UPSTART_SESSION debug3: Ignored env GNOME_KEYRING_CONTROL debug3: Ignored env GJS_DEBUG_TOPICS debug3: Ignored env USER debug3: Ignored env LS_COLORS debug3: Ignored env SSH_AUTH_SOCK debug3: Ignored env SESSION_MANAGER debug3: Ignored env USERNAME debug3: Ignored env DEFAULTS_PATH debug3: Ignored env XDG_CONFIG_DIRS debug3: Ignored env PATH debug3: Ignored env DESKTOP_SESSION debug3: Ignored env QT_IM_MODULE debug3: Ignored env JOB debug3: Ignored env PWD debug3: Ignored env XMODIFIERS debug3: Ignored env GNOME_KEYRING_PID debug1: Sending env LANG = en_US.UTF-8 debug2: channel 0: request env confirm 0 debug3: Ignored env GDM_LANG debug3: Ignored env MANDATORY_PATH debug3: Ignored env IM_CONFIG_PHASE debug3: Ignored env GDMSESSION debug3: Ignored env SESSIONTYPE debug3: Ignored env XDG_SEAT debug3: Ignored env HOME debug3: Ignored env M2_HOME debug3: Ignored env SHLVL debug3: Ignored env GNOME_DESKTOP_SESSION_ID debug3: Ignored env LOGNAME debug3: Ignored env M2_REPO debug3: Ignored env XDG_DATA_DIRS debug3: Ignored env QT4_IM_MODULE debug3: Ignored env DBUS_SESSION_BUS_ADDRESS debug3: Ignored env LESSOPEN debug3: Ignored env INSTANCE debug3: Ignored env TEXTDOMAIN debug3: Ignored env WINDOWPATH debug3: Ignored env XDG_RUNTIME_DIR debug3: Ignored env DISPLAY debug3: Ignored env XDG_CURRENT_DESKTOP debug3: Ignored env GTK_IM_MODULE debug3: Ignored env LESSCLOSE debug3: Ignored env TEXTDOMAINDIR debug3: Ignored env COLORTERM debug3: Ignored env XAUTHORITY debug3: Ignored env _ debug3: Ignored env OLDPWD debug3: Ignored env GIT_PREFIX debug1: Sending command: git-receive-pack '[my-username]/private-repo.git' debug2: channel 0: request exec confirm 1 debug2: callback done debug2: channel 0: open confirm rwindow 0 rmax 32768 debug2: channel 0: rcvd adjust 2097152 debug2: channel_input_status_confirm: type 99 id 0 debug2: exec request accepted on channel 0 Counting objects: 3240, done. Delta compression using up to 4 threads. Compressing objects: 100% (1264/1264), done. debug2: channel 0: read<=0 rfd 4 len 0 debug2: channel 0: read failed debug2: channel 0: close_read debug2: channel 0: input open -> drain Writing objects: 100% (3240/3240), 303.52 KiB | 0 bytes/s, done. Total 3240 (delta 887), reused 2940 (delta 750) debug2: channel 0: rcvd adjust 98453 debug2: channel 0: ibuf empty debug2: channel 0: send eof debug2: channel 0: input drain -> closed debug2: channel 0: rcvd adjust 106496 debug2: channel 0: rcvd adjust 106000 remote: GitLab: No such project debug1: client_input_channel_req: channel 0 rtype exit-status reply 0 debug2: channel 0: rcvd eof debug2: channel 0: output open -> drain debug2: channel 0: obuf empty debug2: channel 0: close_write debug2: channel 0: output drain -> closed debug2: channel 0: rcvd close debug3: channel 0: will not send data after close debug2: channel 0: almost dead debug2: channel 0: gc: notify user debug2: channel 0: gc: user detached debug2: channel 0: send close debug2: channel 0: is dead debug2: channel 0: garbage collecting debug1: channel 0: free: client-session, nchannels 1 debug3: channel 0: status: The following connections are open: #0 client-session (t4 r0 i3/0 o3/0 fd -1/-1 cc -1) debug1: fd 0 clearing O_NONBLOCK debug1: fd 1 clearing O_NONBLOCK Transferred: sent 315080, received 3428 bytes, in 5.9 seconds Bytes per second: sent 53846.8, received 585.8 debug1: Exit status 0 To gitlab:[my-username]/private-repo.git ! [remote rejected] dev -> dev (pre-receive hook declined) error: failed to push some refs to 'gitlab:[my-username]/private-repo.git' 
The fact that it is saying "No such project" means it is getting to this code in
internal.rb:if project && status && status.allowed? status else Gitlab::GitAccessStatus.new(false, 'No such project') endThat means GitLab either can't find the project, can't find your username, or thinks your user account doesn't have permission. I'm inclined to guess the latter, but I haven't been able to reproduce this issue myself.
I'm not sure if there is a better way, but would one of you be willing to insert print statements to help figure out what's going on? I would recommend:
In
/var/opt/embedded/service/gitlab-rails/lib/api/internal.rb:Rails.logger.info("!!! TEST #{actor} #{params} #{project} #{status} #{status.try(:allowed?)}") # Add if project && status && status.allowed? status else Rails.logger.info("!!! Status is #{status}") # Add Gitlab::GitAccessStatus.new(false, 'No such project') endCheck
/var/log/gitlab/production.logfor these messages.@stanhu Small correction,
statuscould benilon the first line of your second code block, so replacestatus.allowed?bystatus.try(:allowed?)-
@rptracker-dev were you able to gather more debug information with the suggestions above?
-
@stanhu , I didn't notice any changes in log output:
debug1: Authentication succeeded (publickey). Authenticated to gitlab.com ([54.93.71.23]:22). debug2: fd 4 setting O_NONBLOCK debug2: fd 5 setting O_NONBLOCK debug1: channel 0: new [client-session] debug3: ssh_session2_open: channel_new: 0 debug2: channel 0: send open debug1: Requesting no-more-sessions@openssh.com debug1: Entering interactive session. debug1: Remote: Forced command. debug1: Remote: Port forwarding disabled. debug1: Remote: X11 forwarding disabled. debug1: Remote: Agent forwarding disabled. debug1: Remote: Pty allocation disabled. debug1: Remote: Forced command. debug1: Remote: Port forwarding disabled. debug1: Remote: X11 forwarding disabled. debug1: Remote: Agent forwarding disabled. debug1: Remote: Pty allocation disabled. debug2: callback start debug2: fd 3 setting TCP_NODELAY debug3: packet_set_tos: set IP_TOS 0x08 debug2: client_session2_setup: id 0 debug1: Sending environment. debug3: Ignored env XDG_VTNR debug3: Ignored env XDG_SESSION_ID debug3: Ignored env CLUTTER_IM_MODULE debug3: Ignored env SESSION debug3: Ignored env GPG_AGENT_INFO debug3: Ignored env TERM debug3: Ignored env SHELL debug3: Ignored env XDG_MENU_PREFIX debug3: Ignored env VTE_VERSION debug3: Ignored env GJS_DEBUG_OUTPUT debug3: Ignored env WINDOWID debug3: Ignored env UPSTART_SESSION debug3: Ignored env GNOME_KEYRING_CONTROL debug3: Ignored env GJS_DEBUG_TOPICS debug3: Ignored env USER debug3: Ignored env LS_COLORS debug3: Ignored env SSH_AUTH_SOCK debug3: Ignored env SESSION_MANAGER debug3: Ignored env USERNAME debug3: Ignored env DEFAULTS_PATH debug3: Ignored env XDG_CONFIG_DIRS debug3: Ignored env PATH debug3: Ignored env DESKTOP_SESSION debug3: Ignored env QT_IM_MODULE debug3: Ignored env JOB debug3: Ignored env PWD debug3: Ignored env XMODIFIERS debug3: Ignored env GNOME_KEYRING_PID debug1: Sending env LANG = en_US.UTF-8 debug2: channel 0: request env confirm 0 debug3: Ignored env GDM_LANG debug3: Ignored env MANDATORY_PATH debug3: Ignored env IM_CONFIG_PHASE debug3: Ignored env GDMSESSION debug3: Ignored env SESSIONTYPE debug3: Ignored env XDG_SEAT debug3: Ignored env HOME debug3: Ignored env M2_HOME debug3: Ignored env SHLVL debug3: Ignored env GNOME_DESKTOP_SESSION_ID debug3: Ignored env LOGNAME debug3: Ignored env M2_REPO debug3: Ignored env XDG_DATA_DIRS debug3: Ignored env QT4_IM_MODULE debug3: Ignored env DBUS_SESSION_BUS_ADDRESS debug3: Ignored env LESSOPEN debug3: Ignored env INSTANCE debug3: Ignored env TEXTDOMAIN debug3: Ignored env WINDOWPATH debug3: Ignored env XDG_RUNTIME_DIR debug3: Ignored env DISPLAY debug3: Ignored env XDG_CURRENT_DESKTOP debug3: Ignored env GTK_IM_MODULE debug3: Ignored env LESSCLOSE debug3: Ignored env TEXTDOMAINDIR debug3: Ignored env COLORTERM debug3: Ignored env XAUTHORITY debug3: Ignored env OLDPWD debug3: Ignored env _ debug3: Ignored env GIT_PREFIX debug1: Sending command: git-receive-pack '[my-username]/private-repo.git' debug2: channel 0: request exec confirm 1 debug2: callback done debug2: channel 0: open confirm rwindow 0 rmax 32768 debug2: channel 0: rcvd adjust 2097152 debug2: channel_input_status_confirm: type 99 id 0 debug2: exec request accepted on channel 0 Counting objects: 3223, done. Delta compression using up to 4 threads. Compressing objects: 100% (1259/1259), done. debug2: channel 0: read<=0 rfd 4 len 0 debug2: channel 0: read failed Writing objects: 100% (3223/3223), 300.70 KiB | 0 bytes/s, done. debug2: channel 0: close_read Total 3223 (delta 880), reused 2924 (delta 743) debug2: channel 0: input open -> drain debug2: channel 0: ibuf empty debug2: channel 0: send eof debug2: channel 0: input drain -> closed debug2: channel 0: rcvd adjust 98453 debug2: channel 0: rcvd adjust 106496 debug2: channel 0: rcvd adjust 103119 remote: GitLab: No such project debug1: client_input_channel_req: channel 0 rtype exit-status reply 0 debug2: channel 0: rcvd eof debug2: channel 0: output open -> drain debug2: channel 0: rcvd close debug3: channel 0: will not send data after close debug3: channel 0: will not send data after close debug2: channel 0: obuf empty debug2: channel 0: close_write debug2: channel 0: output drain -> closed debug2: channel 0: almost dead debug2: channel 0: gc: notify user debug2: channel 0: gc: user detached debug2: channel 0: send close debug2: channel 0: is dead debug2: channel 0: garbage collecting debug1: channel 0: free: client-session, nchannels 1 debug3: channel 0: status: The following connections are open: #0 client-session (t4 r0 i3/0 o3/0 fd -1/-1 cc -1) debug1: fd 0 clearing O_NONBLOCK debug1: fd 1 clearing O_NONBLOCK Transferred: sent 312220, received 3532 bytes, in 1.8 seconds Bytes per second: sent 177131.5, received 2003.8 debug1: Exit status 0 To gitlab:[my-username]/private-repo.git ! [remote rejected] dev -> dev (pre-receive hook declined) error: failed to push some refs to 'gitlab:[my-username]/private-repo.git' -
@rptracker-dev, did you check
/var/log/gitlab/production.log? You may also have to restart GitLab (sudo gitlab-ctl restart). -
@stanhu , I don't use local gitlab installation. I've just registered in GitLab and add my project there. So, the problem is in gitlab.com internally.
-
Oh, I see. That should make it easier for @DouweM to diagnose.
@rptracker-dev Could you please let me know the exact user and project you are having this problem with? And the username for a user on the project who isn't having the problem?
You can email them to douwe@gitlab.com if you don't feel comfortable posting them here publicly.
-
@DouweM , I've sent details to email. The problem is still reproducible for me.
Thank you @rptracker-dev. We're actively looking into the issue!
@rptracker-dev We have so far been unable to reproduce the issue you're describing. If we replay the authorization request for your user account and the project in question, we are getting a successful response every time.
@fadsel Are you still having trouble pushing as well? Could you let me know the relevant user, project, key (if using SSH) and branch?
-
@DouweM , Can you advice anything for me? Is there any special environment variable used for project name determination? Should I provide my ssh key(private/public part) via email? I'm going to re-create my project this week, if problem won't be solved.
@rptracker-dev Have you tried pushing over HTTPS to see if that works? Otherwise I have now ideas right now. I'm working on making the error message more descriptive so you'll see something useful rather than "Project not found", which should help you (and us) track down the issue.
-
@DouweM , I've logged in via Google SSO, I'll set password to my profile and try. Thanks for idea.
-
@DouweM , I've tried to push changes via https, and got the same error:
Username for 'https://gitlab.com': rptracker-dev Password for 'https://rptracker-dev@gitlab.com': Counting objects: 3429, done. Delta compression using up to 4 threads. Compressing objects: 100% (1374/1374), done. Writing objects: 100% (3429/3429), 317.99 KiB | 0 bytes/s, done. Total 3429 (delta 921), reused 2926 (delta 743) remote: GitLab: No such project To https://gitlab.com/rptracker-dev/[private-repo].git ! [remote rejected] master -> master (pre-receive hook declined) error: failed to push some refs to 'https://gitlab.com/rptracker-dev/[private-repo].git' @rptracker-dev Well, at least it's consistent and apparently not a problem with your SSH key. We'll continue looking into it, sorry about the inconvenience.
mentioned in merge request !437 (merged)
-
@sanand0, I removed master from protected branches. The problem is still reproducible
@DouweM I have unchecked protected branch , Now I can only merge requests from a forked copy which is a temporary solution for me (cant push directly though )... for pushing directly I had to create a dublicate dev account which I push via my other machine ... but as owner still no luck , currently sticking to the merge request seems to work for now ,
PS :
🚶 just wondering why gravatars are not showing up , we are using GitLab 7.8.4 019ffd9a - but thats for another issue :)@fadsel Could you let me know the relevant user, project, key (if using SSH) and branch?
@DouweM we 've installed gitlab on our server , not inside gitlab.com --- and the branch is master i use the same username, fadsel
💧 Here is how you can re-produce the errorcreate a new project -> push -> then add new members as developers , developers-can-push enabled -> then try to push again :) -> error occurs
-> unprotect the branch -> push as owner -> error still occurs
🙊 -> push as dev -> no errors
💃 @fadsel I did the exact step you mentioned and I wasn't able to get the error. Any chance you could create a test repository on gitlab.com that reproduces this problem and share it with us?
@rptracker-dev Quick check, what do you see when you do
ssh git@gitlab.com?-
@DouweM ,
ssh git@gitlab.com PTY allocation request failed on channel 0 Welcome to GitLab, Sergei Barinov! Connection to gitlab.com closed. -
@DouweM , I think, the problem is not related with ssh authorization. Looks like the problem is in pre-receive hook on gitlab side.
@rptracker-dev I'm thinking the same thing, but I'd like to eliminate all other possibilities first. It's really weird, there's something keeping you two from pushing, but everything works when we try to copy your steps, and no one else seems to be having any problems.
If anyone can get pushing failing consistently with a repo and account on GitLab.com, and if they provide us with the exact commands, commits, files they're using, that would be incredibly useful.
@fadsel could you add the code @stanhu posted to your own gitlab instance and see what ends up in the logs?
GitLab 7.8.4 shouldn't make a difference, since @rptracker-dev is having the same issue with gitlab.com which is running 7.9.0.
mentioned in commit 8f3f6e9e
@rptracker-dev That's expected, 8f3f6e9e isn't on gitlab.com yet :)
@guancongli No luck yet, but you could help us out by letting us know the specific user, repo and branch you're having trouble with.
Hello, I've the same problem with some projects on our GitLab instance at work. But this problem appears only with HTTPS; I switch to SSH when it happens, then it works fine. I'm always the owner of the projects where this problem occurs. It concerns the version 7.9.4.
I can provide log with (https://gitlab.com/gitlab-org/gitlab-ce/issues/1236#note_993215) this change if necessary (tomorrow).
@schroeterm With 7.10.0, we've made the error messages a bit more descriptive to help us (and you) debug this. Is it possible for you to upgrade and try again then? If that's not possible, adding those debug logging commands and sharing the results with us would be very helpful.
@DouweM, here the logs
Client side
$ git push Counting objects: 7, done. Delta compression using up to 8 threads. Compressing objects: 100% (4/4), done. Writing objects: 100% (4/4), 352 bytes | 0 bytes/s, done. Total 4 (delta 3), reused 0 (delta 0) remote: GitLab: No such project To https://__COMPANYURL___/MS/mail.git ! [remote rejected] master -> master (pre-receive hook declined) error: failed to push some refs to 'https://__COMPANYURL__/MS/mail.git'Production.log
Started GET "/MS/mail.git/info/refs?service=git-receive-pack" for __IPADDRESS__ at 2015-04-23 09:08:14 +0200 Started GET "/MS/mail.git/info/refs?service=git-receive-pack" for __IPADDRESS__ at 2015-04-23 09:08:14 +0200 Started GET "/MS/mail.git/info/refs?service=git-receive-pack" for __IPADDRESS__ at 2015-04-23 09:08:15 +0200 Started POST "/MS/mail.git/git-receive-pack" for __IPADDRESS__ at 2015-04-23 09:08:15 +0200 Started POST "//api/v3/internal/allowed" for __IPADDRESS__ at 2015-04-23 09:08:15 +0200 !!! TEST #<User:0x0000000f040fd8> #<Hashie::Mash action="git-receive-pack" changes="c3c0d39baaa034b4cbd4d8cc2cdac9cc5791bdcc 1d3ebb9d7ce06816ab69ad21cad75a7cfee4cc8b refs/heads/master\n" project="MS/mail" route_info=#<Grape::Route:0x000000063a0920 @options={:prefix=>nil, :version=>"v3", :namespace=>"/internal", :method=>"POST", :path=>"/:version/internal/allowed(.:format)", :params=>{}, :compiled=>/\A\/(?<version>v3)\/internal\/allowed(?:\.(?<format>[^\/.?]+))?\Z/}> secret_token="__SECRETTOKEN__" user_id="11"> #<Project:0x0000000f0340f8> #<Gitlab::GitAccessStatus:0x0000000ef8cf88> false !!! Status is #<Gitlab::GitAccessStatus:0x0000000ef8cf88>@schroeterm All right, thanks. It appears though that those log commands didn't actually give as much information as I was hoping for. Could you try again with the below log commands instead?
Rails.logger.info("!!! TEST #{actor.inspect} #{params.inspect} #{project.inspect} #{status.inspect}") # Add if project && status && status.allowed? status else Gitlab::GitAccessStatus.new(false, 'No such project') endI've understood the bug.. it's not a bug
!!! TEST #<User id: 11, email: "xcraft@__SERVER__", encrypted_password: "__ENCPASSWORD__", reset_password_token: nil, reset_password_sent_at: nil, remember_created_at: nil, sign_in_count: 4, current_sign_in_at: "2015-03-12 12:46:23", last_sign_in_at: "2015-03-12 12:42:18", current_sign_in_ip: "__IPADDRESS__", last_sign_in_ip: "__IPADDRESS__", created_at: "2014-06-25 09:19:10", updated_at: "2015-03-12 12:48:12", name: "Xcraft", admin: false, projects_limit: 0, skype: "", linkedin: "", twitter: "", authentication_token: "__AUTHTOKEN__", theme_id: 2, bio: "", failed_attempts: 0, locked_at: nil, username: "xcraft", can_create_group: false, can_create_team: false, state: "active", color_scheme_id: 1, notification_level: 1, password_expires_at: nil, created_by_id: 3, last_credential_check_at: nil, avatar: nil, confirmation_token: nil, confirmed_at: "2015-03-12 12:48:12", confirmation_sent_at: "2015-03-12 12:48:12", unconfirmed_email: nil, hide_no_ssh_key: false, website_url: "", github_access_token: nil, gitlab_access_token: nil, notification_email: "xcraft@__SERVER__", hide_no_password: false, password_automatically_set: false, bitbucket_access_token: nil, bitbucket_access_token_secret: nil> #<Hashie::Mash action="git-receive-pack" changes="c3c0d39baaa034b4cbd4d8cc2cdac9cc5791bdcc 1d3ebb9d7ce06816ab69ad21cad75a7cfee4cc8b refs/heads/master\n" project="MS/mail" route_info=#<Grape::Route:0x000000046f0e38 @options={:prefix=>nil, :version=>"v3", :namespace=>"/internal", :method=>"POST", :path=>"/:version/internal/allowed(.:format)", :params=>{}, :compiled=>/\A\/(?<version>v3)\/internal\/allowed(?:\.(?<format>[^\/.?]+))?\Z/}> secret_token="__SECRETTOKEN__" user_id="11"> #<Project id: 218, name: "Mail", path: "mail", description: "", created_at: "2015-04-23 07:03:15", updated_at: "2015-04-23 07:03:15", creator_id: 3, issues_enabled: true, wall_enabled: false, merge_requests_enabled: true, wiki_enabled: true, namespace_id: 3, issues_tracker: "gitlab", issues_tracker_id: nil, snippets_enabled: false, last_activity_at: "2015-04-23 07:03:15", import_url: nil, visibility_level: 10, archived: false, import_status: "none", repository_size: 0.0, star_count: 0, import_type: nil, import_source: nil, avatar: nil> #<Gitlab::GitAccessStatus:0x0000000d190228 @status=false, @message="You don't have permission">In this log, it's the user Xcraft, but it's not right because I'm not this user. This one is used sometimes by a program on my computer which uses https://Xcraft:password@__SERVER__/blabla in order to clone some repositories. But on my system I've a cache credential enabled. Then when I work, this program changes my credential for the Xcraft user and this one can not push.
Then I've removed the cache, and everything works fine now.
Thank you @DouweM
@schroeterm Glad you got it working again!
mentioned in issue #1527 (closed)
@schroeterm - Could you be more specific about which cache you cleared? I seem to have a very similar problem that has persisted across multiple versions of gitlab.
@joeldjohnston the git cache credentials for https, IIRC I've just removed the file:
~/.git-credentialsIt's been at least 2 weeks (and a new release) since we heard from you. I'm closing this issue but if you still experience this problem, please open a new issue (but also reference the old issue(s)). Make sure to also include the necessary debugging information conforming to the issue tracker guidelines found in our contributing guidelines.
Can not push to my new file . please anybody solve my problem
Edited by username-removed-544202mentioned in merge request morpheus.lab/morpheus!21 (closed)
I have the same problem. I am the owner, but unable to push it for some reason. Please help
remote: GitLab: You are not allowed to push code to protected branches on this project.
To git@gitlab.com:balavishnu/PunjabSchoolNew.git ! [remote rejected] master -> master (pre-receive hook declined)Nothing worked in my case. I don't know why but at last I was stuck. Finally I removed by myself. Please take a look on my answer https://gitlab.com/gitlab-com/support-forum/issues/40. I hope it may help some one.
Mentioned in issue #24209 (closed)
