Git push "Remote end hung up"

Question

I created a new branch in my local repository and after some commits, I wanted to push it to a remote repository.

git push origin new_branch

I have this error:

$ git push origin new_branch

Counting objects: 32, done.

Delta compression using up to 2 threads. Compression of objects: 100% (18/18), done.

Object spelling: 100% (18/18), 5.29 KiB done. Total 18 (Delta 13), Reused 0 (Delta 0)

Write error: broken pipe

fatal: the far end unexpectedly hung up

fatal: the far end unexpectedly hung up

When I am a user of $ git remote -v

origin git @ 106.187.99.99: XXX.git (sample)

origin git @ 106.187.99.99: XXX.git (push)

git branch

fiberead_com$ git branch -a * new_branch master remotes/origin/HEAD -> origin/master remotes/origin/dev remotes/origin/master remotes/origin/online 

nginx.conf

 user www-data; worker_processes 1; error_log /var/log/nginx/error.log; pid /var/run/nginx.pid; events { worker_connections 1024; # multi_accept on; } http { include /etc/nginx/mime.types; access_log /var/log/nginx/access.log; sendfile on; #tcp_nopush on; #keepalive_timeout 0; # keepalive_timeout 65; client_header_timeout 3m; client_body_timeout 3m; keepalive_timeout 175 120; client_max_body_size 35m; tcp_nodelay on; gzip on; gzip_disable "MSIE [1-6]\.(?!.*SV1)"; include /etc/nginx/conf.d/*.conf; include /etc/nginx/sites-enabled/*; } 

Can anyone help me please?

My git server is in Linode. I am using GITLAB, and another project does not have this problem. Only a new project, the user of 'git clone' to pull out my computer. But when I click on the code, something is wrong.

I am using Nginx.

And I use the '$ git push origin master', have the same problem.

Answer 1

This means that the HTTP server responsible for listening to the request (here git push over http) could not be completed.

• Or because of a problem on the server:
  Only the log of the specified http server contains the main reason (this may be, for example, the message is too large to process the server, or the correct problem, or ...).
  These logs can be in etc/httpd/httpd.conf (Apache) or /var/log/nginx/error.log ( NGiNX ) or even in gitlab itself.

• Or because it never received a request that OP jesktop confirms this here:

I found the entire log, but the error log is empty.
The problem is in the network. Because I'm in China, and there is a special network.
Thus, VPN can solve this problem.

Answer 2

Try the following:

 git push origin feature/new_branch 

and also check if this connection is alive.