HTTP push fails with Error 500 #408

New Issue

GiteaMirror · 2025-11-02T03:22:06-06:00

GiteaMirror commented

2025-11-02 03:22:06 -06:00

Originally created by @simonthum on GitHub (Feb 28, 2017).

Hi all,

I am trying to upload an insanely oversized repo (ex SVN) using plain http to my freshly installed gitea 1.0.1. on windows, installed as a service. Smaller repos worked fine.

$ git push mine --all
Counting objects: 85538, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (19927/19927), done.
Writing objects: 100% (85538/85538), 1.99 GiB | 11.15 MiB/s, done.
Total 85538 (delta 69000), reused 79958 (delta 64546)
error: RPC failed; HTTP 500 curl 22 The requested URL returned error: 500 Internal Server Error
fatal: The remote end hung up unexpectedly
fatal: The remote end hung up unexpectedly
Everything up-to-date

http.log:

2017/02/28 13:06:12 [...routers/repo/http.go:385 serviceRPC()] [E] fail to serve RPC(receive-pack): exit status 128

Other logs did not show correlated events.

It seems I am hitting some POST size limit. Is it possible to adjust this limit?

(I know how to organize repos better and smaller in general...)

Originally created by @simonthum on GitHub (Feb 28, 2017). Hi all, I am trying to upload an insanely oversized repo (ex SVN) using plain http to my freshly installed gitea 1.0.1. on windows, installed as a service. Smaller repos worked fine. ``` $ git push mine --all Counting objects: 85538, done. Delta compression using up to 4 threads. Compressing objects: 100% (19927/19927), done. Writing objects: 100% (85538/85538), 1.99 GiB | 11.15 MiB/s, done. Total 85538 (delta 69000), reused 79958 (delta 64546) error: RPC failed; HTTP 500 curl 22 The requested URL returned error: 500 Internal Server Error fatal: The remote end hung up unexpectedly fatal: The remote end hung up unexpectedly Everything up-to-date ``` http.log: ```` 2017/02/28 13:06:12 [...routers/repo/http.go:385 serviceRPC()] [E] fail to serve RPC(receive-pack): exit status 128 ```` Other logs did not show correlated events. It seems I am hitting some POST size limit. Is it possible to adjust this limit? (I know how to organize repos better and smaller in general...)

GiteaMirror added the issue/duplicate label 2025-11-02 03:22:06 -06:00

GiteaMirror closed this issue

2025-11-02 03:22:06 -06:00

GiteaMirror commented

2025-11-02 03:22:07 -06:00

@lunny commented on GitHub (Feb 28, 2017):

This is a known issue #218 and should be resolved by #1030 which has been merged to v1.1.

@lunny commented on GitHub (Feb 28, 2017): This is a known issue #218 and should be resolved by #1030 which has been merged to v1.1.

GiteaMirror commented

2025-11-02 03:22:07 -06:00

@simonthum commented on GitHub (Mar 2, 2017):

Sorry I didn't find it, thanks a lot!