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?
-
@robi yes - it appears that way - I tried to modify the nginx.conf but it's read only from the cloudron shell
-
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. -
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?
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login