Adding PackageReference for package fails with 401 (Unauthorized)

Question

I am trying to install a third-party NuGet package (e.g. StyleCop) into a project. The project also has packages that are installed from our own private NuGet feed. When trying to install the package, we receive a 401 error like this.

MyProject> dotnet add .\MyProject.csproj package StyleCop
  Determining projects to restore...
  Writing C:\Users\me\AppData\Local\Temp\tmp6A51.tmp
info : Adding PackageReference for package 'StyleCop' into project '.\MyProject.csproj'.
info :   CACHE https://api.nuget.org/v3/registration5-gz-semver2/stylecop/index.json
info :   GET https://mediavaletsc.pkgs.visualstudio.com/_packaging/c559332f-5d8d-4d3f-8fc2-6e06125775fa/nuget/v3/registrations2-semver2/stylecop/index.json
info :   Unauthorized https://mycompany.pkgs.visualstudio.com/_packaging/xxx-xxx-xxx-xxx-xxx/nuget/v3/registrations2-semver2/stylecop/index.json 680ms
error: Response status code does not indicate success: 401 (Unauthorized).

Oddly enough, running dotnet restore works just fine, even after doing a git clean -xfd. How can we configure dotnet and/or nuget to accept the installation of StyleCop or any other public package?

Shaun Luttin · Accepted Answer · 2021-03-27 00:32:28Z

4

We needed to re-authenticate with Visual Studio Team Services (VSTS) because the API key had expired and/or been revoked.

The reason dotnet restore still worked, but dotnet add ... package ... failed, was because the former used the local cache, whereas the latter hit the server. Restore also stopped working after we ran nuget locals all -clear.

To re-authenticate with did the following.

nuget sources remove -name $sourceName | Out-Null;
nuget sources add -name $sourceName -source $sourcePath -username $username -password $apiKey

answered Mar 27, 2021 at 0:32

Shaun Luttin

143k93 gold badges443 silver badges495 bronze badges

Sign up to request clarification or add additional context in comments.

3 Comments

Edward Han-MSFT Over a year ago

Hi, Thanks for the sharing, you could Accept it as an Answer, it could help other community members who get the same issues, thanks.

Shaun Luttin Over a year ago

Done. Thx for the feedback @EdwardHan-MSFT.

R.D. Alkire Over a year ago

Similar situation here. Currently wanted to update a package from nuget itself, not from our own VSTS, so from this answer I was able: dotnet nuget disable source name-of-our-internal-source

Collectives™ on Stack Overflow

Adding PackageReference for package fails with 401 (Unauthorized)

1 Answer 1

3 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

3 Comments

Your Answer

Sign up or log in

Post as a guest

Related