I have an interesting problem. I have a project for pets on a bit bag, and so far I have managed to get it out of two different networks (home and office). It took some time to properly configure the configuration, but I figured it out with some attempts and errors. Now the problem is that I created a branch in the office (which is located behind the proxy server), and I can’t click on the bitpack with the -all parameter. I get:
RPC error; result = 22, HTTP code = 0
Here is git bash (changed):
user@machine /c/dev/data/personal/projectname (master) $ git push --all --dry-run Password for 'https:// username@bitbucket.org ': To https:// username@bitbucket.org /username/projectname * [new branch] ivymigration -> ivymigration user@machine /c/dev/data/personal/projectname (master) $ git push --all Password for 'https:// username@bitbucket.org ': Counting objects: 194, done. Delta compression using up to 4 threads. Compressing objects: 100% (112/112), done. Writing objects: 100% (116/116), 58.37 KiB, done. Total 116 (delta 81), reused 0 (delta 0) efrror: RPC failed; result=22, HTTP code = 0 atal: The remote end hung up unexpectedly fatal: The remote end hung up unexpectedly Everything up-to-date user@machine /c/dev/data/personal/projectname (master) $ git config --global -l http.proxy=http://user: password@proxy :8080 http.postbuffer=524288000 user.name=[My Name] user.email=[my_name]@[my.domain] core.autocrlf=true push.default=upstream
I tried things from RPC failed; result = 28, HTTP code = 0 but to no avail. Changing https to git or git + ssh does not work either because of the proxy server. Interestingly, the click has so far ceased without the -all attribute. But as soon as I want to push everything, including a new branch, all this will collapse.
Any thoughts?
Update # 1:
I tried to push the branch following the instructions in the https://confluence.atlassian.com/display/BITBUCKET/Branching+a+Repository section "How to join git" without success. Here is git bash:
user@machine /c/dev/data/personal/projectname (master) $ git push origin ivymigration Password for 'https:// username@bitbucket.org ': Counting objects: 203, done. Delta compression using up to 4 threads. Compressing objects: 100% (72/72), done. Writing objects: 100% (125/125), 70.79 KiB, done. Total 125 (delta 86), reused 88 (delta 49) efrror: RPC failed; result=22, HTTP code = 0 atal: The remote end hung up unexpectedly fatal: The remote end hung up unexpectedly Everything up-to-date
As you can see, I get the same error.
Update # 2:
I tried what Seth suggested, and here is the result:
user@machine /c/dev/data/personal/projectname (ivymigration) $ GIT_TRACE=1 git push --all trace: built-in: git 'push' '--all' trace: run_command: 'git-remote-https' 'origin' 'https:// username@bitbucket.org /username/projectname' Password for 'https:// username@bitbucket.org ': trace: run_command: 'send-pack' '--stateless-rpc' '--helper-status' '--thin' '--progress' 'https:// username@bitbucket.org /username/projectname/' 'refs/heads/ivymigration:refs/heads/ivymigration' trace: built-in: git 'send-pack' '--stateless-rpc' '--helper-status' '--thin' '--progress' 'https:// username@bitbucket.org /username/projectname/' 'refs/heads/ivymigration:refs/heads/ivymigration' trace: run_command: 'pack-objects' '--all-progress-implied' '--revs' '--stdout' '--thin' '--delta-base-offset' '--progress' trace: built-in: git 'pack-objects' '--all-progress-implied' '--revs' '--stdout' '--thin' '--delta-base-offset' '--progress' Counting objects: 203, done. Delta compression using up to 4 threads. Compressing objects: 100% (72/72), done. Writing objects: 100% (125/125), 70.79 KiB, done. Total 125 (delta 86), reused 88 (delta 49) efrror: RPC failed; result=22, HTTP code = 0 atal: The remote end hung up unexpectedly fatal: The remote end hung up unexpectedly Everything up-to-date
As you can see the same result and no additional information related to the actual failure. So I tried the second command. This failed because I am on Windows, so there is no strace ( Systrace for Windows ). I also tried creating a branch on the network without a proxy (aka home) and was able to successfully git push --all from there. Like I said earlier. I can git push from the network for a proxy (aka office), but I can not do git push --all .