Atlassian Team members are employees working across the company in a wide variety of roles.
March 15, 2022 edited
@naydsonmariosalpj can you provide me with more details so I can try to help. Are you doing this from your terminal? Is your terminal prompting your to enter your password? if it is not then password is being stored in your git configred credential helper. In that case, you will need to remove the existing account password being stored, then when you try to push/pull you should be asked for your password and you will enter your app password and will most likely be stored in your credential helper for future git ops.
Atlassian Team members are employees working across the company in a wide variety of roles.
March 15, 2022 edited
@sosterhoudt as I've noted in previous comments if you are using the Bitbucket extension for Visual Studio (not VS Code), then that is a community-created extension that Atlassian/Bitbucket did not create nor does it maintain. In fact, that extension is actually not maintained anymore. That's most likely why the error message from using that extension is not good. I would advise caution using community extensions that are no longer maintained as other future issues may arise because of the nature of no longer being maintained.
I entered the app password into Sourcetree on mac os but I still get the error: Permission denied (publickey). The guide I followed didn't really match up with what I'm seeing in Sourcetree. For instance, no mention was made of protocol (do I choose https or ssh? With ssh it isn't even possible to enter the app key.) Can someone please explain to me how to get this working again in plain English?
In Sourcetree (Windows), Tools->Options->Authentication: Delete all credentials Add a new one using same ID used to create app password. basic, Refresh password, paste in app password
Successfully change to app password under the environment of using bitbucket git + source tree for windows by following steps in this post. Thanks a lot!
But in shared repositories, every user should create their own "App password" for your specific user. So it is like using your user password but with more (and useless) steps.
So to update on Teamcity...I managed to get it working with a little help from TC support but the main thing to update is the VCS Root settings username and password. Sometimes they are sys variables but that was not working even after updating those variables. So they key is to edit those values to be your Bitbucket username and the associated app password. Everything then connected properly.
I had problems with Source tree and got that straightened out and my command like was working fine too.
I was happy but after lunch my command line failed to fetch, authentication with "the message". It popped up an Atlassian login window, I entered my App Password for Bitbucket and failed and then I got a git for windows popup to enter my password. I pasted my App Password again. and it's ok. what a PITA.
I hope my SSH doesn't break next!
Update: I went in to my windows credential manager and edited all the Atlassian credentials pasting my app password in each. Then tried the command line again, it failed and I pasted app password in Atlassian and git-for-windows pop ups. Then it proceeded to fetch!
FYI: My repos had different protocols on the remotes, one was git@bitbucket and the other https://user_name@bitbucket. So I must have cloned one from Source tree and the other from the command line..
After trying various suggestions from this thread, this simply does not work. I still get the `remote: Bitbucket Cloud recently stopped supporting ...` message.
Please, somebody from Atlassian, show an example configuration for the git command-line, please DO NOT paste the previous instructions. You need recreate the steps: create a dummy account, create a dummy repository, check that it works as you think that it works (because I suspect that it really doesn't). Then provide the exact configuration that works for you: app passwords, `.gitconfig`, `.git/config`, everything, paste it here exactly with no editing.
Atlassian Team members are employees working across the company in a wide variety of roles.
March 17, 2022 edited
@brunopostle not everyone uses the same setup; there are different steps for different setups.
If you provide me with more details I can try and help. Can you please tell me if you created an app password already? Also when you are trying to push/pull from your terminal to Bitbucket Cloud is your terminal prompting you to enter your password (this is where you enter your new app password instead of your account password). If you are not getting prompted then that means your credentials are being stored in your configured git credential helper
Also, can you please tell me if you are using Windows or Mac (or Linux)?
@David DansbyI'm using basic git on the command-line with Linux and cygwin, yes I have created an app password. I have tried various username and password combinations, the error is the same. I have tried entering the app password on the prompt when I try to push, I have tried the username:password@bitbucket.org format both in a git push and in the .git/config file.
Please can you create a fresh account and repository, configure it so that it works, and paste the entire configuration here
Now running smoothly after many days of nightmares (crossing fingers).
The missing step that has rectified was deleting the extra password file in AppData (found earlier in this thread). This in addition to removing / resetting app password in Windows credential manager.
As a newer developer, I'm still getting my feet wet with learning how to do these basic tasks. This is incredibly frustrating. I used to be able to go into a project, select clone, choose https or ssh, and now neither work.
I created an app password, but how does that work if I'm just a member of a repository? I have admin rights to the repositories that I'm trying to do get/pulls.
I think this is all a bunch of BS. If I want to have a repository, create users, assign them permissions, etc. I'm controlling the security of that repository that way. Why does bitbucket have to "decide" how to secure my repo?
I'm pissed off and now I can't do updates to codes for work.
**Edit - after reading some of the other comments, I was able to get this to work. Regardless though, what a time waster and I don't see how this is any more secure. You're passing off the passkey in clear text. Any sniffer can catch that.
283 comments