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

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,552,946
Community Members
 
Community Events
184
Community Groups

error: RPC failed; HTTP 504 curl 22 The requested URL returned error: 504

Total 20806 (delta 14193), reused 20805 (delta 14193), pack-reused 0

error: RPC failed; HTTP 504 curl 22 The requested URL returned error: 504

fatal: the remote end hung up unexpectedly

fatal: the remote end hung up unexpectedly

Everything up-to-date

 

## steps taken to resolve ##

edit bitbucket.properties file in the server to add 

plugin.ssh.command.timeout.idle=86400
plugin.stash-scm-git.backend.timeout.idle=1800
plugin.stash-scm-git.backend.timeout.execution=86400

 

added ~/.gitconfig

[http]

        postBuffer = 10000000000

        maxRequestBuffer = 500M

        lowSpeedLimit = 0

        lowSpeedTime = 999999

 

Seems able to push to bitbucket but still receiving error

error: RPC failed; HTTP 504 curl 22 The requested URL returned error: 504

fatal: the remote end hung up unexpectedly

fatal: the remote end hung up unexpectedly

 

1 comment

Edward
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Jun 22, 2022

Hi Amrit,

The 504 error means:

The HyperText Transfer Protocol (HTTP) 504 Gateway Timeout server error response code indicates that the server, while acting as a gateway or proxy, did not get a response in time from the upstream server that it needed in order to complete the request

You will need to possibly increase timeouts on the proxy, CloudFront, or use ssh. For example proxy configurations we recommend, please see:

Thanks!

Comment

Log in or Sign up to comment
TAGS
AUG Leaders

Atlassian Community Events