Gitlab Self-Hosted: ERROR: Uploading artifacts as “archive” to coordinator… too large archive

Question

Some time ago, our Gitlab (self-hosted) instance started to throw errors that the archives are too big:

ERROR: Uploading artifacts as "archive" to coordinator... too large archive id=something responseStatus=413 Request Entity Too Large status=413 token=something FATAL: too large
ERROR: Job failed: exit code 1

The only resolution ideas we found was to set the max build artifact size (it's under /admin/application_settings). This did not work for us, the error still occurred.

Reference articles:

• https://gitlab.com/gitlab-com/gl-infra/infrastructure/-/issues/3813
• https://dzone.com/articles/gitlab-ci-runner-artifacts-size-error-quottoo-larg
• https://www.kevinhooke.com/2018/07/30/gitlab-ci-runner-artifacts-size-error-too-large-archive/
• https://forum.gitlab.com/t/uploading-artifacts-too-large-archive-error-413/4867
• How to increase maximum artifacts size for Gitlab on-premises

Answer 1

The solution to this issue is to set the max build artifact size (under /admin/application_settings) and to increase the Gitlab NGINX client_max_body_size property in the configuration file to something higher.