github respiratory authentication failed

[SkyeHarmse]

Hello , im trying to push my code through to github
ive downloaded git and ive done all the required things
after i put
git push -u origin master
it asks for my username and password inside of my terminal. (no window popped up)
i put my username SkyeHarmse
and my password.
it throws out this error:

Support for password authentication was removed on August 13, 2021.
remote: Please see https://docs.github.com/en/get-started/getting-started-with-git/about-remote-repositories#cloning-with-https-urls for information on currently recommended modes of authentication.
fatal: Authentication failed for 'https://github.com/SkyeHarmse/Qr-code-challenge.git/'

please can someone help me. ive tried every combination possible but nothing seems to be working. even tried changing my password. and tried looking for some other type of username that i might of used, but as far as i can see SkyeHarmse is my username.

[airtower-luna]

As the error message says you cannot use your password for git push or other Git operations (but you still need it to log in). You need to create a personal access token and enter that instead when Git asks for your password. When creating the token make sure to select the repo scope (for repository access, like pushing) and if you use Actions also workflow (required to modify workflow files).

[MohammadTaghizadeh]

authorization error when you used token and didn't get results I suggest changing the version of git. It means that you need to install the last version of git.

[Draigdxd]

But how do I use it
Like where do I paste it to get rid of the problem

[GabyCT]

From August 13, 2021, GitHub is no longer accepting account passwords when authenticating Git operations. You need to add a PAT (Personal Access Token) instead, and you can follow the below method to add a PAT on your system.

Create Personal Access Token on GitHub
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

[OlexNas]

Ok, I think I got it. It is a safety feature. It looks like when you build something on the top of your project, meaning you add something to your code without changing the existing version, you can easily push changes, but if you changed something in the base code, meaning you deleted or renamed or made any change to the last pushed commit, Git doesn't allow you to push the new version. It looks like there are at least three ways to fix this: you can create a new branch so the main stays intact, you can merge the old version with a new one, or you can do a force push using
--force push command, which allows you to overwrite the remote repository, thus erasing its history and causing data loss, which means you have to be very careful with force push, especially with public repositories...

[BioKobena]

I didn't find the solution :(
Eventually, I just created a new branch which didn't have the problem anymore.

Ah it's good, if it's OK so

[curiouscoddes]

Hello Everyone,

I hope this helps somebody.

I faced the error as below,

remote: Invalid username or password.
fatal: Authentication failed for 'https://github.com/username/repository/'

I had used PAT to clone my repo on my local machine. I went to my github account and generated another PAT and updated it on the /.git/config file.
and it worked

[HouseWei]

what should I do after I got a token?

[anapedra]

If the token in question is a GitHub Personal Access Token (PAT), it should be used in place of your password when cloning repositories or performing operations that require authentication.

When cloning repositories via HTTPS, GitHub will prompt you for your username and password. In this case, you should enter the token instead of the password.

[MohammadTaghizadeh]

it is possible that the problem is that you don't have the last version of git, so install the last version of git.

[shevitasoi]

I have reinstalled it and then try to push the code. Same issue of not accepting password. I tried token and tried using SSH key also.

[MohammadTaghizadeh]

try to install the new version of git and if it didn't work be careful that .git must be deleted from repo address when you are trying to remote origin.

[MohammadTaghizadeh]

if installing new version of git didn't word try to delete .git from the repo address that you are using for the remote origin address.

[BioKobena]

Oh thanks, I have try and my push is Ok now !
Thanks !

[macjayz]

Hi please how did you resolve that issue, its driving me crazy

[BioKobena]

You can uninstall the Git who are installing and go to the official website of Git and you install the last version of Git. After, you work

[NegasiAbe]

can it (re installing) affect my projects please ?

[MohammadTaghizadeh]

if you couldn't do push and did not have repo with pushes, probably reinstalling can't affect the projects.

[NegasiAbe]

