Error uploading release asset: 502 - Bad Gateway

Lilith River's Avatar

Lilith River

10 Nov, 2020 10:12 PM

I'm having a persistent issue trying to upload assets to GitHub which is blocking my release process

Error uploading release asset: 502 - Bad Gateway

GitHub seems to be up:

  1. 1 Posted by Lilith River on 10 Nov, 2020 10:15 PM

    Lilith River's Avatar
    Collecting artifacts...
    Found artifact 'artifacts\nuget\' matching 'artifacts\nuget\*.nupkg' path
    Found artifact 'artifacts\nuget\' matching 'artifacts\nuget\*.nupkg' path
    No artifacts found matching 'artifacts\*' path
    Uploading artifacts...
    [1/2] artifacts\nuget\ (1,900,537 bytes)...100%
    [2/2] artifacts\nuget\ (3,285,961 bytes)...100%
    Deploying using GitHub provider
    Creating "v1.5.1-rc55" release for repository "imazen/imageflow" tag "v1.5.1-rc55" commit "454c9dd0821fc013f1827453226a17f455cc17ad"...Skipped - release with tag "v1.5.1-rc55" already exists
    Deleting existing release asset ""...OK
    Uploading "" to release assets...Failed
    Will try again in 10 seconds...
    Deleting existing release asset ""...OK
    Re-uploading "" to release assets...Error uploading release asset: 502 - Bad Gateway
  2. Support Staff 2 Posted by Feodor Fitsner on 11 Nov, 2020 12:37 AM

    Feodor Fitsner's Avatar

    Hi Lilith,

    Sorry about that. It could be a temporary issue. It's not a "transport" error, but clearly a response from a GitHub side. Usually, 502 is being sent by load balancer when there is faulty instance behind it. We dealt with GitHub support on this issue in the past. I'm going to contact their support again.

    Btw, try bumping version to have a different release file name (version/commit) as it might stuck on specifically - you've been trying for 3+ hours to upload with the same name.

  3. Support Staff 3 Posted by Feodor Fitsner on 11 Nov, 2020 12:54 AM

    Feodor Fitsner's Avatar

    Reported to GitHub.

    To instrument that we even created a PS script replicating built-in deployment provider, so it could be used instead:

    Another idea - you could create a new "GitHub Releases" environment on "Environments" page and then asynchronously deploy to that environment during the build ( Also, you'd be able to repeat the deployment of the same artifacts over again without re-running the entire build.

  4. Support Staff 4 Posted by Feodor Fitsner on 11 Nov, 2020 05:29 AM

    Feodor Fitsner's Avatar

    Alright, got a response from GitHub:

    Thanks for contacting GitHub Support! We had a temporary issue with the Releases earlier today, but it should now be resolved.
    Please let us know if you're still seeing any errors.

  5. 5 Posted by Lilith River on 11 Nov, 2020 06:18 AM

    Lilith River's Avatar

    Thank you so much!

Reply to this discussion

Internal reply

Formatting help / Preview (switch to plain text) No formatting (switch to Markdown)

Attaching KB article:


Attached Files

You can attach files up to 10MB

If you don't have an account yet, we need to confirm you're human and not a machine trying to post spam.

Keyboard shortcuts


? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac