This article provides ways to fix the most common problems we have had reported with the setup of the Telerik Online Private NuGet Feed:
There are two common reasons for the Telerik packages to be missing in the Telerik Online Feed:
There is a network issue. For example, a proxy, firewall or other similar software blocks requests to our server.
Your license is tied to a different account than the one used for the feed credentials.
To check if this is a networking issue, open the following URL in your browser and enter your
You should see an XML result with the list of packages you can access and you should see the
Telerik.UI.for.Blazor package with the version appropriate to your license.
If you can access the feed in the browser, but you do not see the packages in Visual Studio, the most likely problem is wrong credentials that are not associated with a license. Make sure that your credentials are correct and that there isn't a
nuget.config file in the project that is bringing in invalid credentials - project-level config files override the global settings.
I you suspect the credentials are wrong, here is a sample process of removing stored credentials from Windows so you can re-add the correct ones:
- Remove saved credentials in Windows Credential Manager. They will appear as
- Remove the Telerik Nuget package source from Visual Studio.
- If you have added the Telerik package source by nuget CLI, then try to remove it from the CLI:
- Check if there are any credentials stored in
%AppData%\NuGet\Nuget.Configand if so you have to remove them.
- Try to reset Visual Studio user data. You can read how to do that here.
- Restart Visual Studio.
- Enter the Telerik nuget package source again through Visual Studio or CLI. If you are using the feed in .NET Core application, store your credentials as plain text.
If your password contains a special character, those characters need to be escaped or it may fail authentication resulting in Error 401 login failure from the NuGet server. A common character that needs to be escaped is the ampersand
&, but it can be as unique as the section character
- Change the password so that it only includes characters that do not need to be escaped
- Escape the special characters before storing it as server credentials. For example,
We strongly discourage using a online encoder utility for a password. You can use Powershell command instead, here's one example:
Add-Type -AssemblyName System.Web [System.Web.HttpUtility]::HtmlEncode('my§uper&P@§§word')