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

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


1 badge earned


Participate in fun challenges

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


Gift kudos to your peers

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


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!


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
Community Members
Community Events
Community Groups

Connective issues while connecting with bitbucket

HI Team,


We are seeing continues timeouts while pushing from our jenkins to bitbucket. This is causing lot of issues and blocking our releases. Please let us know the solution to overcome the same.


Fatal error: Can not push to origin:
To ssh://
45909f0..a098d4d feature-mtl -> feature-xxxxx
packet_write_wait: Connection to port 22: Broken pipe
fatal: The remote end hung up unexpectedly
fatal: The remote end hung up unexpectedly



Manikanta A

1 answer

1 accepted

Hi @Fabio Racobaldo _Herzum_ ,

I have the same issue on my laptop (Ubuntu 18.04) as well as my desktop machine. I had been committing changes to my bitbucket repo regularly from the same machines but they starting throwing this error today, and this is the first time I am facing this issue. Note, I have not altered any of my system settings.



Counting objects: 8, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (8/8), done.
Writing objects: 100% (8/8), 364.36 KiB | 3.09 MiB/s, done.
Total 8 (delta 5), reused 0 (delta 0)
packet_write_wait: Connection to port 22: Broken pipe
fatal: The remote end hung up unexpectedly
fatal: The remote end hung up unexpectedly


I tried changing the connection settings as mentioned in your previous reply but it did not solve the problem. The workarounds suggested in those posts are related to setting the SSH client changes, but I dont think this change is required especially that my laptop & desktop had been working fine with code commits all this while without those SSH config changes. It looks like some kind of server side issue.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events