Getting 403 response from GitHub

[cglewis]

I'm using this on several projects and they all started doing this just today:

Run crazy-max/ghaction-docker-buildx@v1.6.0
✅ Buildx version found: v0.4.1
⬇️ Downloading https://github.com/docker/buildx/releases/download/v0.4.1/buildx-v0.4.1.linux-amd64...
##[error]Unexpected HTTP response: 403

The yaml for that step is pretty vanilla:

    - name: Set up Docker Buildx
      id: buildx
      uses: crazy-max/ghaction-docker-buildx@v1.6.0
      with:
        buildx-version: latest
        qemu-version: latest

I just updated to 1.6.0 today, it's also broken on 1.4.0 which is what I was using before.

[crazy-max]

Hi @cglewis, do you have a link to your repo pls?

[crazy-max]

@cglewis Ok just found it's https://github.com/CyberReboot/poseidon. I will try to reproduce with your workflow. Keep you in touch.

[crazy-max]

@cglewis Cannot reproduce with this workflow. There is maybe a limitation if your org triggers to much calls to the download release endpoint. I'll see if it's possible to use the GITHUB_TOKEN to lift this limit if that's the case.

[cglewis]

Huh. I've never run into limits before. Interesting. I'll try it out later and see if resolves itself. Thanks for looking into it!

[crazy-max]

@cglewis

Huh. I've never run into limits before

Me neither and I download assets through many other actions I made so I'm pretty worried about it 😅

Thanks for looking into it!

Sure you're welcome

[cglewis]

@crazy-max I just retriggered the workflow, to see if it worked, and seems happy again. Could have been a GitHub/S3 issue. I'm going to close this for now, but will reopen if I run into the issue again. Thanks again for an awesome project and the quick response!

[crazy-max]

@cglewis

I just retriggered the workflow, to see if it worked, and seems happy again. Could have been a GitHub/S3 issue. I'm going to close this for now, but will reopen if I run into the issue again.

I was going to say the same thing to you, it seems to happen with the HEAD response returning a 403 from S3 indeed. Let's keep an eye on it. I'll do some more research of my own.

Thanks again for an awesome project and the quick response!

🤝

[crazy-max]

@cglewis Next time you've got this issue, please add the secret ACTIONS_STEP_DEBUG to true on your repo.

[crazy-max]

@cglewis Ok this is an incident with GitHub.

[cglewis]

Ahh! Nice find! I actually looked there first, and it was all green at the time!

[crazy-max]

To avoid this problem in the future, I will use the runner cache system to avoid re-downloading buildx at each build if the version did not changed.

[crazy-max]

@cglewis Cache of Buildx binary is now implemented.