Bug: cloning via HTTPS broken after Atlassian account transition

Cloning with HTTPS is broken after the Atlassian account migration.

The clone path is "git clone https://veksler@bitbucket.org/feeorg/fee-cms.git"

"veksler" is my Bitbucket username.  This username does not work after migrating my Bitbucket account to my Atlassian account.  When I clone with SourceTree I get a credential error, and the username is read only, so I can't use my Atlassian credentials.

The workaround is to remove the username from the clone path in the Repository Settings.  This is annoying because I have more than 10 repositories in my SourceTree.  However SourceTree is still asking me for the old Bitbucket account - it must have the old credentials hidden somewhere.


1 answer

0 votes

Hi David

You should be able to authenticate using your Bitbucket username and your Atlassian account password. Does that work?


Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 06, 2018 in Bitbucket

Upgrade Best Practices

Hello! My name is Mark Askew and I am a Premier Support Engineer for products Bitbucket Server/Data Center, Fisheye & Crucible. Today, I want to bring the discussion that Jennifer, Matt, and ...

434 views 6 9
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you