cannot push, "fatal: The remote end hung up unexpectedly"

Dyno Hongjun  Fu avatarDyno Hongjun Fu created an issue

i created a repository etc.dyno to keep my system configurations, encouter error when do the initial push.

[root@cola:etc]# git push -u origin master
Password for 'bitbucket.org': 
Counting objects: 3594, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (2836/2836), done.
error: RPC failed; result=22, HTTP code = 0
fatal: The remote end hung up unexpectedly
Writing objects: 100% (3594/3594), 3.73 MiB | 612 KiB/s, done.
Total 3594 (delta 417), reused 0 (delta 0)
fatal: The remote end hung up unexpectedly

[root@cola:etc]# git --version
git version 1.7.8.3

[root@cola:etc]# git config --get remote.origin.url
https://dyno@bitbucket.org/dyno/etc.dyno.git

Comments (57)

  1. barnburnr

    I am a new user and just encountered the same error. My workaround was to do my commits using SSH instead of HTTP and everything worked fine. Hope that works for you, too.

  2. Matthias Neubert

    I have the same problem: I have to use HTTPS because of coperate firewall. even without firewall I receive:

    git push -u origin master
    Password: 
    Counting objects: 16708, done.
    Delta compression using up to 2 threads.
    Compressing objects: 100% (8074/8074), done.
    error: RPC failed; result=22, HTTP code = 0
    fatal: The remote end hung up unexpectedly
    Writing objects: 100% (16708/16708), 29.47 MiB | 1019 KiB/s, done.
    Total 16708 (delta 6604), reused 16708 (delta 6604)
    fatal: The remote end hung up unexpectedly
    fatal: expected ok/error, helper said '2004??H2????J??tHn??-?Ξ=?5???ֻ???<??Fҭ}z??G?!L??cb????~?^?l3c=y??`?ML?????'
    

    I use macos x 10.7.3 with git 1.7.8.4

    any ideas?

  3. Dylan Etkin
    • changed status to invalid
    • removed assignee

    Hey All,

    Can you please open up a support request by emailing support@bitbucket.org?

    There may be a common cause to your problems but I think it will be easier to look into them individually.

    Sorry for the run-around.

    Cheers,

    Dylan

  4. TripleS

    Had a similiar issue. It seems like the commit size was too big (default is < 1Mbyte). Resolved it with rising the limit up to 500Mbytes:

    git config --global http.postBuffer 524288000

  5. fredrischter

    not resolved... its happenning when i try to push any commits. already tryed the solution upthere..

    D:\workspace\rgl4>git push origin div2 Counting objects: 153, done. Delta compression using up to 2 threads. Compressing objects: 100% (99/99), done. error: RPC failed; result=55, HTTP code = 0 53 KiB/s fatal: The remote end hung up unexpectedly Writing objects: 100% (120/120), 71.19 MiB | 65 KiB/s, done. Total 120 (delta 33), reused 99 (delta 14) fatal: The remote end hung up unexpectedly Everything up-to-date

  6. Vincent Nonnenmacher

    Same here, even when etting a bigger http chunck size for the post, if the size of the commit (and an initial commit could be large), the error :

    error: RPC failed; result=55, HTTP code = 0iB | 6.75 MiB/s fatal: The remote end hung up unexpectedlyMiB | 468 KiB/s

    came after the RPC chunk is uploaded, so I guess the error is the fact that if the whole commit could not bu uploaded in one chunck, we got the error at the end of this first transaction.

    Hope that the ssh way, is well documented ;-)

  7. Marcus Bertrand

    All,

    If you are experiencing this issue, please open a support request via email directly to support@bitbucket.org. We need more information to be able to troubleshoot and reproduce this issue.

    In the mean time, using SSH may get you going. We have a VERY thorough guide at:

    If you have trouble setting it up, check out https://confluence.atlassian.com/display/BITBUCKET/Troubleshooting+SSH+Issues.

    Any other issues you run into setting up SSH, please raise a support request or add the error to any existing support issues you may have open.

  8. Vincent Nonnenmacher

    got it to work using ssh

    and FYI it is very easy to reproduce, take any initial working dir around 100-200MB and try to make the initial commit using HTTPS and you'll get the same problem.

    I recommend the ssh way, its easier and faster.

  9. Marcus Bertrand

    Unfortunately, we've tried with repos of varies sizes up to 1GB and cannot reproduce. If you email support, please also let us know where you are geographically. Perhaps we have an issue that can only be reproduced under certain conditions.

  10. Vincent Nonnenmacher

    Oh I thought it was a much more reproducible bug. I had strictly no problems with smaller repos, that why I deduced it’s was an http post size to RPC problem.

    I'm connecting from Grenoble (France)

    I could mail to support a trace route to help if needed

  11. Teemo Tebest

    Hi,

    I'm also experiencing this issue:

    Counting objects: 168, done.
    Delta compression using up to 4 threads.
    Compressing objects: 100% (162/162), done.
    Writing objects: 100% (165/165), 130.00 MiB | 11.52 MiB/s, done.
    Total 165 (delta 64), reused 0 (delta 0)
    error: RPC failed; result=55, HTTP code = 0
    fatal: The remote end hung up unexpectedly
    fatal: The remote end hung up unexpectedly
    

    I'm from Finland. I'm using Mac OS X 10.7.4.

    []$ git --version git version 1.7.5.4

    Here is a traceroute to bitbucket.org

    []$ traceroute bitbucket.org
    traceroute: Warning: bitbucket.org has multiple addresses; using 207.223.240.181
    traceroute to bitbucket.org (207.223.240.181), 64 hops max, 52 byte packets
     1  10.0.0.2 (10.0.0.2)  1.520 ms  1.521 ms  1.503 ms
     2  helpa1.fi.elisa.net (88.112.32.1)  36.372 ms  103.136 ms  157.051 ms
     3  139.97.67.41 (139.97.67.41)  181.475 ms  639.911 ms  652.088 ms
     4  ae2.helpa-gw1.fi.elisa.net (139.97.6.250)  658.277 ms  677.936 ms  649.839 ms
     5  ae1-10.bbr1.hel2.fi.eunetip.net (213.192.191.53)  710.709 ms  645.948 ms  655.488 ms
     6  so7-0-0-0.bbr1.sto1.se.eunetip.net (213.192.191.210)  676.551 ms  589.216 ms  20.458 ms
     7  213.242.110.169 (213.242.110.169)  20.166 ms  19.921 ms  67.491 ms
     8  * ae-2-7.bar1.copenhagen2.level3.net (4.69.140.202)  34.475 ms *
     9  ae-0-10.bar1.copenhagen1.level3.net (4.69.137.153)  34.731 ms  29.601 ms  29.749 ms
    10  ae-7-7.ebr1.dusseldorf1.level3.net (4.69.142.170)  40.607 ms  41.325 ms  41.160 ms
    11  ae-22-22.ebr2.dusseldorf1.level3.net (4.69.143.186)  41.083 ms
        ae-21-21.ebr2.dusseldorf1.level3.net (4.69.143.182)  41.940 ms
        ae-22-22.ebr2.dusseldorf1.level3.net (4.69.143.186)  41.089 ms
    12  ae-46-46.ebr1.amsterdam1.level3.net (4.69.143.201)  44.665 ms
        ae-45-45.ebr1.amsterdam1.level3.net (4.69.143.197)  44.419 ms
        ae-48-48.ebr1.amsterdam1.level3.net (4.69.143.209)  44.182 ms
    13  ae-1-100.ebr2.amsterdam1.level3.net (4.69.141.170)  45.328 ms  44.200 ms  44.489 ms
    14  ae-46-46.ebr2.london1.level3.net (4.69.143.74)  51.697 ms
        ae-48-48.ebr2.london1.level3.net (4.69.143.82)  67.265 ms  51.669 ms
    15  ae-44-44.ebr1.newyork1.level3.net (4.69.137.78)  120.681 ms  120.464 ms
        ae-41-41.ebr1.newyork1.level3.net (4.69.137.66)  120.798 ms
    16  ae-4-4.ebr1.newyork2.level3.net (4.69.141.18)  121.622 ms  121.148 ms  122.179 ms
    17  ae-1-100.ebr2.newyork2.level3.net (4.69.135.254)  121.217 ms  120.228 ms  120.703 ms
    18  ae-2-2.ebr1.chicago1.level3.net (4.69.132.65)  140.680 ms  141.362 ms  144.856 ms
    19  ae-1-100.ebr2.chicago1.level3.net (4.69.151.178)  140.753 ms  141.177 ms  141.036 ms
    20  ae-4-4.car2.stlouis1.level3.net (4.69.132.189)  146.766 ms  153.985 ms  160.933 ms
    21  ae-11-11.car1.stlouis1.level3.net (4.69.132.185)  145.728 ms  150.582 ms  146.454 ms
    22  wichita-pub.car1.stlouis1.level3.net (4.53.160.186)  146.019 ms  146.058 ms  146.646 ms
    23  b1-e21.c1-f00.stl1.rackmy.com (63.246.15.2)  146.713 ms  148.511 ms  146.411 ms
    24  * * *
    25  * * *
    26  * * *
    27  * * *
    28  * * *
    ....
    
  12. Marcus Bertrand

    To give everyone an update, we are working on this, but are having a time finding the culprit. Please continue to use SSH as a workaround for the time being. Also, please continue to provide any information possible you can here or privately via support@bitbucket.org.

  13. Dylan Etkin

    Hey All,

    We believe we have solved this issue.

    The problem was with our SSL terminator. We were using STUD which seems to have been causing this problem but only under significant load. We have switched to using nginx for SSL termination and have not been able to reproduce the issue with our test rig. We have also not had any reports of this in the time our change has been deployed.

    Please let us know if you are still seeing the problem and thanks for being patient while we sorted it out.

    Cheers,

    The Bitbucket Team

  14. Frank Mattes

    Thank you very much, this was my issue, too. Sizeing up the postBuffer in my local repo did the trick.

    You guys really helped me out of this mess.

  15. nicorama

    Unfortunately, I still have the same problem. On Ubuntu 12.10, it works using the cli, but not with idea. I have the trace : 22:47:25.015: git push origin master:master java.io.IOException: Authentication failed: at org.jetbrains.git4idea.ssh.SSHMain.authenticate(SSHMain.java:282) at org.jetbrains.git4idea.ssh.SSHMain.start(SSHMain.java:156) at org.jetbrains.git4idea.ssh.SSHMain.main(SSHMain.java:136) fatal: The remote end hung up unexpectedly

    What could be : "master:master" ? Looks more like an idea (or user) problem ?

  16. Ricardo1980

    I have that problem with 2 repos I created. Can't upload the first commit. Tried changing the commit size with global and doesn't work. I still have to try SSH.

  17. balabanmario

    I'm experiencing the problem when pushing from a Windows Machine that is installed as guest on a Mac 10.7.5 host (virtualbox). The network adapter is NATed. I was able to checkout the project via https but when pushing the modifications it says:

    $ git push origin master
    Password for 'https://balabanmario@bitbucket.org':
    Counting objects: 32, done.
    Compressing objects: 100% (23/23), done.
    Writing objects: 100% (27/27), 16.76 KiB, done.
    Total 27 (delta 6), reused 0 (delta 0)
    error: RPC failed; result=52, HTTP code = 0
    fatal: The remote end hung up unexpectedly
    fatal: recursion detected in die handler
    Everything up-to-date
    
  18. Anonymous

    I was experiencing this issue in pushing to BitBucket with Git Bash behind a corporate Windows proxy. I have to work on a Windows 7 64 bits workstation. The corporate proxy also blocks SSH traffic. The solution for me is to use a NTLM proxy running in my workstation to intermediate the communication between Git Bash and the corporate proxy. At first I tryed CNTLM (http://cntlm.sourceforge.net/), but I was unable to run it due to adm rights. Now I'm successfully using Java NTLM Proxy (http://java-ntlm-proxy.sourceforge.net/). Hope this help others.

  19. Abhinav Rastogi

    I was experiencing this issue in pushing to BitBucket with Git Bash. I work on a Windows 7 32 bits workstation. I am pushing a directory of size 3 MiB. I had already increased the buffer size from 1MiB to 200 MiB Following is what i get during pushing to bitbucket. Help me guys.

    Agicent@AGICENT-PC ~/sample/xxx (master)
    $ git push -u origin master
    Password for 'https://abhinav19@bitbucket.org':
    Counting objects: 181, done.
    Delta compression using up to 2 threads.
    Compressing objects: 100% (166/166), done.
    Writing objects: 100% (181/181), 1.64 MiB | 0 bytes/s, done.
    Total 181 (delta 35), reused 0 (delta 0)
    error: RPC failed; result=56, HTTP code = 0
    fatal: The remote end hung up unexpectedly
    fatal: The remote end hung up unexpectedly
    Everything up-to-date
    
  20. Brian Nguyen

    Hi,

    If you are experiencing issues pushing, could you contact us at support@bitbucket.org. We can help you without having to spam everyone on this issue. Most of these issues are very specific to the computer/user.

    Cheers, Brian

  21. Log in to comment
Tip: Filter by directory path e.g. /media app.js to search for public/media/app.js.
Tip: Use camelCasing e.g. ProjME to search for ProjectModifiedEvent.java.
Tip: Filter by extension type e.g. /repo .js to search for all .js files in the /repo directory.
Tip: Separate your search with spaces e.g. /ssh pom.xml to search for src/ssh/pom.xml.
Tip: Use ↑ and ↓ arrow keys to navigate and return to view the file.
Tip: You can also navigate files with Ctrl+j (next) and Ctrl+k (previous) and view the file with Ctrl+o.
Tip: You can also navigate files with Alt+j (next) and Alt+k (previous) and view the file with Alt+o.