1. Bitbucket Website
  2. Public Issue Tracker
  3. master

Issues

Issue #7567 invalid

git push remote end hung up

AppEatite
created an issue

The results of the above command you posted is the following MacBook-Pro:Mainrepo.git username$ git push -u origin --all --verbose Pushing to ssh://git@bitbucket.org/NAMEOFGIT.git Counting objects: 600, done. Delta compression using up to 8 threads. Compressing objects: 100% (567/567), done. Received disconnect from 207.223.240.181: 2: Packet corrupt fatal: The remote end hung up unexpectedly error: pack-objects died of signal 13 error: failed to push some refs to 'ssh://git@bitbucket.org/NAMEOFGIT.git'

I tried starting from a fresh repo and pushing changes and was unsuccessful there too. Following are the results user-64-9-235-121:.git username$ git push -u origin master Counting objects: 865, done. Delta compression using up to 8 threads. Compressing objects: 100% (856/856), done. Received disconnect from 207.223.240.182: 2: Packet corrupt fatal: The remote end hung up unexpectedly error: pack-objects died of signal 13 error: failed to push some refs to 'ssh://git@bitbucket.org/NameOfREpo.git'

This was on Mac OS X 10.8 using iTerm2 , if that makes any difference.

Comments (16)

  1. Travis Bennett

    I'm getting this issue now too. This is happening to a new repo that I just created. My repo is only 11MB. Don't know what's going on.

    count: 1064 size: 11.25 MiB in-pack: 0 packs: 0 size-pack: 0 bytes prune-packable: 0 garbage: 0 size-garbage: 0 bytes

  2. Aqeel Aslam

    I got the same issue today. While searching for a solution, i came across this where a principle engineer from Atlassian asked for details to be reported to Bitbucket support, so I did.

    Waiting for their response now.

  3. Aqeel Aslam

    I received a response from support asking me if I was behind a firewall or proxy which I wasn't. But just as a hint from their query, I thought to change my ISP ( Internet Service Provider) and give it a try, and it worked. Strange but just posting here if it helps anyone else.

  4. David Peck

    Same here. I'm using SSH in case that matters.

    Received disconnect from 104.192.143.1: 2: Packet corrupt

    fatal: sha1 file '<stdout>' write error: Invalid argument

    fatal: The remote end hung up unexpectedly

  5. Patrick Chin

    Got a similar error: Counting objects: 9, done.
    Delta compression using up to 8 threads.
    Compressing objects: 100% (9/9), done.
    Writing objects: 100% (9/9), 2.81 MiB | 4.35 MiB/s, done.
    Total 9 (delta 4), reused 0 (delta 0)
    Received disconnect from 104.192.143.2: 2: Packet corrupt
    fatal: The remote end hung up unexpectedly
    fatal: The remote end hung up unexpectedly

  6. uoroaix

    I am using SSH too. Just happened to me today.... no idea why I can't push now Counting objects: 55, done. Delta compression using up to 4 threads. Compressing objects: 100% (48/48), done. Received disconnect from 104.192.143.1: 2: Packet corrupt fatal: The remote end hung up unexpectedly error: pack-objects died of signal 13 error: failed to push some refs to 'git@bitbucket.org:dotvici/tranuggle.git'

  7. rutaihwa

    I forgot to update, Daz Bradbury I dea worked for me, only that I had to change and push via https instead of ssh. I changed that in the .git/config and once finished changed back to ssh and it worked like a charm.

  8. Duncan Mortimer

    I'm also having this problem. As with Aqeel Aslam, when trying to push via ssh I get:

    Counting objects: 88, done.
    Delta compression using up to 4 threads.
    Compressing objects: 100% (88/88), done.
    Writing objects: 100% (88/88), 2.02 MiB | 0 bytes/s, done.
    Total 88 (delta 63), reused 0 (delta 0)
    Received disconnect from 104.192.143.3: 2: Packet corrupt
    Disconnected from 104.192.143.3
    fatal: The remote end hung up unexpectedly
    fatal: The remote end hung up unexpectedly
    

    Trying to push via https gives:

    Counting objects: 88, done.
    Delta compression using up to 4 threads.
    Compressing objects: 100% (88/88), done.
    Writing objects: 100% (88/88), 2.02 MiB | 0 bytes/s, done.
    Total 88 (delta 63), 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
    

    Have tried increasing http.postBuffer.

  9. Brian Ramsey

    I am having the same difficulty, being new to Git I am thinking I am doing something wrong but I do not know what I possibly could be doing wrong, my webapp works fine, no corrupt files and keep getting this:

    Counting objects: 1855, done.
    Delta compression using up to 16 threads.
    Compressing objects: 100% (1500/1500), done.
    Received disconnect from 104.192.143.2: 2: Packet corrupt
    Disconnected from 104.192.143.2
    Wrfatal: The remote end hung up unexpectedly
    fatal: sha1 file '<stdout>' write error: Broken pipeKiB/s
    error: failed to push some refs to '(repo)'
    

    same kind of issue with LESS information, when trying to push HTTPS

  10. boussouira

    Same issue here, i had to use SSH Tunneling to push the first time to this new project, on other projects pushing works without any proxy. Also github and heroku works without issue too.

    % proxychains git push -u origin master  
    ProxyChains-3.1 (http://proxychains.sf.net)
    |DNS-request| bitbucket.org 
    |S-chain|-<>-127.0.0.1:1080-<><>-4.2.2.2:53-<><>-OK
    |DNS-response| bitbucket.org is 104.192.143.3
    |S-chain|-<>-127.0.0.1:1080-<><>-104.192.143.3:22-<><>-OK
    Counting objects: 3388, done.
    Delta compression using up to 2 threads.
    Compressing objects: 100% (1089/1089), done.
    Writing objects: 100% (3388/3388), 2.79 MiB | 85.00 KiB/s, done.
    Total 3388 (delta 2312), reused 3343 (delta 2281)
    To git@bitbucket.org:username/web-app.git
     * [new branch]      master -> master
    Branch master set up to track remote branch master from origin.
    
  11. Tom Clarke

    Also experiencing this issue. Using SSH. 153 Objects, 8.06 MiB.

    Received disconnect from 104.192.143.3: 2: Packet corrupt 
    fatal: The remote end hung up unexpectedly
    error: pack-objects died of signal 13
    error: failed to push some refs to '<repo>.git'
    

    Strange thing is, I've managed to push the master branch (only one commit) but when I try to push develop I get this error.

  12. Log in to comment