GitLab project uploads API Size Limit
-
When pushing artefacts in a gitlab runner, we get the following message:
in text form:
[2:26:53 PM] [semantic-release] [@semantic-release/gitlab] › ✖ An error occurred while uploading /builds/clients/dwp_frs/artefacts/viya.sas to the GitLab project uploads API: HTTPError: Response code 413 (Request Entity Too Large) at Request.<anonymous> (/builds/clients/dwp_frs/node_modules/got/dist/source/as-promise/index.js:118:42) at runMicrotasks (<anonymous>) at processTicksAndRejections (node:internal/process/task_queues:96:5) { code: 'ERR_NON_2XX_3XX_RESPONSE', timings: { start: 1662647207472, socket: 1662647207474, lookup: 1662647207481, connect: 1662647207520, secureConnect: 1662647207559, upload: 1662647213057, response: 1662647213651, end: 1662647213651, error: undefined, abort: undefined, phases: { wait: 2, dns: 7, tcp: 39, tls: 39, request: 5498, firstByte: 594, download: 0, total: 6179 } } }
We tried increasing the max artifacts size as described here, but the error persists, even after a restart:
Is there something we are missing?
-
@allanbowe Atleast, on nginx side, it allows uploads of all size. We use the upstream nginx config file https://github.com/gitlabhq/gitlabhq/blob/master/lib/support/nginx/gitlab#L88 which has
client_max_body_size 0
. -
I double checked and
client_max_body_size
is set to 0 everywhere (meaning no limit in nginx side). Can you check the size of the artifact that you are trying to upload? -
@allanbowe Please try with the latest package. For good measure, I added the
client_max_body_size
directive to the top level.