I am facing the problem shown below ... i can't push what i did , and gives me same error when trying to push from different repos [image: image.png] with Regards

…

On Tue, Dec 6, 2022 at 10:52 AM Mohammad Taghizadeh < ***@***.***> wrote: if you couldn't do push and did not have repo with pushes, probably reinstalling can't affect the projects. — Reply to this email directly, view it on GitHub <#29193 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AOY462Y7AUMHZC2E7JTHMRLWL4EELANCNFSM56JI3NAA> . You are receiving this because you commented.Message ID: ***@***.***>

[DuduzileR]

hi did you end up finding a solution to this?

[BioKobena]

Ah ok, I had the same problem, I couldn't push my local repositories to the remote repository. For me the solution was to reinstall Git, the process I followed is more tedious and I believe there is an easier one.

[MARICEL30]

I have the same issue, I have updated git and is not working for me

[NegasiAbe]

Thank you very much for your swift respnse

…

On Thu, Dec 8, 2022 at 1:03 PM Negasi Abebe ***@***.***> wrote: I am facing the problem shown below ... i can't push what i did , and gives me same error when trying to push from different repos [image: image.png] with Regards On Tue, Dec 6, 2022 at 10:52 AM Mohammad Taghizadeh < ***@***.***> wrote: > if you couldn't do push and did not have repo with pushes, probably > reinstalling can't affect the projects. > > — > Reply to this email directly, view it on GitHub > <#29193 (reply in thread)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AOY462Y7AUMHZC2E7JTHMRLWL4EELANCNFSM56JI3NAA> > . > You are receiving this because you commented.Message ID: > ***@***.***> >

[farzankhan7850]

I have faced the same issue that let me do to run all commands.
At last after help from my friend I came to the solution that, instead of using the default terminal use the "VS Code Terminal" everything will definitely work.

[MARICEL30]

Thank you! it worked from the VS Code Terminal

[ossygarcia]

I'm facing the same issue but on my aws terminal

[code-JOA]

I just had the same issue. SOLUTION : Open your teminal from Vscode ( download VScode if you dont have it ) and push to github. Vscode will ask you to allow it access to your github. Click on allow and enter your github password. Now come to the VScode terminal and type git push.

[anapedra]

Cara estava com o mesmo pr desde que mudei para o linux. Acho que era um conflito pois tinha mais de uma conta no github, pesquisei fiz algumas configuraçẽs más nada resolvia. Segui a sua dica e foi batata, obrigada!

[PratikSK]

For whom an accepted solution did not work - try using "Fine-grained personal access tokens" instead of "tokens (classic)". It worked for me.

[BioKobena]

Thanks for your assistance.

[chocle254]

and how did you use it

[MACHIKA21]

I have created a new token ,it still gives me the same error

[MohammadTaghizadeh]

try to reinstall git.

[MohammadTaghizadeh]

Reinstall it in its new version.

[mlinux91]

Please help for below issue im unable to push from local to central repo. getting below error

remote: Support for password authentication was removed on August 13, 2021.
remote: Please see https://docs.github.com/en/get-started/getting-started-with-git/about-remote-repositories#cloning-with-https-urls for information on currently recommended modes of authentication.
fatal: Authentication failed for 'https://github.com/mlinux91/centralgit.git/'

[Basanagoudapatil02]

your password might have space in front, remove that space then try it

[nishkakhendry]

In case anyone is facing this error despite using a Personal Access Token to log in, it may be because the token does not have the required scope to do the task throwing this error.

Creating a new Personal Access Token with the relevant scopes ticked worked for me!

Attaching a screenshot of the token creation page showing where scopes can be chosen from. Scroll on that page to see the full list and choose the relevant ones-

[BioKobena]

Yeah it's true, it was my case I think

[michaelaskew6543]

It seems you are encountering an authentication error while trying to push your code to GitHub using Git. The error is likely due to using your GitHub password instead of an access token or a personal access token (PAT).

