You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
From Yesterday , i am unable to login using Git bash , Its prompting for password , even though i am entering the correct password its keep throwing error. Can someone help me out here .
These instructions on the blog post are trash BTW starting with 'Personal Settings' is not an option when you click on your avatar, under the settings under your Avatar there are no options to Create app password.
If you are making drastic and required changes to something that has been the status quo for over a decade try and do better.
If you are following the blog post, navigate to bitbucket.org, this is not located under your Atlassian profile.
Then from the git command line check that you are using your Atlassian user name:
git remote --view
If it's contains something like 'email@example.com' change it to 'firstname.lastname@example.org' using the same git remote command.
Setup a new password per the blog post with what permissions who knows, no guidance given so I gave mine Repositories: Read and Write privilege's I don't know if it needs Admin.
Set the password with
git config user.password xxxxnewlygeneratedpasswordxxx
Hi, @Shan, welcome to the community!
By your description, it seems that the issue you are facing is related to the recent changes with the removal of support for Atlassian account password for operations GIT over HTTPS and API requests.
This was announced in our Blog post Deprecating Atlassian account password for Bitbucket API and Git activity and shared on multiple email communication sent to our customers in the last few months. This announcement was also included in the terminal message response for HTTPS GIT transactions.
For more details on how to resolve this issue, please refer to our community post here:
This post provides detailed instructions users need to take to help resolve the issue. This community post also provides answers to FAQ, make sure you scroll to the bottom of the page to find the answers.
If after reading the community post you have further questions, please do reach out and we will be happy to help.