The Remote End Hung Up Unexpectedly Sourcetree

  1. Git Remote Hung Up
  2. Sourcetree Clone Fatal The Remote End Hung Up Unexpectedly
  3. The Remote End Hung Up Unexpectedly Sourcetree Video

How to troubleshoot 'remote end hung up unexpectedly' error in Git?Helpful? Please support me on Patreon: thanks &. Compressing objects: 100% (318), done. Error: RPC failed; result=22, HTTP code = 411 fatal: The remote end hung up unexpectedly Writing objects: 100% (23669), 483.30 MiB 114.26 MiB/s, done. Total 2332669 (delta 1949888), reused 2330461 (delta 1949349) fatal: The remote end hung up unexpectedly.

If you are setting up your gitlab behind an apache server as described on my previous article, you will soon find out that you cannot push up your code into your gitlab and gitlab will throw you the following error

However, if you try to push a single file change, you can safely push the code without getting any kind of annoying errors.

Solution

In order for you to push your code into your gitlab apache setup you will need to do 2 things.

Compressing objects: 100% (1280/1280), done. Error: RPC failed; result=22, HTTP code = 413 116 KiB/s fatal: The remote end hung up unexpectedly Writing objects: 100% (2504/2504), 449.61 MiB 4.19 MiB/s, done. Total 2504 (delta 1309), reused 2242 (delta 1216) fatal: The remote end hung up unexpectedly Everything up-to-date. Compressing objects: 100% (27/27), done. Error: RPC failed; HTTP 403 curl 22 The requested URL returned error: 403 Forbidden fatal: The remote end hung up unexpectedly Writing objects: 100% (29/29), 1.42 MiB 805.00 KiB/s, done. Total 29 (delta 20), reused 0 (delta 0) fatal: The remote end hung up unexpectedly Everything up-to-date.

Firstly you will need to run the below code on your client side (your computer!)

Unexpectedly

And the second steps you will need to do is to increase the timeout on gitlab! On the server, open the file unicore.rb

Git

and look for the line

at line 30, you will see that you will need to change this number to something bigger, for my case, i changed it to 3600 (1 hour)

after you have updated this value, you will need to restart gitlab!

Once you restarted gitlab, try to push your code again, you should be getting this

don't you just hate apache when everyone is using nginx for gitlab? haha..

Git Remote Hung Up

*************************************** UPDATE ********************************

*shy* i'm also using nginx now lol for reverse proxy... if everything above doesn't work, go to your nginx configuration and adjust your client_max_body_size

increasing this will allow your data to be send over to your server safely!

No related posts.

  • Status:Closed(View Workflow)
  • Resolution: Fixed
  • Labels:
  • Bug Fix Policy:

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

Sourcetree Clone Fatal The Remote End Hung Up Unexpectedly

{{

{[[email protected]:etc]# git push -u origin masterPassword 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 = 0fatal: The remote end hung up unexpectedlyWriting 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[[email protected]:etc]# git --versiongit version 1.7.8.3[[email protected]:etc]# git config --get remote.origin.urlhttps://[email protected]/dyno/etc.dyno.git}

}}

Attachments

  1. 787710903-Screen%20Shot%202016-02-23%20at%2012.06.43.png
    82 kB

The Remote End Hung Up Unexpectedly Sourcetree Video

Votes:
4Vote for this issue
Watchers:
25Start watching this issue