Hi,
Is there a problem with nuget.abp.io?
Recently our Azure DevOps builds are failing when attempting to install the cli and/or when attempting to install nuget packages,
Here is the script to install the CLI:
dotnet tool install -g Volo.Abp.Studio.Cli
It fails with the following error:
Response status code does not indicate success: 403 (Forbidden).
Similarly, when attempting to install nuget packages:
Determining projects to restore...
Retrying 'FindPackagesByIdAsync' for source 'https://nuget.abp.io/ {{redacted}} /v3/package/volo.abp.users.abstractions/index.json'.
Response status code does not indicate success: 403 (Forbidden).
Regards,
Lucian
2 Answer(s)
-
0
Hi, the package
Volo.Abp.Users.Abstractionsis not in our NuGet Server, instead, it's an open-source package and stored in the nuget.org (https://www.nuget.org/packages/Volo.Abp.Users.Abstractions/9.2.0-rc.1). Therefore, it's normal to get this error message because this is how NuGet package system works, it tries to get the related packages from the defined package-sources (checks the relevant packages in all package sources with a fallback mechanism).So, in your case, probably there is a problem between these two:
1-) You might be not logged in through ABP CLI: This might be the reason, because it gives a 403 error. To check it you can run the
abp login-infocommand in your terminal and ensure you are logged in or not:abp login-infowith this command, you should be able to see the logged-in user details, including your OrganizationName:
If you don't see the relevant information, then it means that you are not logged in via ABP CLI and should log in with the following command:
abp login <username> -p <password> -o <organization-name>2-) Wrong
packageSourceMappingin NuGet.config file: This might also be the reason and it would be better to check the NuGet.config file in your solution, especially you can check your api-key andpackageSourceMappingsection (if it exists)
After you checked these two solutions, if you are still unable to fix the problem, then please let me know.
Regards.
-
0
Hi, the package
Volo.Abp.Users.Abstractionsis not in our NuGet Server, instead, it's an open-source package and stored in the nuget.org (https://www.nuget.org/packages/Volo.Abp.Users.Abstractions/9.2.0-rc.1). Therefore, it's normal to get this error message because this is how NuGet package system works, it tries to get the related packages from the defined package-sources (checks the relevant packages in all package sources with a fallback mechanism).So, in your case, probably there is a problem between these two:
1-) You might be not logged in through ABP CLI: This might be the reason, because it gives a 403 error. To check it you can run the
abp login-infocommand in your terminal and ensure you are logged in or not:abp login-infowith this command, you should be able to see the logged-in user details, including your OrganizationName:
If you don't see the relevant information, then it means that you are not logged in via ABP CLI and should log in with the following command:
abp login <username> -p <password> -o <organization-name>2-) Wrong
packageSourceMappingin NuGet.config file: This might also be the reason and it would be better to check the NuGet.config file in your solution, especially you can check your api-key andpackageSourceMappingsection (if it exists)
After you checked these two solutions, if you are still unable to fix the problem, then please let me know.
Regards.
Hi,
This was working until recently.
The first problem is that the CLI does not install successfully in the build agent.Then the second problem, that Volo.Abp.Users.Abstractions
Regards,
Lucian Appels.
