Create
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Products
See all
Community resources
Interests
See all
Community resources
Top groups
Explore all groups
Community resources
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

Join now to unlock these features and more

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.

Get started Tell me more
Atlassian Community about banner
4,456,841
Community Members
 
Community Events
176
Community Groups

Upgraded from git 2.33 to 2.36 and now can't access repos

Edited
Vince
Vince Apr 28, 2022

I upgraded from git 2.33 to 2.36.0.windows.1 today, and suddenly I'm unable to clone or pull from BitBucket. I get the following error:

git@"domain": Permission denied (publickey).

fatal: Could not read from remote repository.

Please make sure you have the correct access rights

and the repository exists

 

I have found several solutions online (including these forums) and no luck so far. I've recreated SSH keys, made sure they are in my ssh-add/uploaded to BitBucket, etc. Still, no luck. It worked fine immediately before I did the git upgrade.

Has anyone experienced this with the upgrade to 2.36 or have other suggestions on how to get this to work?

Answer
Watch
Like Be the first to like this
252 views

1 answer

0 votes
Tom Schleyer
Tom Schleyer Jun 23, 2022

I have experienced this after upgrading to Git 2.36.0 and using Bitbucket 7.17.1.  I was not able to resolve the issue but, upgrading Bitbucket to 7.21.2 fixed it.

Reply

Suggest an answer

Log in or Sign up to answer
Bitbucket
Bitbucket
TAGS

Atlassian Community Events

See all events