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

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

Avatar

1 badge earned

Collect

Participate in fun challenges

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

Challenges
Coins

Gift kudos to your peers

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

Recognition
Ribbon

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!

Leaderboard

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
4,457,953
Community Members
 
Community Events
176
Community Groups

Error 403 when using second account in SourceTree

Long time Sourcetree user, but only ever with a single account. I was attempting to setup a second account with a work email address and test out the Google Rooms Atlas bot, but scratch that... The Sourcetree app would not allow me to access my newly setup demo Repo on my newly setup second account. The first account (my private hobby account) still worked fine as expected, but SourceTree failed to authenticate when a second account was tied to it. And I couldn't exactly demo my remake of Atari's classic Asteroids to my work mates... Well, I mean I could... but then they'd start to wonder what they're actually paying me for... ehem.

Anyway, I have no idea how to troubleshoot this, it's frustrating as heck and I'm close to giving up. Even tried a clean uninstall of Sourcetree, but no go.

For the record, error reads (replace hashes with my other account);

Command: git -c diff.mnemonicprefix=false -c core.quotepath=false --no-optional-locks ls-remote https://##########@bitbucket.org/########/example.git
Output:
Error: remote: You'll need to authenticate with a valid app password. You can create an app password from your account at https://bitbucket.org/account/admin/app-passwords
fatal: unable to access 'https://bitbucket.org/########/example.git/': The requested URL returned error: 403

I cross checked both the OAuth in my old and new accounts, they look as expected? And the Sourcetree has the OAuth green light on both accounts... I'm at a loss. I don't understand why Source tree and authentication has been setup to be so confusing. Surely it's not unusual for users to have two different bitbucket accounts, one for work, one for play? Or two or more for different clients? ... I'll stop my whinging, hopefully someone can help.

0 answers

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events