none
VS Source Control GIT: RPC failed; HTTP 500 curl 22 The requested URL returned error: 500 RRS feed

  • Question

  • Unable to Push source control.  this has been working for years and unsure what changed or how to debug.  I am able to login to Bonobo.Git.Server.  any thoughts or help is greatly appreciated.  

    Opening repositories:
    C:\Users\JBrown\Documents\DotNet-Projects\WindowsApplication1
    Pushing master
    Error encountered while pushing branch to the remote repository: Git failed with a fatal error.
    the remote end hung up unexpectedly
    the remote end hung up unexpectedly
    RPC failed; HTTP 500 curl 22 The requested URL returned error: 500
    Pushing to http://servername/Bonobo.Git.Server/WindowsApplication1.git
    Everything up-to-date


    Work Smarter Not Harder

    Monday, January 20, 2020 11:04 PM

Answers

  • Hi jimbrown.ws,

    Welcome to MSDN forum.

    Actually, HTTP 500 error is related to web server, it means something has gone wrong on the website’s server. So, normally, this issue isn’t caused by you or your project, I think there is something wrong with server.

    No matter how you change/debug on your side, if you don’t check the server, this issue maybe couldn’t be solved. So I suggest you should check/confirm if there is something wrong with server.

    Some similar issues PRC failed  git push large repository fail.

    BTW, since your issue is more related to Git Server, I recommend you could start a new thread in Stack Overflow tagged git or GitLab and seek for a more professional help.

    Hope all above could help you.

    Sincerely,

    Tianyu


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    • Marked as answer by jimbrown.ws Thursday, January 23, 2020 10:13 PM
    Tuesday, January 21, 2020 5:05 AM

All replies

  • FYI I tried these things and they did not help.  I also can push a very small project  or files that are 35kb or less I start getting the errors 36kb file or bigger.

    git config --global http.postBuffer 157286400

    git config --global http.postBuffer 524288000

    https://bonobogitserver.com/frequently-asked-questions/ 

    Cloning Error - RPC failed

    There are multiple reasons why this error can occure on the client, but the most frequent ones are related to the size of the request. If you encounter this issue try to increase the following values.

    • run git config http.postBuffer [desired size] on your client, you can try 524288000
    • increase <requestLimits maxAllowedContentLength=”[desired size]”> in web.config; the size could be 1073741824
    • increase <httpRuntime maxRequestLength=”[desired size]”> in web.config; try the value 1024000

    Apparently, there is no need in limiting maxRequestLength on IIS 8.0 so if you run into troubles, try to remove the line.


    Work Smarter Not Harder


    • Edited by jimbrown.ws Tuesday, January 21, 2020 9:13 PM
    Tuesday, January 21, 2020 2:44 AM
  • Hi jimbrown.ws,

    Welcome to MSDN forum.

    Actually, HTTP 500 error is related to web server, it means something has gone wrong on the website’s server. So, normally, this issue isn’t caused by you or your project, I think there is something wrong with server.

    No matter how you change/debug on your side, if you don’t check the server, this issue maybe couldn’t be solved. So I suggest you should check/confirm if there is something wrong with server.

    Some similar issues PRC failed  git push large repository fail.

    BTW, since your issue is more related to Git Server, I recommend you could start a new thread in Stack Overflow tagged git or GitLab and seek for a more professional help.

    Hope all above could help you.

    Sincerely,

    Tianyu


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    • Marked as answer by jimbrown.ws Thursday, January 23, 2020 10:13 PM
    Tuesday, January 21, 2020 5:05 AM
  • I re-staged my server and IIS it's a Hyper-V Virtual Server and that fixed the issue as well as updated my Bonobo.Git.Server to 6.5.   

    Work Smarter Not Harder

    Thursday, January 23, 2020 10:16 PM