The requested URL returned error: 403 Forbidden

[sunnytranco]

When I finish step 3 of the wizard, this error shows up:

error: The requested URL returned error: 403 Forbidden while accessing https://sunnytranco:{password}@github.com/sunnytranco/gravLearn2.git/info/refs fatal: HTTP request failed

I've already tested my connection, it's fine

[w00fz]

Make sure the password is actually correct, I know it sounds like a stupid advice but I did have this issue myself before 😃. Also, if you are using 2FA with GitHub, you cannot use the actual password from remote, you need to create an Access Token and use that instead of your password.

[w00fz]

You do still a password even if it's public. The authentication is required in order to guarantee you have PUSH permissions.

[ghost]

how can I create an access token

[nitinsreevstv]

Go to settings > Developer Settings > personal access tokens > Generate a Token (Classic)

[paulhibbitts]

Hi @Amina-Zafar , it depends on the Git-based service you are using. For example, with GitHub you could create a token at https://github.com/settings/tokens

[paulhibbitts]

Sorry @best-lucky1030 , I don't have much technical knowledge of using tokens etc.

[ghost]

Thanks

…

On Tue, Mar 5, 2019 at 11:57 PM Paul Hibbitts ***@***.***> wrote: Hi @Amina-Zafar <https://github.com/Amina-Zafar> , it depends on the Git-based service you are using. For example, with GitHub you could create a token at https://github.com/settings/tokens — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#39 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ArlAI_G1QF-4nuYlHBw0wJ8_c-MH0CShks5vTr4PgaJpZM4NCC1J> .

[ghost]

unable to push my code into my current account, getting access denied 403 error. I have tried many options making new repos, by changing drive, even created repo on Bitbucket but still, my repo is associated with my colleague GitHub account. Please guide me how can I resolve this issue?

[bonsoirval]

Create a new token, making sure to tick repo and or user

[zahirzohair]

This worked for me. Thanks man!
Basically, when you generate new token there are many checkboxes to be checked first, I checked the checkbox for repository only and then generated the token. it worked fine.

[samuellukudu]

Yeah, this works. Thanks

[NuraiymMamatova]

This works! Thanks!

[paulhibbitts]

Did you follow these steps https://www.youtube.com/watch?v=avcGP0FAzB8 (interface slightly different now)? Are you getting any error messages?

[ghost]

Thanks a lot, i will check it

…

On Mon, Mar 11, 2019 at 9:34 PM Paul Hibbitts ***@***.***> wrote: Did you follow these steps https://www.youtube.com/watch?v=avcGP0FAzB8 (interface slightly different now)? Are you getting any error messages? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#39 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ArlAIwZZr594cV6jXTIbJgPJBhis9SV_ks5vVoWAgaJpZM4NCC1J> .

[ghost]

I have viewed this video but this is not my problem solution. Actually, my repo is public and my colleague repo is also public. The problem is, I am unable to push my code into my account repo this is the main problem that I am facing. Please help me.

[ghost]

Moreover, when I push my code into GitHub then give the error, 'access denied from my colleague account', which is no more login on my laptop.

[paulhibbitts]

This sounds less like a GitSync Plugin issue and more of a Git/GitHub issue... sorry but I don't think I can be of any help with that.

[ghost]

It's okay

…

On Tue, Mar 12, 2019 at 8:46 PM Paul Hibbitts ***@***.***> wrote: This sounds less like a GitSync Plugin issue and more of a Git/GitHub issue... sorry but I don't think I can be of any help with that. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#39 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ArlAI4w5jeXnQaDGmSMR3XD_ThW8EZitks5vV8vTgaJpZM4NCC1J> .

[habibakij]

fatal: unable to access 'https://github.com/habibakij/Testing.git/': The requested URL returned error: 403
i face this problem.. username habibakij

[ingrid-liu]

