Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Search
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

Cloudron Forum

Apps - Status | Demo | Docs | Install
  1. Cloudron Forum
  2. GitLab
  3. GitLab project uploads API Size Limit

GitLab project uploads API Size Limit

Scheduled Pinned Locked Moved GitLab
gitlab
7 Posts 3 Posters 3.0k Views 3 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • A Offline
    A Offline
    allanbowe
    wrote on last edited by
    #1

    When pushing artefacts in a gitlab runner, we get the following message:
    365c09ba-b834-4568-b6fb-4e9e636a7d0f-image.png

    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:

    5fb02eb2-1425-4093-90e2-ace33470175f-image.png

    Is there something we are missing?

    girishG 2 Replies Last reply
    0
    • robiR Offline
      robiR Offline
      robi
      wrote on last edited by
      #2

      perhaps this error response is from nginx?

      Conscious tech

      A 1 Reply Last reply
      0
      • robiR robi

        perhaps this error response is from nginx?

        A Offline
        A Offline
        allanbowe
        wrote on last edited by
        #3

        @robi yes - it appears that way - I tried to modify the nginx.conf but it's read only from the cloudron shell

        robiR 1 Reply Last reply
        0
        • A allanbowe

          @robi yes - it appears that way - I tried to modify the nginx.conf but it's read only from the cloudron shell

          robiR Offline
          robiR Offline
          robi
          wrote on last edited by
          #4

          @allanbowe that would be the package version which @staff would have to modify.

          There is also the Nginx reverse proxy for the app in the host OS.

          Conscious tech

          1 Reply Last reply
          0
          • A allanbowe

            When pushing artefacts in a gitlab runner, we get the following message:
            365c09ba-b834-4568-b6fb-4e9e636a7d0f-image.png

            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:

            5fb02eb2-1425-4093-90e2-ace33470175f-image.png

            Is there something we are missing?

            girishG Offline
            girishG Offline
            girish
            Staff
            wrote on last edited by
            #5

            @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.

            1 Reply Last reply
            0
            • girishG Offline
              girishG Offline
              girish
              Staff
              wrote on last edited by
              #6

              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?

              1 Reply Last reply
              0
              • A allanbowe

                When pushing artefacts in a gitlab runner, we get the following message:
                365c09ba-b834-4568-b6fb-4e9e636a7d0f-image.png

                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:

                5fb02eb2-1425-4093-90e2-ace33470175f-image.png

                Is there something we are missing?

                girishG Offline
                girishG Offline
                girish
                Staff
                wrote on last edited by
                #7

                @allanbowe Please try with the latest package. For good measure, I added the client_max_body_size directive to the top level.

                1 Reply Last reply
                0

                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
                Reply
                • Reply as topic
                Log in to reply
                • Oldest to Newest
                • Newest to Oldest
                • Most Votes


                • Login

                • Don't have an account? Register

                • Login or register to search.
                • First post
                  Last post
                0
                • Categories
                • Recent
                • Tags
                • Popular
                • Bookmarks
                • Search