Issue #8774 resolved

error: RPC failed; result=35, HTTP code = 0

Egidio Caprino
created an issue

Hello. I get this error while trying to push the commit.

Egidio

warning: push.default is unset; its implicit value is changing in
Git 2.0 from 'matching' to 'simple'. To squelch this message
and maintain the current behavior after the default changes, use:

  git config --global push.default matching

To squelch this message and adopt the new behavior now, use:

  git config --global push.default simple

See 'git help config' and search for 'push.default' for further information.
(the 'simple' mode was introduced in Git 1.7.11. Use the similar mode
'current' instead of 'simple' if you sometimes use older versions of Git)

Password for 'https://Aegidius@bitbucket.org': 
Counting objects: 21, done.
Delta compression using up to 8 threads.
Compressing objects: 100% (10/10), done.
Writing objects: 100% (11/11), 4.42 KiB | 0 bytes/s, done.
Total 11 (delta 4), reused 0 (delta 0)
error: RPC failed; result=35, HTTP code = 0
fatal: The remote end hung up unexpectedly
fatal: The remote end hung up unexpectedly
Everything up-to-date

Comments (17)

  1. Paul Barker

    I'm getting the same issue when cloning a repository over https. There's no issue cloning over http. I've only seen this for one repository so far, all my others are working fine.

    $ git clone https://bitbucket.org/underwater-acoustics/meta-udaq.git
    Cloning into 'meta-udaq'...
    error: RPC failed; result=35, HTTP code = 0
    fatal: The remote end hung up unexpectedly
    
  2. Sidhant Panda

    Getting the same problem

    $ git push -u origin master
    Password for 'https://ABC@bitbucket.org': 
    Counting objects: 1283, done.
    Delta compression using up to 8 threads.
    Compressing objects: 100% (1112/1112), done.
    error: RPC failed; result=35, HTTP code = 0
    fatal: The remote end hung up unexpectedly
    Writing objects: 100% (1282/1282), 1.57 MiB | 670.00 KiB/s, done.
    Total 1282 (delta 398), reused 0 (delta 0)
    fatal: The remote end hung up unexpectedly
    Everything up-to-date
    
  3. Jason Erickson

    I also have been getting this for the past several days intermittently. Usually, when I just try it again, it works, so I'm not stuck - just thought I would chime in to see that I've been seeing that error message, too.

  4. Egidio Caprino reporter

    Not working.

    [egidio@egidio 1-dollar-jackpot]$ GIT_CURLOPT_SSLVERSION=3 git push
    warning: push.default is unset; its implicit value is changing in
    Git 2.0 from 'matching' to 'simple'. To squelch this message
    and maintain the current behavior after the default changes, use:
    
      git config --global push.default matching
    
    To squelch this message and adopt the new behavior now, use:
    
      git config --global push.default simple
    
    See 'git help config' and search for 'push.default' for further information.
    (the 'simple' mode was introduced in Git 1.7.11. Use the similar mode
    'current' instead of 'simple' if you sometimes use older versions of Git)
    
    Password for 'https://Aegidius@bitbucket.org': 
    Counting objects: 21, done.
    Delta compression using up to 8 threads.
    Compressing objects: 100% (10/10), done.
    Writing objects: 100% (11/11), 4.42 KiB | 0 bytes/s, done.
    Total 11 (delta 4), reused 0 (delta 0)
    error: RPC failed; result=35, HTTP code = 0
    fatal: The remote end hung up unexpectedly
    fatal: The remote end hung up unexpectedly
    Everything up-to-date
    [egidio@egidio 1-dollar-jackpot]$ 
    
  5. Paul Barker

    So we know this is common but intermittant, any official reply from Bitbucket? Is anyone else having this problem when cloning/pulling or are you all just seeing it when pushing?

    The issue for me is automated systems like Ohloh which pull my code. I can't trigger a retry without involving their tech support and I can't control the environment variables or config options used.

  6. Log in to comment