did you fix it now? I met same problem:(

[rizkytegar]

i have same problem

[AndABond]

fatal: unable to access 'https://github.com/habibakij/Testing.git/': The requested URL returned error: 403
i face this problem.. username habibakij

Did you manage to fix this error, Facing the same thing

[Ritesh8732]

fatal: unable to access 'https://github.com/habibakij/Testing.git/': The requested URL returned error: 403
i face this problem.. username habibakij

Did you manage to fix this error, Facing the same thing

i also faced the same issue
Here is how i sloved this
first of all you need to generate the PAT from github ,
now paste this PAT when it says to enter password for your github
then it will prompt you a error:unable to access 'https://github.com/habibakij/Testing.git/': The requested URL returned error: 403
so to fix this go to
go to github account => settings => developer settings => personal access token =>
there you will see a token that you generated earlier.
click on that token provide all the access by clicking the checkbox .
This will solve your problem

[andreamgonzalez]

Thank you! I spent the majority of the day reading "solutions" that weren't the problem! You saved my evening.

[Piyush-Mishra-10]

where is developer settings?

[KirilNit]

Have the same issue with my repo. Who managed this or anyone who can help?

[Reydel-Gutierrez]

I had this error while working on Linux environment,

I was able to fix it by creating personal access token in GitHub with most of the permissions changed to read and write. Made sure to regenerate the token if you edit the permissions.

[Sleekboss]

im getting this can some one help me

[Fireroman]

Sooooo many years, but GitHub team still can't solve this issue... unbelievable

[SAMHRACHI]

I get the same issue... Guys make sure that u r using GitHub Personal Access Token.
Here are the steps for that. From your GitHub account, go to Settings → Developer Settings → Personal Access Token → Generate New Token (Give your password) → Fillup the form → click Generate token → Copy the generated Token, it will be something like ghp_sFhFsSHhTzMDreGRLjmks4Tzuzgthdvfsrta

The next mistake is that while creating a Token some people a forgetting to checkmark options below for repo. Do it guys!

Then just write ur username in GitHub and for password field past the personal token like I show below.

$ git clone https://github.com/YOUR-USERNAME/YOUR-REPOSITORY

Cloning into YOUR-REPOSITORY...
Username:
Password: <type your password or personal access token (GitHub)

hope that helped mate :)

Some additional cources that can be helpful

https://stackoverflow.com/questions/68775869/message-support-for-password-authentication-was-removed-please-use-a-personal

[SAMHRACHI]

Thanks u man!!!! . U can't imagine how much I respect it!!!!!. You're always welcome! U can reach me for any question!!!

…

On Mon, Jan 23, 2023 at 3:45 AM Andrea Michelle ***@***.***> wrote: Thank you! I spent the majority of the day reading "solutions" that weren't the problem! You saved my evening. — Reply to this email directly, view it on GitHub <#202 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A3YX4CT3ZZBSE77PT6BMV7TWTXBCTANCNFSM5BLWUY6Q> . You are receiving this because you commented.Message ID: <trilbymedia/grav-plugin-git-sync/repo-discussions/202/comments/4751964@ github.com>

[SAMHRACHI]

Awesome!

…

On Fri, Jan 27, 2023, 05:17 Samuel Lukudu ***@***.***> wrote: Yeah, this works. Thanks — Reply to this email directly, view it on GitHub <#202 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A3YX4CQ4M454NHL5FP4OQ7TWUMOZTANCNFSM5BLWUY6Q> . You are receiving this because you commented.Message ID: <trilbymedia/grav-plugin-git-sync/repo-discussions/202/comments/4792741@ github.com>

[irohanrajput]

I think the problem is somewhere in the options that are to be checked while generating token.
I found the the solution here : https://www.youtube.com/watch?v=84caV_3RKgA&ab_channel=THEPROTONGUY

WORKED LIKE MAGIC 🍻🍻

[gcloud11]

After entering 'git push origin master' this message appears after using a beta token key when prompted for a password:

gaylacloud@Gaylas-MBP Portfolio % git push origin master
remote: Permission to gcloud11/Portfolio.git denied to gcloud11.
fatal: unable to access 'https://github.com/gcloud11/Portfolio.git/': The requested URL returned error: 403

I also used Homebrew code:

brew tap microsoft/git
brew install --cask git-credential-manager-core

which then proceeded to ask for a password. I entered the beta token key then used github actual password, still no good

Could someone assist?

[angelodavido]

I think the problem is somewhere in the options to be checked while generating tokens.
I found the solution here https://bobbyhadz.com/blog/support-for-password-authentication-was-removed-on-august

[habbanpaz]

I was facing the same problem. Basically another user was logged in on GitHub. All you need to go and remove it from the Generic credentials. To do so:

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

Next, remove the GitHub account.

[ShubhamDobhal-371]

Goto Control Panel->User Accounts->Credential Manager->Generic Credentials->click on github.com->remove username & Password.

[Wayne0758]

Helpful!

[rockaline]

Even though, nothing worked for me... What should I do?
I am using a public repo, which I am the owner...

[Hayelalfaisali]

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:

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

[Mohammed-abdullah-abdullah]

thanks it works for me very good

[deleSerna]

Even though I have used the correct personal access token ( fine grained access- token), I ran into the same issue . While creating the fine grained access- token, I tried to give the right commit access scope but I was still getting the same issue.
Then I used the classical token and gave repo access to the token and then push worked fine.
Therefore, I am thinking that with the fine grained token, I did not give the correct permission.

Also, set your remote url in the following way so that you do not need to enter your username ( not email) every time.
git remote set-url origin https://[email protected]/username/repositoryname.git