Github 403 ошибка push failed

I just got the same problem and just figured out what’s cause.

Github seems only supports ssh way to read&write the repo, although https way also displayed ‘Read&Write’.

So you need to change your repo config on your PC to ssh way:

1. Edit .git/config file under your repo directory.
2. Find url=entry under section [remote "origin"].
3. Change it from:
   url=https://MichaelDrogalis@github.com/derekerdmann/lunch_call.git
   to:
   url=ssh://git@github.com/derekerdmann/lunch_call.git
   That is, change all the texts before @ symbol to ssh://git
4. Save config file and quit. now you could use git push origin master to sync your repo on GitHub.

To definitely be able to login using https protocol, you should first set your authentication credential to the git Remote URI:

git remote set-url origin https://yourusername@github.com/user/repo.git

Then you’ll be asked for a password when trying to git push.

In fact, this is on the http authentication format. You could set a password too:

https://youruser:password@github.com/user/repo.git

You should be aware that if you do this, your github password will be stored in plaintext in your .git directory, which is obviously undesirable.

answered Jul 6, 2012 at 19:41

One small addition to Sean’s answer.

Instead of editing .git/config file manually, you can use git remote set-url command.

In your case it should be:

git remote set-url origin ssh://git@github.com/derekerdmann/lunch_call.git

I find it easier and cleaner, than messing around with dot-files.

• help.github.com: Changing a remote’s URL

Edit .git/config file under your repo directory

Find url= entry under section [remote "origin"]

Change it from url=https://github.com/rootux/my-repo.git to
https://USERNAME@github.com/rootux/my-repo.git

where USERNAME is your github user name

answered Nov 7, 2012 at 9:39

The other answers that suggest switching to SSH sort of miss the point. HTTPS is supported, but you must log in with you GITHUB password, not your SSH passphrase (which was what was giving me the same exact error).

I was having the same problem, but making sure to use my actual GitHub password at the terminal password prompt fixed the solution with no alteration to the config, or resorting to SSH.

The reason it is important to note this, is many public institutions (such as my school) will block SSH, but allow HTTPS (which is the only reason I started cloning over HTTPS in the first place).

Hope that helps anyone else having the same issue…

answered Jan 17, 2012 at 17:27

If you are using windows, sometimes this may happen because Windows stores credentials for outer repo (in our case github) in its own storage. And credentials that saved there can be different from those you need right now.

So to avoid this problem, just find github in this storage and delete saved credentials. After this, while pushing git will request your credentials and will allow you to push.

answered Apr 18, 2018 at 7:34

Same error and resolution on Mac OS X.

Everything was working fine till I created a new account on GitHub and tried to push

$ git push -u origin master

And got the error:

remote: Permission to NEWUSER/NEWREPO.git denied to OLDUSER. fatal: unable to access ‘https://github.com/NEWUSER/NEWREPO.git/’: The requested URL returned error: 403

It should have fixed by setting the user.name either for global or current repo

$ git config –-global user.name NEWUSER
$ git config user.name NEWUSER

But it didn’t.

I got it fixed by deleting the OLDUSER associated with GitHub from Keychain Access app under Passwords section. Then the push command went successful.

$ git push -u origin master

reference

This works for me -:

git remote set-url origin https://username@github.com/user/repo.git

Hope it helps

answered Jun 27, 2012 at 14:44

gsfgsf

1,76816 silver badges11 bronze badges

answered Sep 16, 2011 at 0:32

nevesneves

32k25 gold badges153 silver badges188 bronze badges

answered Sep 16, 2011 at 3:29

I faced the same error and the cause was stupid — I did not have privileges to commit to selected repository. I did not know that I have to

1. fork selected project first
2. clone repository locally
3. commit my changes locally
4. push changes to my github clone
5. request pull request to upstream

as described in https://help.github.com/categories/63/articles

answered Mar 2, 2014 at 14:54

I actually had a very simple fix to this. All i did was edit the git config file differently after cloning the repository. The remote origin url is what you need to edit in your default config file. It should look like seen below

[core]
    repositoryformatversion = 0
    filemode = true
    bare = false
    logallrefupdates = true
[remote "origin"]
    fetch = +refs/heads/*:refs/remotes/origin/*
    url = https://*username*@github.com/*username*/*repository*.git
[branch "master"]
    remote = origin
    merge = refs/heads/master

answered Oct 13, 2015 at 23:00

Do this for a temporary fix

git push -u https://username:password@github.com/username/repo_name.git master

answered Sep 19, 2018 at 15:41

1. Click on your repository
2. On the right hand side, click on «Settings»
3. On the left hand side option panel, click on «Collaborators»
4. Add the person name you know in GitHub
5. Click «Add Collaborators»

After this our «Push to Git» worked fine.

change it from

url=https://MichaelDrogalis@github.com/derekerdmann/lunch_call.git 

to

url=ssh://git@github.com/derekerdmann/lunch_call.git

It works!

Do not forget the «git» before the «@».

SMSMSMSM

1,4793 gold badges19 silver badges34 bronze badges

For those having permission denied 403 error while using ssh(according to Xiao) or http urls
try these commands

>git config --global --unset-all credential.helper

>git config --unset-all credential.helper

with administrator rights

>git config --system --unset-all credential.helper

None of the above answers worked for my enterprise GitHub account. Follow these steps for pushing via ssh key generation way.

Create a repo by visiting your git account.

Generate ssh key:

ssh-keygen -t rsa -C "your_email@example.com"

Copy the contents of the file ~/.ssh/id_rsa.pub to your SSH keys in your GitHub account settings.
Test SSH key:

ssh -T git@github.com
clone the repo:
git clone git://github.com/username/your-repository

Now cd to your git clone folder and do:

git remote set-url origin git@github.com:username/your-repository.git

Now try editing a file (try the README) and then do:

git add -A
git commit -am "my update msg"
git push -u origin master

Update: new git version seems to recommend not to have any file while new repo is created. Hence make aa blank repo.

answered Feb 13, 2018 at 7:02

Below is the solution

For Windows you can find the keys here:

control panel > user accounts > credential manager > Windows credentials > Generic credentials

Next, remove the Github keys.

In mac

1-In Finder, search for the Keychain Access app.

2In Keychain Access, search for github.com.

3-Find the «internet password» entry for github.com.

4-Edit or delete the entry accordingly.

answered Apr 13, 2020 at 9:27

What worked for me:

My repo was a fork and still linked to the the parents repo.

git remote -v

Will tell you if it is your repo or not.

git remote set-url origin https://github.com/USERNAME/OTHERREPOSITORY.git

Allows you to reconfigure it to your repo and then allow you to push.

sailfish009sailfish009

2,5011 gold badge24 silver badges31 bronze badges

For anyone curious, my mac machine vs lucid vm ran git 1.7.6 vs 1.7.0.4, and the exact same repo was pushable from my mac (newer git) but not the VM

Same curl version. Perhaps some older git versions don’t support https pushes?

answered Mar 5, 2012 at 23:49

answered Mar 5, 2016 at 15:01

Try below command using administrator permission. This command solved my issue. Hope it will resolve your problem.

git config --system --unset-all credential.helper

answered Apr 25, 2020 at 18:03

NicoNico

1,7882 gold badges23 silver badges41 bronze badges

I figured out my own variation of this problem.

The issue was not changing the protocol from https to ssl, but instead,
setting the Github global username and email! (I was trying to push to a
private repository.

git config --global user.email "your_github_email_@email.com"

git config --global user.name "Your full name"

answered Feb 17, 2014 at 21:08

AndyLAndyL

14.2k14 gold badges43 silver badges70 bronze badges