Troubleshooting

New to Telerik UI for Blazor? Download free 30-day trial

Telerik NuGet Feed Troubleshooting

This article summarizes the issues that may occur when you work with the Telerik UI for Blazor library and the online Telerik NuGet feed, and their solutions.

Regardless of the cause for the issue, it is recommended that you start from the section on the commonly occurring issues.

Telerik NuGet Feed Status

Visit status.telerik.com to check the status of the Telerik NuGet server. The top section shows manually logged incidents with possible updates or workaround suggestions. The System Metrics section provides real-time automated diagnostics.

Tips for Handling Common NuGet Issues

The most common reasons for issues with the private Telerik NuGet feed are related to:

  • Authentication and credentials.
  • Licensing. For example, requesting commercial packages with a trial license or vice-versa.
  • Missing or wrong local configuration (NuGet.Config).
  • Network connectivity issues, including proxies and firewalls.

Errors like Unable to load the service index for source https://nuget.telerik.com/v3/index.json don't indicate the exact cause of the problem. In such cases, check the additional error information which usually provides an error code.

To verify if you can access the Telerik NuGet server and the expected packages, open the https://nuget.telerik.com/v3/search?q=blazor&prerelease=true&skip=0&take=100&semVerLevel=2.0.0 URL directly in the web browser and enter your Telerik credentials in the prompt.

As a result, you will see a JSON output with the NuGet packages and versions that are available for you. Depending on your license, search for Telerik.UI.for.Blazor or Telerik.UI.for.Blazor.Trial.

If the above URL doesn't open, you have either come across a local networking issue or the NuGet server is down.

If you can access the feed in the browser, but you do not see the packages in Visual Studio, most likely the problem is caused by entering wrong credentials or using a different Telerik account. Make sure your saved credentials are correct. Also, you must not have a NuGet.Config file in your project as it may bring in invalid credentials and project-level configuration files override the global ones.

Removing Saved Credentials

If you suspect that your saved credentials are wrong, use the following steps to remove them from Windows and, then, add the correct ones:

  1. Remove the saved credentials in the Windows Credential Manager. These credentials will appear as nuget.telerik.com or VSCredentials_nuget.telerik.com entries.
  2. Remove the Telerik NuGet package source from Visual Studio.
  3. If you have added the Telerik package source by NuGet CLI, try to remove it from the CLI by running the following commands:
  4. Check if you have any credentials stored in %AppData%\NuGet\Nuget.Config. If so, remove them.
  5. Try to reset the Visual Studio user data by forcing NuGet to ask for authentication.
  6. Restart Visual Studio.
  7. Enter the Telerik NuGet package source again through Visual Studio or CLI. If you are using the feed in a .NET Core application, store your credentials as plain text.

Error 401 Unauthorized

If your credentials are correct and your license includes the requested product and version, then the password probably contains special characters. You need to escape these characters or the authentication can fail on the NuGet server. For example, a common character you must escape is the ampersand (&); however, the character causing the issue may be as unique as the section character (§).

To solve the issue:

  1. Change the password so that it doesn't include characters you need to escape.
  2. Escape the special characters before storing the credentials. For example, my§uper&P@§§word encodes to my§uper&P@§§word.

Avoid using an online encoder utility for a password. Instead, use a Powershell command:

Add-Type -AssemblyName System.Web
[System.Web.HttpUtility]::HtmlEncode('my§uper&P@§§word')

Powershell Encoding

Unable to Find Package

If the error occurs for the Telerik.UI.for.Blazor package, it may look like this:

error NU1101: Unable to find package Telerik.UI.for.Blazor. No packages exist with this id in source(s): nuget.org

Such an error implies that the Telerik NuGet source is not added or enabled. The possible causes are:

  • Missing Telerik NuGet source configuration in the NuGet.Config file.
  • The correct NuGet.Config file is not used, because it is missing or misplaced.

If the error occurs in a Docker scenario, the solution is to copy the NuGet.Config file (or configure the NuGet source) explicitly during the Docker image build. You can also reference the NuGet.Config file path explicitly in the dotnet restore command. For more information, see the Docker section in the deployment documentation and the private NuGet feeds in Docker forum thread.

If the error occurs for the Telerik.FontIcons and Telerik.SvgIcons icon packages, the NuGet client is not using nuget.org as a NuGet source. The possible causes are:

  • The nuget.org source is disabled.
  • There is packageSourceMapping, which forces the NuGet client to search for the icon packages in the nuget.telerik.com source. However, the icon packages are published on nuget.org.

Error 503 Service Unavailable

If you get a message like Unable to load the service index for source and error 503 (Service unavailable), check the Telerik NuGet server health at the Telerik live services status page.

In urgent cases, download the NuGet packages from your Telerik Account Downloads page. Then, set up a local NuGet feed.

Package Version Not Found

You may encounter an error similar to:

ProjectName depends on Telerik.UI.for.Blazor (>= 5.1.1) but Telerik.UI.for.Blazor 5.1.1 was not found. An approximate best match of Telerik.UI.for.Blazor 6.0.2 was resolved.

or

error NU1102: Unable to find package Telerik.UI.for.Blazor with version (>= 5.1.1)

This error means that version 5.1.1 is outside the subscription period of your license.

To solve the issue, use a different version or ask the license holder at your company to assign you another license that includes the desired product version.

Unable to Resolve Package due to PackageSourceMapping

Incorrect package source mapping can result in errors similar to:

NU1100 Unable to resolve 'Telerik... (>= ...)' for 'net...'. PackageSourceMapping is enabled, the following source(s) were not considered: ...

The solution is to check the Package Source Mapping settings in Visual Studio, or review all applicable NuGet.Config files on the machine. Then, adjust the package source mapping configuration.

Failed to Retrieve Information from Remote Source

An attempt to use the obsolete Telerik NuGet v2 feed after November 2024 will result in an error:

Failed to retrieve information about 'Telerik.UI.for.Blazor' from remote source 'https://nuget.telerik.com/nuget/FindPackagesById()?id='Telerik.UI.for.Blazor'&semVerLevel=2.0.0'.

The solution is to use the Telerik NuGet v3 feed.

Another possible reason for the same error is an incorrect NuGet feed URL.

See Also

In this article
Related articles
Not finding the help you need? Improve this article