I'm setting access for another user on Bitbucket.
But still, `git clone email@example.com:workspacename/reponame.git` fails with "Connection closed by 188.8.131.52 port 22 fatal: Could not read from remote repository.".
What else can I do to diagnose this?
Hi @Sinus Pi,
I would suggest checking the following:
GIT_SSH_COMMAND="ssh -vvv" git clone firstname.lastname@example.org:workspacename/reponame.git
I applaud your multi-faceted approach. :)
In the meantime I figured out something similar - ssh was using a private key from .ssh/id_rsa, but git was trying to rely on (possibly misconfigured) ssh-agent. I didn't get to investigate in more detail, because our spare repo worked for the user attempting this and there was no point to keep trying this one.
However, the takeaway would be that it could make sense to amend your documentation, to take into consideration that even while `ssh -T email@example.com` may be working, `git clone firstname.lastname@example.org/project/repo.git` may not.
Or that's how it looked, anyway.
Hi @Sinus Pi,
Thank you for your reply and feedback.
Is the user able to clone if they add the key ~/.ssh/id_rsa to the SSH agent, with the following command?
They can also specify the private key to be used with Bitbucket in the ~/.ssh/config file, with an entry like the following:
I have attempted to reproduce the behavior you reported, but I'm afraid I haven't been able to. I'm not sure if the issue is specific to the ssh client and/or agent used, or possibly also the ssh configuration on the user's machine.
If you wouldn't mind sharing some details, like
1) operating system and version of the user
2) what SSH client is used and what version
3) whether there is any config in the ~/.ssh directory of the user, either specific to bitbucket.org or for Host *
4) The version of Git used
I can attempt to reproduce, so we can see under what circumstances the issue occurs and amend the documentation.
I experienced the same symptoms as the original poster.
I was able to track it down to the fact that my private key was named bitbucket_rsa instead of id_rsa.
I was able to use the debugging steps and solution provided by @Theodora Boudale . The solution for me was creating the Host entry in the ~/.ssh/config file with the proper IdentityFile specified.
Beginning on April 4th, we will be implementing push limits. This means that your push cannot be completed if it is over 3.5 GB. If you do attempt to complete a push that is over 3.5 GB, it will fail...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events