• Community
  • Products
  • Bitbucket
  • Questions
  • Why, after years of pushing to my repositories, do I now get "authorization failed", and debug shows "default repository not configured"?

Why, after years of pushing to my repositories, do I now get "authorization failed", and debug shows "default repository not configured"?

In the past I've had no problem using my Bitbucket repositories, but now when I try pushing or cloning I receive the message "abort: authorization failed". When I run hg push debug, I get "abort: default repository not configured". I do have the path to the repository in my hgrc file. I'm at a loss here.

1 answer

From a fellow user (not Atlassian staff): my guess is this has something to do with the migration to Atlassian account. Do you have one? If so, have you tried logging into the BB website with it?

If not, try accessing this page.

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...

699 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