I get this error cloning a specific repo, while other of my repos clone with no problem:
git clone error: fatal: RPC failed; curl 52 Empty reply from server The remote end hung up unexpectedly
Any idea about a solution?
Based on the error mentioned, it seems you are experiencing issues while cloning using HTTP(S) prolocol. That said, you could:
evaluate the issue by running the following from Command Prompt / Terminal:
# Linux export GIT_TRACE_PACKET=1 export GIT_TRACE=1 export GIT_CURL_VERBOSE=1 # Windows set GIT_TRACE_PACKET=1 set GIT_TRACE=1 set GIT_CURL_VERBOSE=1 git clone <YOUR CLONE URL>
attempt on increasing the buffer size
git config http.postBuffer <SIZE>
Please, refer to the following documentartion for further information:
Rafael P. Sperafico
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs