No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

```pulumi plugin install resource aws
error: 401 HTTP error fetching plugin from <https://api.github.com/repos/pulumi/pulumi-aws/releases/latest>```

locally. but seeing the same issue with github workflow

could you run
```curl -i <https://api.github.com/repos/pulumi/pulumi-aws/releases/latest>```

any chance you could add it as a step to your action as well?

the solution is to add a GITHUB_TOKEN env var to your action, but we’re seeing increased instances of this so trying to get more info

ok, that looked to work, even if the var is blank

Hi, I'm having a similar error. empty `GITHUB_TOKEN` doesn't help.

I use `pulumi/pulumi:latest` image

```$ pulumi preview

Previewing update (dev):

warning: A new version of Pulumi is available. To upgrade from version '3.56.0' to '3.57.0', visit <https://pulumi.com/docs/reference/install/> for manual instructions and release notes.

error: could not load plugin for gcp provider 'urn:pulumi:dev::xxxx::pulumi:providers:gcp::default': Could not automatically download and install resource plugin 'pulumi-resource-gcp', install the plugin using `pulumi plugin install resource gcp`.

Underlying error: 401 HTTP error fetching plugin from <https://api.github.com/repos/pulumi/pulumi-gcp/releases/latest>```

`pulumi plugin install resource gcp` brings the same error: error: `401 HTTP error fetching plugin from <https://api.github.com/repos/pulumi/pulumi-gcp/releases/latest>`

These 401 errors are a little surprising. We can't see any clear documented reason from GitHub why they'd be happening but we have a ticket now open to investigate: <https://github.com/pulumi/pulumi/issues/12379>

If I use my own GITHUB_TOKEN would that solve it temporarily ?

Probably, we're assuming this is related to rate limits despite being 401 not 403 like a normal rate limit error. Would be good to hear back if that does actually help.

After adding `- export GITHUB_TOKEN=${PULUMI_TOKEN_GITHUB}` to the pipeline, pulumi works.

I used `<https://github.com/settings/personal-access-tokens/new>  New fine-grained personal access token Beta` with `Public Repositories (read-only)`

Updated github ticket: <https://github.com/pulumi/pulumi/issues/12379#issuecomment-1461658628>

We've raised <https://github.com/pulumi/pulumi/issues/12391> to track this 401 issue, looks like a auth header regression in 3.56 when we refactored to code to also support GitLab auth headers. Fix should be released today in 3.57.1.

3.57.1 has been released with a fix for this