7

I'm trying to push the changes to Git remote repository, but got ended with following error message -

error: RPC failed; HTTP 500 curl 22 The requested URL returned error: 500 INKApi Error fatal: The remote end hung up unexpectedly fatal: The remote end hung up unexpectedly Everything up-to-date

I have followed the steps below till now -

  1. Made required configuration to clone the package

git config --global http.proxy http://mydomain\myusername:mypassword@myproxyserver:8080

  1. Cloned the repository using following line -

git clone http://mypackageurl

  1. Made some changes in existing method and saved the file
  2. Then executed following commands to add, commit & push

git add testpath/updatedfile.py

git commit -m "Updating sample script"

git push

git push origin master

But no luck, getting same error mentioned above.

Git clone was successful, didn't face any issue in that. While trying to push the change only getting HTTP 500 error. And I've installed GitHub desktop application and trying all these stuffs through Git Shell

starball
  • 20,030
  • 7
  • 43
  • 238
zeal
  • 475
  • 4
  • 11
  • 25
  • `git clone http://mypackageurl` usually you cannot push over http, error says that your server responses 500 (internal server error), so check server logs for anything suspicious. Which git repo manager do you use? – kan May 04 '16 at 09:14
  • As I remember, the http is read-only protocol, you could clone, but could not push. – kan May 04 '16 at 09:34
  • Yes, git http was read-only. According to this link : https://git-scm.com/book/tr/v2/Git-on-the-Server-The-Protocols#The-HTTP-Protocols Git can communicate over HTTP in two different modes. Prior to Git 1.6.6 there was only one way it could do this which was very simple and generally read-only. – Edvin May 04 '16 at 10:00
  • Cool... now it's clear that HTTP would allow two way communication. But could someone please help me in resolving the HTTP 500 error? – zeal May 04 '16 at 11:17

5 Answers5

16

Github itself may be down also. The status of GitHub can be observed at https://www.githubstatus.com/.

starball
  • 20,030
  • 7
  • 43
  • 238
apinanyogaratnam
  • 628
  • 7
  • 14
  • 2
    Objectivly, this answer isn't very good even if it's real – Elikill58 Mar 17 '22 at 15:24
  • As far as I can tell, the question is not actually about github. the error message the asker is getting indicates a relation to the apache traffic server proxy. – starball Nov 16 '22 at 22:33
8

Increase the Git buffer size to the largest individual file size of your repo:

git config --global http.postBuffer 157286400

http.postBuffer

Maximum size in bytes of the buffer used by smart HTTP transports when POSTing data to the remote system. For requests larger than this buffer size, HTTP/1.1 and Transfer-Encoding: chunked is used to avoid creating a massive pack file locally. Default is 1 MiB, which is sufficient for most requests.

Praveen Govind
  • 2,619
  • 2
  • 32
  • 45
  • If you are sure that this is the cause of the error, then I'd suggest marking this question as a duplicate of [Git, fatal: The remote end hung up unexpectedly](https://stackoverflow.com/q/15240815/11107541), where a similar answer already exists (though it might help if you improved it there :) ). However, I'm inclined to believe the problem is related to their proxy, since the error message includes a portion that seems specific to Apache Traffic Server. – starball Nov 17 '22 at 02:27
0

I am running Gitlab Community Edition version 8.10.6. To solve this issue I changed two params in my /etc/gitlab/gitlab.rb configuration file. I show the default values in the commended rows.

# gitlab_rails['git_max_size'] = 20971520
gitlab_rails['git_max_size'] = 524288000

# nginx['client_max_body_size'] = '250m'
 nginx['client_max_body_size'] = '0'

After that I run the above commands (the second is optional),

gitlab-ctl reconfigure
gitlab-ctl restart
Georgios Syngouroglou
  • 18,813
  • 9
  • 90
  • 92
0

First, i tried and i get the same Error.

But i went to the config Project in Gitlab, and i add my email to members in project, and after i changed the SSH url to HTTPS i make again the git remote add and it works

Sebastian Agreda
  • 11
  • 1
0

I know github is down right now, but somehow this works for me everytime I try to push.

git pull --rebase
git push
ouflak
  • 2,458
  • 10
  • 44
  • 49
bhpcv
  • 28
  • 5