GitHub has made some changes to their authentication process, and as of August 13, 2021, they no longer support using passwords for authentication when pushing code using Git. Instead, they require using either an access token or a personal access token (PAT) as your password.

Here's how you can resolve the issue:

Generate a Personal Access Token (PAT) on GitHub:

Go to your GitHub account settings.
Click on "Developer settings" in the left sidebar.
Click on "Personal access tokens."
Click "Generate new token."
Follow the instructions to create a new token, and make sure to select the appropriate scopes/permissions for your needs (e.g., "repo" for full access to repositories).
Use the Personal Access Token (PAT) as your password:
Regards; apkfik

[CaglarTaha]

Okat but where I put on the tokken on my terminal

[BioKobena]

• You go to Github
• On Github you access to Settings
• You search token
• You generate an token
  And you follow the different next step

[AnuragNishad12]

hii everyone ,
I'm getting an error all over my github repository
this one

Can anyone knows how to solve it ?
Please help me

[Jagadeeesh6]

Hi , I did same Methi generate token and paste but still it's showing same error

…

On Thu, 20 Jul, 2023, 12:49 pm Anurag Nishad, ***@***.***> wrote: hii everyone , I'm getting an error all over my github repository this one [image: image] <https://user-images.githubusercontent.com/124987038/254804144-d960039f-bc1f-4a7c-a677-fc83e1aedf3d.png> Can anyone knows how to solve it ? Please help me — Reply to this email directly, view it on GitHub <#29193 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BBHY2RXDYV7RQXMJUBP3FGLXRDLZXANCNFSM56JI3NAA> . You are receiving this because you commented.Message ID: ***@***.***>

[BioKobena]

Can I know where are you deploying your version ? Git or other terminal ?

…

On Thu, Jul 20, 2023, 9:00 AM Jagadeeesh6 ***@***.***> wrote: Hi , I did same Methi generate token and paste but still it's showing same error On Thu, 20 Jul, 2023, 12:49 pm Anurag Nishad, ***@***.***> wrote: > hii everyone , > I'm getting an error all over my github repository > this one > [image: image] > < https://user-images.githubusercontent.com/124987038/254804144-d960039f-bc1f-4a7c-a677-fc83e1aedf3d.png> > > Can anyone knows how to solve it ? > Please help me > > — > Reply to this email directly, view it on GitHub > < #29193 (comment)>, > or unsubscribe > < https://github.com/notifications/unsubscribe-auth/BBHY2RXDYV7RQXMJUBP3FGLXRDLZXANCNFSM56JI3NAA> > . > You are receiving this because you commented.Message ID: > ***@***.***> > — Reply to this email directly, view it on GitHub <#29193 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A4JEWUMC4UVSERE4QNIMIADXRDXT3ANCNFSM56JI3NAA> . You are receiving this because you commented.Message ID: ***@***.***>

[BioKobena]

ohh you're welcome Have you fixed your bug ?

…

_____________________________________________ *Bio Paul Kobena* Etudiant à l'ESATIC 📩 ***@***.*** 📞 +225 05 74 62 00 56 Abidjan, Côte d'Ivoire biopaul.netlify.appp <https://biopaul.netlify.app> Le mar. 8 août 2023 à 17:18, Shubham Shejaval ***@***.***> a écrit :

thank you — Reply to this email directly, view it on GitHub <#29193 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A4JEWUNHFWDR4E6UWW624D3XUJYGLANCNFSM56JI3NAA> . You are receiving this because you commented.Message ID: ***@***.***>

[not-ana]

I had the same problem. It turned out I was just forgetting to check the permission boxes before saving changes.

[attiahana]

i have the same problem and i change token and dosen't work ,@SkyeHarmse how did you solve your problem

[wb7odyfred]

Here is a good 5 minute video, that demonstrates the same actions I wrote below. Fix Github Missing Password error

