SSH cannot connect to bitbucket

christie_vas
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 29, 2023

Hello, I followed all steps from https://support.atlassian.com/bitbucket-cloud/docs/set-up-personal-ssh-keys-on-windows/ to set up the keys, I believe successfully. However, at the very last step I get the message

$ ssh -T git@bitbucket.org
authenticated via ssh key.

You can use git to connect to Bitbucket. Shell access is disabled

after maybe three or four minutes. And when I try to git fetch in my cloned repo, it does not seem to return anything.

Any help would be very much appreciated! (I should say I have been using git - without being an expert - for a number of years, but I did not work on the specific bitbucket repo for maybe a year).

1 answer

0 votes
Patrik S
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
June 30, 2023

Hello @christie_vas and welcome to the community!

The git fetch command will return no output when your local repository is up to date with the remote. If the command is completed with no errors and no output, it likely means that it was able to successfully connect to Bitbucket and verify the local branch already contains all the changes from the remote repository

You can try to use git pull instead, which will output the message "Already up to date" if the repository is in sync with the remote.

Another option, if you want to test that the SSH key was setup correctly, is to clone the repository again to a different folder : 

git clone git@bitbucket.org:WORKSPACE/REPOSITORY.git

Hope that helps! Let me know in case you run into any issues.

Thank you, @christie_vas !

Patrik S

christie_vas
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 2, 2023

Thanks a lot Patrik. My phrasing was wrong, I did not mean "it does not return anything" as in it gives me back the command line or an "already up to date" notification, I meant it does not give anything, as in the process does not finish.

This morning this was fixed, I suspect it was because I added the newest key to the known-host file. Many thanks!

Like Patrik S likes this

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events