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

Next challenges

Recent achievements

  • Global
  • Personal


  • Give kudos
  • Received
  • Given


  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

git clone failure: error: RPC failed; result=22, HTTP code = 504

I am trying to clone a repo hosted on BigBucket to my BeagleBone Black derivative, currently running git v1.7.10.4. 

I consistently get the following error:

> git clone https://<myaccount>@bitbucket,org/<myrepo.git>

> Cloning into <myrepo> ...

> Password for https://<myaccount>

error: RPC failed; result=22, HTTP code = 504
fatal: The remote end hung up unexpectedly

What would cause this error? Is this a compatibility issue with git or perhaps as the result of some configuration limitation?

3 answers

1 accepted

1 vote
Answer accepted

This was because I was still using https to access my repo, once I switched my repo to support SSH, everything was good. I am now using SSH to access my repo from my developer account (Visual Studio/Windows) and my embedded device (Linux), and I am able to clone and pull code without issues.

it's work to my problem.

Hi Even i am getting that error now could you please tel me how to switched repo to support SSH

The main thing is the remote URL. it should start with "ssh://" instead of "https://". Depending on the host, other parts of the URL might change, too.

Do you have some sort of proxy server that could be timing out?

0 votes
rrudnicki Atlassian Team Sep 22, 2015

According to the HTTP specification, 504 is returned when "The server was acting as a gateway or proxy and did not receive a timely response from the upstream server." In general, 504 is caused due to slow network. 

As workaround, try to setup your ~/.ssh/config with the following:

Host *

    ServerAliveInterval 120

To get more details about the error, set GIT_CURL_VERBOSE=1


Renato Rudnicki

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Bitbucket

Powering DevOps with Bitbucket Server & Data Center

Hi everyone, The Cloud team recently announced 12 new DevOps features that help developers ship better code, faster   ! While we’re all excited about the new improvements to Bitbucket ...

2,124 views 0 7
Read article

Community Events

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

Events near you