Pushing to BitBucket Gives "413 Request Entity Too Large" But No Large Files

Question

I am trying to push a local repo (initial commit) into BitBucket using SourceTree. SourceTree gives the following error:

413 Request Entity Too Large

However, the largest file in my repo is 995kb and I get this even if I exclude it. The entire repo is about 36mb.

I set the http.postBuffer to some arbitrarily large value in my local git.

LFS is enabled in the repo.

I get the same error from command line.

TIA for any help.

Rasti · Answer

I was experiencing the same issue, however not by pushing to Bitbucket repository, but by posting code insights via REST API as described at https://developer.atlassian.com/server/bitbucket/tutorials-and-examples/code-insights-tutorial. The posted JSON has few kilobytes. The curl was giving me just HTTP 413.

We use the Official Bitbucket Docker image, with no Apache nor Nginx in front of Bitbucket, so I was wondering, where is the error coming from. After looking into the response body it turned out to be a hard limit of annotations count allowed to be posted within the report to 1000. The response was:

{"errors":[{"context":null,"message":"Max annotation limit would be exceeded. Only 1,000 annotations can be stored for a single report","exceptionName":null}]}

Hope it helps someone stumbling upon a similar issue.

Michael Brown [Ascend] · Answer

To follow on Justin's point, we just resolved this issue for one our clients. We did so by updating the following to the NGINX  Configuration:

* Go to /etc/nginx
* Open the nginx.conf
* Add the following lines to the configuration:* client_max_body_size 500M;
* client_body_timeout 120s;

* Restart NGINX

Apache has a similar setting I believe that needs to be updated as well.

Bob Hatcher_sc6kh6 · Answer

Thank you, I have referred this to the appropriate people at my company. In the meantime I was able to push using ssh.