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 Join to answer
Community showcase
Piotr Plewa
Published Dec 27, 2017 in Bitbucket

Recipe: Deploying AWS Lambda functions with Bitbucket Pipelines

Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda&nbsp...

673 views 0 4
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
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot