ssh stopped working

I've been using Bitbucket with TortoiseHg (Windows 8) with SSH authorization for the last four years with no issues, but suddenly on a push attempt I got the dreaded "abort: authorization failed". When I went to log in I noticed that I could no longer use my username but had to use my "registered email". I really don't want to have to muck about with SSH keys if I don;t have to, is there an easy way to get SSH to work with the existing keys?

1 answer

Never mind, this was due to the recent Atlassian-wide user name change AND password change in combination with TortoiseHg. When I first looked at the TortoiseHg settings file (from the workbench select "File/Settings", then click the "{user}'s global settings" tab, then click the "Edit File" button) I noticed the first "username" field under the "[ui]" section and changed that to no avail. But when I looked more thoroughly I found the "[auth]" section below it that had "bitbucket.org.username" and "bitbucket.org.password" fields and set those to my credentials and it worked.

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

636 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