One-Click App (GitLab CE) - "Github Push Error: RPC failed; result=22, HTTP code = 413"

Was having this same issue with the DigitalOcean one click install of GitLab CE. It seems the fix is related to either Apache or Nginx. (Unsure what’s installed by the one-click installer.)

DigitalOcean recommended via Twitter to come here for help with resolving this due to the lack of any kind of tutorial on fixing this problem.

Can anyone help?


Submit an answer
You can type!ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

The DigitalOcean GitLab One-Click image uses GitLab’s “omnibus” installer which bundles it’s own copy of Nginx. You can insert custom Nginx settings, by editing /etc/gitlab/gitlab.rb If you wanted to increase the client_max_body_size add this line:

nginx['client_max_body_size'] = '50m'

For the change to take effect, you must then run: sudo gitlab-ctl reconfigure

For more information on customizing GitLab’s Nginx configuration, see the upstream documentation.

Hey there, I read over that stack overflow and you want to take a look at the solution for Nginx that was proposed in the top answer. I’ll copy it below:

Just load your nginx.conf and add client_max_body_size 50m; ( changing the value to your needs ) in the http block.

Reload nginx to accept the new config by executing sudo service nginx reload and try again to push your commit over http.

Andrew DigitalOcean TechOps