Hello ABP Support Team,
I am facing an issue with my ABP Commercial subscription and license management:
Issue:
I do not see any valid licenses under my ABP Commercial account
→ Licenses section.
When I try to build/run my solution, I encounter license validation errors.
Error Logs:
2025-09-11 18:55:06.766 +05:30 [ERR] ABP-LIC-0017 - License code is not valid: API Key
2025-09-11 18:55:06.766 +05:30 [ERR] ABP-LIC-0017 - License code is not valid: API Key
2025-09-11 18:55:06.779 +05:30 [ERR] ABP-LIC-ERROR - License check failed for 'Volo.FileManagement.HttpApi-v8.3.1.0'.
What I tried so far:
Checked my nuget.config setup.
Verified package sources are pointing to https://nuget.abp.io/....
Confirmed API key entry in <packageSourceCredentials>.
Cleaned cache (dotnet nuget locals all --clear) and retried.
Request:
Could you please help me with the following:
Why I don’t see any licenses under my account dashboard?
How to generate the correct license code/API key for ABP Commercial packages (e.g., Volo.FileManagement.HttpApi-v8.3.1.0).
Steps to fix the ABP-LIC-0017 error so my solution builds successfully.
Environment Details:
ABP Framework version: v8.3.1
.NET SDK: 8
OS: (Windows)
Thanks in advance for your support!
3 Answer(s)
-
0
The error
ABP-LIC-0017 - License code is not valid: API Key
and the absence of licenses in your ABP Commercial account dashboard indicate that your account does not currently have an active or valid ABP Commercial license assigned.For ABP Commercial packages (such as
Volo.FileManagement.HttpApi-v8.3.1.0
), you must have a valid commercial license. The license code (API key) is unique to your organization and project, and is not the same as the NuGet package source API key.The NuGet package source API key (used in
<packageSourceCredentials>
) is only for downloading packages from the ABP Commercial NuGet server. It does not activate or validate your runtime license.The runtime license code (
AbpLicenseCode
) must be set in your application's configuration (e.g.,appsettings.json
or as an environment variable) and must match the license assigned to your organization/project.
How to resolve:
Check Your License Status
- Log in to your ABP Commercial account at https://abp.io/my-organizations.
- Go to the "Licenses" section. If you do not see any valid licenses, your subscription may have expired, or you may not have been assigned a license by your organization admin.
Obtain a Valid License Code
- If you are the license owner, ensure your subscription is active.
- If you are part of an organization, ask your organization admin to assign a license seat to your user.
- Once assigned, you will see the license in your dashboard and can copy the
AbpLicenseCode
for use in your project.
Configure the License Code
- Add the
AbpLicenseCode
to your application'sappsettings.json
or as an environment variable. - Example:
- Add the
{ "AbpLicenseCode": "YOUR-LICENSE-CODE-HERE" }
- Restart your application after updating the license code.
- Troubleshooting
- If you recently purchased or renewed a license, log out and log in again to refresh your license status.
- If you still do not see a license, contact ABP Commercial support at license@abp.io with your account details.
Summary of Steps to Fix ABP-LIC-0017:
- Ensure you have an active ABP Commercial license assigned to your user.
- Use the correct
AbpLicenseCode
in your application configuration. - The NuGet API key is only for package download, not for runtime license validation.
Sources:
- https://abp.io/support/questions/3931
- https://abp.io/docs/latest/others/free-licenses-vs-pro-licenses
This response was generated by AI. If it didn’t solve your problem, feel free to post a new answer — our support team will jump in to help you soon.
-
0
-
0
hi
When I try to build/run my solution, I encounter license validation errors.
Was this project created recently?
Can you check the
appsettings.secret.json
file under the project?It should contain the
AbpLicenseCode
.Can you try to create a new project and copy the
AbpLicenseCode
from the new project to your old project?Can you also run the new project to test if the license check works?
Thanks.