I used the above Classic Personal Access token method. I had to use Shift-Ctrl-V to paste the personal_access_token_line for the password entry, rather than Shift-Insert to paste the token_line from Classic Personal Access token. The Fine-Grained-Token did not work for me. But that might have been, I was using Shift-Insert . This Fine-Grained_Token might have worked if I used the Shift-Ctrl-V . Save the Personal_Access_Token string into a file. Don't forget or lose it.

git push -u origin stable-arm64/14 or git push -u origin main or git push -u origin master
Username for 'https://github.com': your_user_name_here
Password for 'https://[email protected]': ghp_NkIZxIwK_Personal_Access_Token_Classic_value

Answer the password question, by pasting or inserting the Personal_Access_Token in place of a previous Github password.
Hope the above is explicit enough to get you over the hump attiahana. Use Classic or Fine-Grained-Token Personal Access Token when it asks for password.

Otherwise you will get this error:
remote: Permission to your_user_name/ghostbsd-src.git denied to your_user_name.
fatal: unable to access 'https://github.com/your_user_name/your_repo_name.git/': The requested URL returned error: 403

[fer1980]

Thanks everybody, the the solution was token classic, Kali Linux,thanks for your help

[Jerrymansurjoe]

I appreciate your incredible work! Thank you for a job well done! Your dedication and efforts are truly appreciated. Congratulations! Your generosity gives me hope.

[anapedra]

🥰🙏🙏 Em sex., 26 de abr. de 2024 às 04:06, Jerry Mansur ***@***.***> escreveu:

…

I appreciate your incredible work! Thank you for a job well done! Your dedication and efforts are truly appreciated. Congratulations! Your generosity gives me hope. — Reply to this email directly, view it on GitHub <#29193 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AZETUJIQIZEED7VC345QEJ3Y7H4JDAVCNFSM56JI3NAKU5DIOJSWCZC7NNSXTOKENFZWG5LTONUW63SDN5WW2ZLOOQ5TSMRTGMYTMMI> . You are receiving this because you commented.Message ID: ***@***.***>

[arshadakl]

The error you're encountering is due to GitHub's removal of password authentication for Git operations. As of August 13, 2021, GitHub requires the use of token-based authentication for all Git operations¹[1]. Here's how you can resolve this issue:

1. Generate a Personal Access Token (PAT):

   • Visit your GitHub account settings.
   • Navigate to the Developer settings.
   • Go to Personal access tokens and generate a new token.
   • Make sure to select the appropriate scopes for the token, such as repo, admin:org, etc., depending on your needs.
   • Copy the generated token immediately, as you won't be able to see it again.

2. Use the PAT in place of your password:

   • When prompted for a password in the terminal, enter the PAT instead of your GitHub password.

3. Update your Git configuration (Optional):

   • If you want to avoid entering the PAT every time, you can update your Git configuration to store your credentials.

   • Use the following commands:

     git config --global credential.helper store

     Then push as usual, and the credentials will be saved

     git push -u origin master

   • Alternatively, you can switch to SSH authentication for a more secure connection:

     git remote set-url origin [email protected]:USERNAME/REPOSITORY.git

[shahidayub555]

i can't see anywhere personal access token under Developers setting .
plz guide more

[shahidayub555]

i got this PAT ,thx
Do I need to use this one time only ?
Also is this need to save in some file?

[BioKobena]

You have tried to generate one ?

[shahidayub555]

Do I need to create every time PAT CODE or I can save it somewhere ?I did try to save this code in new folder but it does not show any paste option by clicking right of mouse.plz guideSent from my iPhoneOn May 16, 2024, at 4:51 AM, Ramadan ***@***.***> wrote: ❤️❤️❤️ —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***>

[shahidayub555]

Do I need to create every time PAT CODE or I can save it somewhere ?I did try to save this code in new folder but it does not show any paste option by clicking right of mouse.plz guideSent from my iPhoneOn May 16, 2024, at 2:11 AM, Bio Paul Kobena ***@***.***> wrote: You have tried to generate one ? —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***>