Recently it became impossible to push updates to our Gitea-hosted repo. We receive an error (shown below) that I do not know how to solve. A potential solution is to configure an SSH+GIT options, but this would require changes to our Kubernetes ingress rules that I’m not sure I can actually make (we are running Gitea as a Kubernetes deployment). I was able to push the updates to another copy of this repository on the host machine via
ssh, but if I can’t push to the Gitea-controlled repo there is not much use to us for Gitea. Any help would be appreciated.
Pushing to https://example.com/repo.git Enumerating objects: 139, done. Counting objects: 100% (139/139), done. Delta compression using up to 12 threads Compressing objects: 100% (106/106), done. Writing objects: 100% (124/124), 5.71 MiB | 149.90 MiB/s, done. Total 124 (delta 24), reused 116 (delta 16) POST git-receive-pack (5986730 bytes) error: RPC failed; HTTP 413 curl 22 The requested URL returned error: 413 fatal: the remote end hung up unexpectedly fatal: the remote end hung up unexpectedly Everything up-to-date