Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Problem with remote and app password

Hello, I'm a new bitbucket user. I have recently gotten into a game dev team.

After I cloned the repository, I attempted to fetch(in sourcetree) only to get an error along the lines of;

git -c diff.mnemonicprefix=false -c core.quotepath=false --no-optional-locks fetch --no-tags origin
remote: Bitbucket Cloud recently stopped supporting account passwords for Git authentication.
remote: See our community post for more details:
remote: App passwords are recommended for most use cases and can be created in your Personal settings:
fatal: Authentication failed for ''

Thats when I noticed there was an exclamation mark on the "remote" button which leads to my title. 

I followed some tutorials and implemented the app password, but the code error persists and the remote problem hasnt gone away. What is going on ?

I have tried to search for answers but I think my inexperience is getting in the way of me finding the right ones. Even a pointer to the right direction would be appreciated.

1 answer

0 votes
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Sep 04, 2022

Hey @Soldiernom 

Welcome to the community!

The most common issue customers are experiencing related to authentication in SourceTree is due to the local config still using an old outdated password to authenticate instead of App Password.

This generally happens on Windows Sourcetree, so I assume you are using Windows Sourcetree as well?

If yes, I would suggest you to uninstall and delete all the files/folder under the following path:

  • Navigate to C:\Users\<UserName>\AppData\Local and delete all Sourcetree folders and files (if any)
  • Navigate to C:\Users\<UserName>\AppData\Local\Atlassian and delete all Sourcetree folders and files (if any)
  • Navigate to C:\Users\<UserName>\AppData\Roaming\Atlassian __ and delete all Sourcetree folders and files (if any)

Once done, download the latest version of Sourcetree and install it. Now use the basic authentication and generate and use App Password instead your account password.

If you happen to be on MAC, you can just simply delete the store password in Keychain by searching for Bitbucket and removing all save passwords. This will force Sourcetree to reset and ask for a new password where you can enter your new App Password.

I hope this helps.


I followed your instructions to a T, but the problem persists. Could it have something to do with the automatic auth in the registration phase of installing sourcetree ?

Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Sep 05, 2022

Hey @Soldiernom 

Noted. Can you let me know what you did?

That said, can you verify that you are using the correct App Password by trying to clone your repository via HTTPS and using the app password?

git clone https://<username>:<app_password><workspace_name>/<repo_name>

Let me know how it goes.


Cloning result "fatal: destination path 'towerdefense' already exists and is not an empty directory."

I deleted all the files you told me to. I created an app password through bitbucket. Installed sourcetree again, went to options/authentication, changed auth to basic, clicked refresh password and pasted the app password in.

It says auth ok and a little green mark is there but there is no change. 

Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Sep 06, 2022

Hey @Soldiernom 


Can you try cloning the repo in an alternate folder since the error means you are trying to clone in the same directory that already has existing repo?

That said, can you check your Windows credential manager and see if there's any saved password for If yes, please remove it and try authenticating again.


Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events