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,464,074
Community Members
 
Community Events
176
Community Groups

All users unable to git clone or push. Fails with "fatal: Authentication failed for"

Just recently started running into this issue on our local Bitbucket server instance. None of our users are able to clone/pull from any of our repositories. It pops up an Atlassian authentication dialog which does not authenticate the user correctly resulting in a "fatal: Authentication failed for" error. Following the "Can't log in?" button on this login screen directs us to the Bitbucket cloud login, which makes no sense as this is our own Bitbucket server instance. 

Neither SSH or HTTPS works. Not in Visual Studio, Sourcetree or git console either. The only way we have somehow been able to clone any repository is via Github's import repository option, which was successful in importing our repository.

All the users are able to successfully log into bitbucket via the web interface. They are able to create branches, commit code and create pull requests from here. 

 

Any assistance with solving this issue would be greatly appreciated. 

 

1 answer

0 votes

I am having this exact error, was this ever resolved?

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events