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,465,382
Community Members
 
Community Events
176
Community Groups

What does error "Result=52 The remote end hung up unexpectedly" after Git Pull mean?

Hello everybody,
I'm attempting to pull code from a bitbucket repo.
When running a simple git pull command, I'm prompted for my BitBucket credentials
After entering my credentials I run into this error:

"Error: RPC failed; result=52, HTTP code = 0
fatal: The remote end hung up unexpectedly"


I'm certain the remote origin URL correctly points to my bitbucket repo.
I'm also certain my bitbucket credentials are correct.

From what I've seen in other forums, one accepted answer suggested this error stems from internal bitbucket server errors. Could that be?
Has anyone here run into this error before? 
Any advice or suggestion is greatly appreciated! Thanks in advance!

1 answer

0 votes

Welcome to the Atlassian Community!

I'm afraid your other forums are probably wrong.  This error is usually caused by hosting large files in git, ones that are too big for the buffer.  You can also get it if the remote git repository is slow (often down to network slowness) and can't deliver the file in time.

Try increasing the size of the git buffer -

git config http.postBuffer 520000000

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events