Sudden butler failure in CI

A topic by eurac created Apr 20, 2022 Views: 658 Replies: 2

Viewing posts 1 to 2

Hi! Since last week, butler worked perfectly in my GitLab CI, but it started returning 403.

When pushing to an existing channel, i get this 403, which really sounds like GCS dislikes my CI:

> For channel `html5`: last build is 551790, downloading its signature api.itch.io: HTTP 403: <?xml version='1.0' encoding='UTF-8'?><Error><Code>AccessDenied</Code><Message>Access denied.</Message><Details>We're sorry, but this service is not available in your location</Details></Error> in conn.tryConnect, got HTTP non-2XX

Full log here: https://gitlab.inf.unibz.it/commul/oetzit/-/jobs/42769/raw

When pushing to a new channel i get another 403, with no clear message.

Full log here: https://gitlab.inf.unibz.it/commul/oetzit/-/jobs/42783/raw

Locally, everything works just fine.

Has anyone ever experienced this?

Like Reply

leafoAdmin2 years ago(+1)

I’ve never encountered this error before. This looks like an error coming directly from our storage provider, Google Cloud Storage. Butler implements uploads by generating a secure upload URL remotely, then sends it to your machine to upload the file directly to Google’s server for storage. (The file bytes skip our servers entirely to avoid any additional processing/slowdown).

This error suggests to me that something about the server you are running CI on is being restricted from accessing Google’s services.

Hope that helps

Like Reply

eurac2 years ago

In the end, this had nothing to do with butler or GCS; the issue solved itself after a GitLab update and a runner reconfiguration of which I unfortunately know nothing, so I'm afraid I don't have much information for future readers. :/

In any case, thanks for the support!

Like Reply