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,463,394
Community Members
 
Community Events
176
Community Groups

OAuth authentication fails for my Bitbucket Account in Sourcetree.

Edited

Hello,

I have an issue with Sourcetree for Windows 3.3.8. I successfully uninstalled and reinstalled Sourcetree on my machine, which is running Windows 10 Pro. The issue I am experiencing is related to creating my account. I have imported my SSH key and my user account information is correctly listed in [Tools]_[Options]_[General]. When I attempt to add my account under the [Authentication] tab, I attempt to refresh my OAuth token, but the path is not valid. This URL appears in Firefox when I attempt to refresh my OAuth token:

http://localhost:34106/?state=authenticated&code={redacted}

A connection was not able to be established at the local host. This occurs regardless of whether I use HTTPS or SSH. Please help. I am not able to use any of my repos until I get this fixed properly. Thanks.

A bit more info:

I ran netstat -anop tcp to get a list of all TCP ports and their states.

 

TCP 0.0.0.0:34106 0.0.0.0:0 LISTENING 4

 

I don't see port 34106/tcp listening on 127.0.0.1 though.

 

 

 

1 answer

A bit more info:

I ran netstat -anop tcp to get a list of all TCP ports and their states.

 

TCP 0.0.0.0:34106 0.0.0.0:0 LISTENING 4

 

I don't see port 34106/tcp listening on 127.0.0.1 though.

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events