[Solved] Telerik NuGet package source Showing Unauthorized 401 error

[Camron]

I am trying to follow the instructions on this URL: https://www.telerik.com/aspnet-core-ui/documentation/getting-started/video-onboarding

I added the source to the Nuget settings with this URL: https://nuget.telerik.com/v3/index.json

When I go to the NuGet package manager and select the Telerik. The first time I did enter credentials but I got a 

[Telerik] Unable to load the service index for source https://nuget.telerik.com/v3/index.json.
  Response status code does not indicate success: 401 (Unauthorized).

Since then I have tried removing and re-adding the source but I always get the same error and I can't re-enter my credentials to see if that is the issue. 

How do I check if I entered my credentials wrong and How do I fix this so I have access to the telerik nuget source?

[Lance | Senior Manager Technical Support]

Hi Cameron, this sounds like you have some credentials cached, or you have a nuget.config with incorrect credentials. I have two things for you to try:

1. Close any IDE/tooling that might be using NuGet.
2. Open the Windows Credential Manager app
3. Switch to the Windows Credentials tab
4. Scroll down and locate two items;  "nuget.telerik.com" and "VSCredential_nuget.telerik.com"
5. Edit both of them... or delete them and re-enter the credentials when VS tries to load the source again.

Now, let's see if you have anything in a nuget.config.

1. First, lets check the default global file, open %appdata%/NuGet/NuGet.Config
   1. Do you have a packageSourceCredentials section for the Telerik source?
   2. If yes, either delete it or update it (if you update it, do not use your password, use a Telerik NuGet Key instead)
2. Next, lets check for a nuget.config in your source code. This is a very common approach to also include a nuget.config file in the sync source code (it's usually in the folder next to the sln file, but can be in the project folder or higher up).
   1. In that project-specific config file, do you see a packageSourceCredentials section like mine? => src/NuGet.Config#L21-L26 
   2. If yes, this is used for building the code in CI/CD, there is typically an environment variable placeholder. You can add those two env vars to your OS user's environment and it will be used when .NET SDK or VS tries to connect to that exact source.

I would personally just delete all the items in Credential Manager and let VS2022 re-save them the next time you open a project. Keep in mind that if you also have a nuget.config with a packageSourceCredential, that will be used instead.

[Kristin]

It should not be this difficult to simply use Telerik. We have a paid subscription and I have yet been able to do anything without the prompts that says I don't have a subscription.

 

[Lance | Senior Manager Technical Support]

Hi Kristin, This sounds different than setting credentials (the problem Cameron had).

Since you can build and run the app, it means your dotnet restore is suceeeding, the compilations is okay and your package sources are working as expected.

Problem

Rather, if you are seeing that watermark at runtime means when you compiled the code, there was no license file present on your machine.

This is a protection mechanism to prevent an unauthorized user form stealing the binaries form your application and attempting to use it in their own code.

Solution

The solution is fast and easy; make sure you have the "telerik-license.txt" file on your computer in the %appdata%/Telerik folder. We always find it there and automatically use it every time you compile.

Next Steps

Now, that begs the question, why don't you already have it present? We automatically put it there when you install any product. I'm guessing you never installed anything and you're only using source control with our NuGet package references?

Let's manually take care of this in less than 30 seconds:

1. Go to License Keys | Your Account and click "Download License Key"
2. Move the file to %appdata%/Telerik
   • You should now have a file %appdata%/Telerik/telerik-license.txt present
3. Build the project again

If you look at the build output, you will see a section that looks like this:

If you have any trouble, please open a Technical Support Ticket instead of a Forum post. you have Priority Support and will get help quickly (the forums don't have an SLO).

[Kristin]

Now I get Unhandled exception: Unable to load the service index for source https://nuget.telerik.com/v3/index.json.

 

 

[Lance | Senior Manager Technical Support]

Hi Kristin, that is because of missing or bad credentials for the NuGet server. This is the core of advice I provided Camron above, when you first added the NuGet server to your Visual Studio, you saved your credentials in a popup. This gets saved to the Windows Credentials Manager because of how Visual Studio NuGet Manager works, you can see this here => adding-private-nuget-feed#setup-in-visual-studio 

This tutorial takes you though everything you need, regardless of how you're compiling (IDE or CLI) => https://www.telerik.com/products/reporting/documentation/getting-started/installation/adding-private-nuget-feed 

Moving Forward

Unfortunately, I can't really give you precise advice without understanding more about when this happens for you. Is it happening in Visual Studio, VS Code, local PC via CLI, CI/CD? Where/when it happens is very important bcause it tells us the context of what the .NET SDK is doing.

To move forward, please open a support ticket instead of replying here. We will need to ask you to share sensitive info that shouldn't be in a public forum post (and you can leverage your professional support rights with 24hr responses).

1. Go to https://prgress.co/DevToolsSupport
2. Open a ticket for Reporting and ensure you include the following information:
   • When do you get the error? Are you building the project in VS? Is it happening in Azure DevOps or GitHub Actions?
   • Do you have a nuget.config file inside your source code folder (or parent folder)
   • How did you originally set the credentials?
3. Give them a copy of the %appdata%/NuGet/NuGet.Config file on your PC
4. If the project has its own nuget.config file, also attach that one.
5. If this error happens in CI/CD, give them a copy of your YAML workflow.

Once you submit that case, it will go right into the queues of the Reporting engineering team members. You can also come back here and tell me the ticket ID (it's a 7 digit number), and I will ask the team to prioritize it further.

[Kristin]

Will someone please tell me which "Support Ticket Product Option" I am supposed to select?
For the money we spend, getting help should not be this difficult.

 

[Lance | Senior Manager Technical Support]

Hi Kristin, you just select the product you are using.

While I understand NuGet issues are generally constrained to any .NET product, it's still best if you choose the one that you're actually using, that way you get directly connected to that product's engineering team.

In any case, I do see you have the support ticket open for UI for Blazor, the Blazor team will follow up with you there. I will keep an eye on the ticket to ensure things go smoothly and hop in to offer any additional context for the team.