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

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

Vince
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
April 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?

2 answers

1 vote
Divakar
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
July 13, 2023

The problem is with ssh keys. 

Git 2.33 and above, rsa keys are disabled by default.

You need to use ed25519. You need to generate ssh key usinng 

ssh-keygen -t ed25519

It will solve the problem

0 votes
Tom Schleyer
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
June 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.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events