git clone error: fatal: RPC failed; curl 52 Empty reply from server The remote end hung up unexpectedly

John Wygonski November 19, 2016

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?

2 answers

1 vote
Michael Heemskerk
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
November 20, 2016

There might be more information in the server logs. I'd suggest opening a support request on https://support.atlassian.com and uploading support zip so our support engineers can scan for errors in the logs. 

0 votes
rsperafico
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
November 21, 2016

Hello John,

Based on the error mentioned, it seems you are experiencing issues while cloning using HTTP(S) prolocol. That said, you could:

  1. 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>
  2. attempt on increasing the buffer size

    git config http.postBuffer <SIZE>

    Please, refer to the following documentartion for further information:
    https://confluence.atlassian.com/bitbucketserverkb/git-push-fails-fatal-the-remote-end-hung-up-unexpectedly-779171796.html
    https://confluence.atlassian.com/bitbucketserverkb/error-rpc-failed-result-22-push-to-bitbucket-server-fails-779171801.html

  3. clone using SSH instead
  4. raise a support request as already suggested in this thread

Kind regards,
Rafael P. Sperafico

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events