2: fatal: The remote end hung up unexpectedly For all the cases reported, beside the 403 problem, they are all caused by the remote server end hung up unexpectedly. In this case it is BitBucket terminates connection for some unknown reason. We notice that by disable git shallow fetch ( --depth=1 ), the problem does not occur anymore.
2: fatal: The remote end hung up unexpectedly For all the cases reported, beside the 403 problem, they are all caused by the remote server end hung up unexpectedly. In this case it is BitBucket terminates connection for some unknown reason. We notice that by disable git shallow fetch ( --depth=1 ), the problem does not occur anymore.
Sep 12, 2015 · I just ran into a very similar error (for which this answer is the top google result) - the solution was in a comment by @Liviu Chircu The solution was to put the .git on the end of the url git clone http://myURL/projectname Cloning into 'projectname'... error: RPC failed; result=22, HTTP code = 404 fatal: The remote end hung up unexpectedly
This is the error code coming from libcurl, the underlying library used in http communications with Git. From the libcurl documentation, a result code of 22 means: CURLE_HTTP_RETURNED_ERROR (22) This is returned if CURLOPT_FAILONERROR is set TRUE and the HTTP server returns an error code that is >= 400.
11.09.2015 · POST git-receive-pack (490857233 bytes) error: RPC failed; result=22, HTTP code = 404. fatal: The remote end hung up unexpectedly. Everything up-to-date. Completed with errors, see above. I have already tried the following: git config --global http.postBuffer 524288000. git atlassian-sourcetree azure-devops.
I got the following error message when I tried to push my code: error: RPC failed; result=22, HTTP code = 401 fatal: The remote end hung up unexpectedly ...
26.11.2013 · Total 47 (delta 0), reused 0 (delta 0) error: RPC failed; result=22, HTTP code = 411 fatal: The remote end hung up unexpectedly fatal: The remote end hung up unexpectedly Everything up-to-date. The solution is the run the below command on the client to increase the postBuffer size before trying to re-run the git push.
Specifically, the 'result=22' portion. This is the error code coming from libcurl, the underlying library used in http communications with Git. From the libcurl documentation, a result code of 22 means: CURLE_HTTP_RETURNED_ERROR (22) This is returned if CURLOPT_FAILONERROR is set TRUE and the HTTP server returns an error code that is >= 400. Cause