git-receive-pack not permitted on Push

Question

I am using EGit in Eclipse, and attempting to push to Github. I made a commit locally, and then tried to push it upstream. I got this error:

 Can't connect to any URI: https://github.com/Buroa/Konklex.git (An internal Exception occurred during push: https://github.com/Buroa/Konklex.git: git-receive-pack not permitted)

I can't seem to find a way around it. Am I missing something here?

Does it work if you use the `ssh://` URL? (I've only ever pushed over SSH, not over HTTPS. But that's just me.) — Greg Hewgill, May 07 '12 at 01:37
possible duplicate of [How do I push to Git Repo given the following error: An internal Exception occurred during push: ssh://git@github.com/xxx/xxx.git: session is down](http://stackoverflow.com/questions/9003840/how-do-i-push-to-git-repo-given-the-following-error-an-internal-exception-occur) — Greg Hewgill, May 08 '12 at 03:03
issue is due to git hub new rule(to add generated token as password in password field in tool where you are uploading your code ) if you dont understand you can follow below video follow below link it will solve your issue https://youtu.be/rLEYw1caoBQ — anil, Aug 21 '21 at 05:09

score 25 · Answer 1 · answered Jun 23 '13 at 21:39

25

I know this is a old thread, but I struggled with the same for more than an hour today and finally found out this happened because on my egit push dialog window i had used a different userid

Once i entered the right github user, the push to the remote repository went through fine.

answered Jun 23 '13 at 21:39

Venkat

1,229
1
15
23

I had to reconfigure the push, with both my username and password, and check the "Store in Secure Store" – chrismarx Apr 08 '14 at 18:18
1

same here. I already had other projects in Eclipse which were using a user that was not a collaborator in the new project. – atmelino Jun 11 '14 at 02:36
Thanks. This is basically a very weird error message for "username/password not recognized" – Jonathan Benn Apr 13 '17 at 16:00
How to do this ? – nonozor Feb 26 '19 at 08:39
1

Note: GitHub recently changed its Authentication policy. Users have to use Personal Access Token (P.A.T) instead of password while doing pull or push or clone etc. Take a look at: https://docs.github.com/en/github/authenticating-to-github/keeping-your-account-and-data-secure/creating-a-personal-access-token – Shadyar Aug 14 '21 at 23:57

score 14 · Answer 2 · answered Mar 28 '17 at 14:41

14

As stupid as it may sound: Make sure you do have rights to push to the repo.

In my case the colleague hadn't given my user the push rights yet...

answered Mar 28 '17 at 14:41

fl0w

3,593
30
34

3

This is the typical reason why I encounter the error – Jonathan Benn Sep 28 '17 at 18:03

score 12 · Answer 3 · answered May 09 '14 at 12:58

12

just check "store in secure store" in context menu > team > remote > configure push to upstream > change. problem solved :D

answered May 09 '14 at 12:58

user3620506

129
1
2

2

The context menu entry was greyed out for me. Underlying reason for me was missing rights to push on the repo. – fl0w Mar 28 '17 at 14:43

Jonathan Benn · Answer 4 · 2022-09-01T13:00:32.273

8

git-receive-pack not permitted is equivalent to username/password not recognized

As others have posted, you could get the error message for many different reasons, including:

You don't have an account on Github
You didn't do the email verification to complete your account on Github
Your username does not have push rights to that repository (e.g. your username is not listed as a contributor)
You used the wrong username by accident (substituting with one that does not have push rights on that repository)
You entered the password wrong
You pushed using the wrong protocol (e.g. you used SSH or HTTPS, when only the other protocol was acceptable)
You provided the correct authentication but the email address you sent with it did not match what the server was expecting

edited Sep 01 '22 at 13:00

answered Sep 28 '17 at 18:12

Jonathan Benn

2,908
4
24
28

I was using token instead a user/pass (so my credentials are fine) , but my mistake was the user registered at the commit (not the user to push to remote). Hope helps. – danipenaperez Aug 23 '22 at 09:59
@danipenaperez I'm not sure I understand. What does "the user registered at the commit" mean? – Jonathan Benn Aug 29 '22 at 19:13
I'm not using http+basic auth to push my changes to remote git, I am using ssh key instead, so I will never could get a user/pass error. But in this scenario, when I do a local commit an email user needs to be configured locally. My mistake was configure userA@git.com in local git configuration, but my email registered on remote git server was userB@git.com, so on push commits y receive the git-receive-pack not permitted error (remember that I can push my changes because I am using ssh key, but remote git checks that email at merge request commit that matchs with associated ssh account email). – danipenaperez Aug 31 '22 at 07:10
Thanks for the clarification @danipenaperez . I have added your specific case to the list. – Jonathan Benn Sep 01 '22 at 13:01

score 7 · Answer 5 · answered Nov 01 '13 at 18:39

7

sometimes you need to verify your account e-mail on github

answered Nov 01 '13 at 18:39

Charleston

1,539
18
10

4

This answer seems like it could use more detail. – James Jenkins Nov 01 '13 at 18:57
how and where do you do that? – Deian May 03 '22 at 14:44

score 2 · Answer 6 · answered Sep 30 '15 at 14:19

In my case I had to accept the invitation to the organization on Github.

Initially, I was trying to push my changes and was getting the mentioned error.

After I clicked on the link from the invitation letter, my push succeeded. Look for the email with the following content in your inbox and click on the link to join:

Hi <username>,

<other_username> has invited you to join the <org_name> organization on GitHub. Head over to https://<github_address>/<org_name> to check out <org_name>'s profile.

To join <org_name>, follow this link:

https://<github_address>/orgs/<org_name>/invitation?via_email=1

Some helpful tips:

If you get a 404 page, make sure you're signed in as <username>.

You can also accept the invitation by visiting the organization page directly at https://<github_address>/<org_name>

If you were not expecting this invitation, you can ignore this email.

Thanks, The GitHub Team

score 2 · Answer 7 · answered Oct 07 '19 at 16:27

I faced this issue with eGit and AnypointStudio ( with https protocol)

Solution-

Generate a access token in the respective Git repo Settings, save this token aside.
Go to Git Repositories -> Your Project -> Remotes -> origin -> Right click on Push(Red Arrow) and select Change Credentials.

Enter the access token generated in the first step in the password box and username,save and try to Push your local commit now.

For me it worked.

score 2 · Answer 8 · answered Aug 14 '21 at 18:40

2

After the latest github update you cannot use password to access. Instead use 2FA or generate a token and place it in password field. Follow the link below.

Generate token

answered Aug 14 '21 at 18:40

Shrutika Sawant

31
1

score 2 · Answer 9 · answered Aug 16 '21 at 13:23

I resolved this using PATs(Personal Access Tokens). You can use the combination of PATs with usernames instead of passwords.

Follow this github guideline: https://docs.github.com/en/github/authenticating-to-github/keeping-your-account-and-data-secure/creating-a-personal-access-token

Personal access tokens (PATs) are an alternative to using passwords for authentication to GitHub when using the GitHub API or the command line.

If you want to use a PAT to access resources owned by an organization that uses SAML SSO, you must authorize the PAT. For more information, see "About authentication with SAML single sign-on" and "Authorizing a personal access token for use with SAML single sign-on."

score 2 · Answer 10 · edited Aug 24 '21 at 21:33

2

In newer updates of GitHub, applications are not allowed direct access to your account repositories. To overcome this, you have to create a token from "Settings > Developers > Create Token with Repository Rights" and use that instead of your password in eclipse or any other application. This will work. All the answers above are for before the update, so they won't solve the problem.

For a more detailed guide, you can refer to this video (it's not mine): https://www.youtube.com/watch?v=8x0ywtCOzxo

edited Aug 24 '21 at 21:33

Adrian Mole

49,934
160
51
83

answered Aug 19 '21 at 07:15

Ali Shaukat

25
4

Here is another link from github https://github.blog/2020-12-15-token-authentication-requirements-for-git-operations/ – godidier Aug 19 '21 at 09:43

score 1 · Answer 11 · answered Feb 22 '17 at 08:01

For some reasons egit doesn't seem to work with the Wincred credential store. You have to use the eclipse one.

Open the Git Repositories perspective.
Open the Remotes node and right click on origin (or the remote of your choice).
Click on Configure Push then Change... button
Fill in the Authentication section
Make a Dry-Run to test

That should do the trick.

score 1 · Answer 12 · answered Aug 11 '17 at 13:58

1

I encountered this error when pushing to a GitLab repo, the username I was using does not have permissions to push to the branche's repository.

Changed the permission's level from reporter to master solved the problem.

answered Aug 11 '17 at 13:58

YellowStrawHatter

856
7
16

score 1 · Answer 13 · answered Nov 05 '21 at 11:23

1

for people wondering how to fix this for Bitbucket repo + eclipse IDE

go to Preferences->Git and then change Http Client to Java built-in HTTP

This resolved the issue for me.

answered Nov 05 '21 at 11:23

Lars Hendriks

998
5
22

Thanks! Save my day as well, Just wondering if it's working on VS but not in eclipse! – TheFoxLab Jan 07 '22 at 04:19

score 0 · Answer 14 · answered Apr 10 '17 at 13:42

In my case, it was because the permissions. we did some migration from gitlab to github. My colleague created a private project from our old project which I was working on. And after I finished, I found I was not able to push and got this error. Finally, we found it was because I wasn't added to the collaborator of this project. I thought it should be automatically done since I am one of the contributors of this project already. Hope it would be helpful for someone with similar issue.

score 0 · Answer 15 · answered Jun 15 '17 at 12:02

If you ever run into a git-receive-pack not permitted error when using Git, chances are that it's a configuration issue on your end.In my case, I had cloned the repository using via https (which required authentication). However, pushing failed with the aforementioned error. This was due to the fact that I was only allowed to push via SSH. Therefore, once I changed the protocol in the configuration for my checkout, all was well again.

Since I use Eclipse (and eGit), it might be handy for some to know that the configuration settings for a Git-cloned project can be accessed via the project's context menu (right click), and choosing Team, Remote, and "Configure Fetch from upstream" or Configure Push to upstream", as applicable.

Hope this helps!

score 0 · Answer 16 · answered Jul 16 '19 at 10:27

Since my organization requires us to use SSH keys instead of username+password the way to make it work for me was:

Right-click on your project in Eclipse --> Team --> Remote --> Configure Push to Upstream
Next to the URI click on "Change"
Choose protocol ssh
Under Authentication --> User insert git (it seems that eclipse / git will automatically search for your id_rsa key file if you use the default username here - I tried adding my real username but that never worked)
Finish & Save and Push

score 0 · Answer 17 · answered Jun 13 '20 at 08:00

0

Surely your git user id and password are mismatched on configuration. Please recheck and make sure that your credentials are correct.

answered Jun 13 '20 at 08:00

Anthoni Lawrance Arokiyasamy

39
4

score 0 · Answer 18 · answered Mar 16 '21 at 09:06

Another issue could be that you have not checked all necessary checkboxes when creating the personal access token for Github.

In my case this was my mistake and by creating a new token with all rights / checkboxes checked when creating the personal access token, it worked fine.

score 0 · Answer 19 · answered May 18 '21 at 07:51

Go to Bitbucket - Personal Settings - Access Management - App Passwords - Click 'Create app password' Button

Provide any name in 'Label' fields

Select all check boxes in Permissions Section

Click 'Create' Button

A Password will be generated. Copy this Password and save it to any local text file.

Go to Credential Manager - Windows Credential Manager

Delete the Bitbucket Logins saved.

Now go to Eclipse and try to do Commit and Push again

When prompted for Password, Provide the copied generated app password.

Now the Commit and Push should be successful without git-receive.-pack not permitted Error.

enter image description here

score 0 · Answer 20 · answered Aug 16 '21 at 00:24

0

Stumbled upon this for a long time and finally found the answer. In the Password section, we should not be entering the GitHub login password, instead we have to enter the Personal Access Token. Below link shows how to create the Personal Access Token: https://docs.github.com/en/github/authenticating-to-github/keeping-your-account-and-data-secure/creating-a-personal-access-token

answered Aug 16 '21 at 00:24

Sawan Upadhyay

1

While this link may answer the question, it is better to include the essential parts of the answer here and provide the link for reference. Link-only answers can become invalid if the linked page changes. – Tyler2P Aug 18 '21 at 10:24
@Tyler2P I do agree with your point. But in this case, the answer to the question would be to enter Personal Access Token instead of Password, and the link shared just talks about how to setup Personal access token just in case someone doesn't know. – Sawan Upadhyay Aug 19 '21 at 18:16

score 0 · Answer 21 · answered Aug 20 '21 at 17:38

Try this

This error is because of the upgrade. So you need to go to

Settings > Developer settings > Personal access tokens > Generate Token

Select the first option & click generate
Use this generated token as password of git

https://www.youtube.com/watch?v=rLEYw1caoBQ

score 0 · Answer 22 · answered Aug 19 '23 at 10:25

0

In my case, I resolved this issue by changing the GitHub token, I regenated the token and given in eclipse. by the way I used the Fine grained token on github.

we need to give the permissions for token users.

answered Aug 19 '23 at 10:25

Gaganam Krishna

121
1
4

score -1 · Answer 23 · answered Jul 07 '20 at 09:41

-1

Very basic but it happened to me: I didn't verify my email. Check you email, press the "verify email" button and then try pushing again.

answered Jul 07 '20 at 09:41

Asma Rahim Ali Jafri

1,173
2
15
22

score -1 · Answer 24 · answered May 13 '21 at 06:44

-1

Simple answer is - You don't have the write permission to the repo you are trying to push.

answered May 13 '21 at 06:44

Rishab Jula

97
4

score -1 · Answer 25 · answered Jul 28 '21 at 08:00

With the latest changes in GitHub, try this link. Now instead of actual password you need to pass token as password.

Refer - https://docs.github.com/en/github/authenticating-to-github/keeping-your-account-and-data-secure/creating-a-personal-access-token

git-receive-pack not permitted on Push

25 Answers25

Try this

Linked