Our organization (Webking / Activator, Business license, valid until January 13, 2027) runs an application on ABP Commercial 8.1.1 (MongoDB, Identity.Pro, Account.Pro, OpenIddict.Pro, Saas, LanguageManagement, TextTemplateManagement, Gdpr, LeptonX).
The application stops at startup with:
ABP-LIC-ERROR - License check failed for 'Volo.Abp.Identity.Pro.HttpApi-v8.1.1.0'. You need to log in using the command 'abp login <username>'. For more information, contact to license@abp.io.
What we tried:
- The
AbpLicenseCodethat has been in the application since March 2024 (an older code). - A new
AbpLicenseCode, generated on 2026-11-17 by creating a new Pro solution with ABP Studio CLI 3.1.6 (abp login --device, thenabp new ... -t app-pro) with the account webking-abp1. The code is passed to the app as theAbpLicenseCodeenvironment variable (the length is correct, 1536 characters, and no other source overrides it). The same error appears.
The app runs in a Linux container (dotnet sdk 8.0). The network is open to the internet.
Questions:
- Is a license code generated by the new CLI (ABP 10 template) accepted by packages in version 8.1.1, or do we need a code generated with a CLI/template version that matches 8.1.1 (for example Volo.Abp.Cli 8.x)?
- Why does the message ask for
abp loginwhenAbpLicenseCodeis set? Does version 8.1.1 also need a login token on the machine? - Is anything else needed for the license to cover these packages (developer seat, organization setting)?
- Is there a supported way to get a working code for 8.1.1 for the remaining months of our license, while we move away from the commercial modules?
Thank you!
1 Answer(s)
-
0
- Your issue is not about “template/CLI major version compatibility” of the
AbpLicenseCode. A license code generated today should still be accepted by older commercial packages (like 8.1.1) as long as the runtime licensing mechanism can validate it in that environment. - In your case, the error text “You need to log in using
abp login” typically appears when the app can’t find a valid runtime license file/session for that machine/environment, even ifAbpLicenseCodeis set.
Do the following (this is the supported/known resolution path for containers & servers):
1) Run the app in Release mode in the container
ABP Commercial licensing behaves differently depending on environment/build configuration. For server/container deployments, Release is the expected mode.
In container env vars, set (example):
ASPNETCORE_ENVIRONMENT=Release DOTNET_ENVIRONMENT=ReleaseThis exact fix is confirmed by ABP support in a very similar “
AbpLicenseCodeis set but still asks forabp login” scenario (Azure container): onceASPNETCORE_ENVIRONMENTwas set toRelease, it worked.
So first, make sure you are not effectively running in Development/Debug in the container.2) If you must run as Development/Debug in that container: you need
AbpLicense.binor ABP CLI login on that machineABP support’s guidance (again confirmed in the same thread) is:
- If you run in Debug/Development, you must either:
- Copy
AbpLicense.binfrom a machine where you have logged in successfully, or - Run
abp login <username>on the server/container environment (so it can create the local license/session file)
- Copy
This is why the message mentions
abp logineven whenAbpLicenseCodeexists: in Development/Debug scenarios, ABP may require the local license file/session (AbpLicense.bin) rather than relying only on the code.Practical container approach (supported conceptually):
- Login on a dev machine once (
abp login ...) and then mount/copy the producedAbpLicense.bininto the container image/runtime (location depends on the user profile inside the container), or login inside the container during build/startup (be careful with secrets).
Also note ABP support’s warning: logging in on a different computer can be counted as a new development computer (seat/device implications).
3) Seats / organization setting
Nothing in the verified sources indicates you need extra module-specific toggles for packages like
Volo.Abp.Identity.Pro.*beyond having an active commercial license and a valid runtime validation method for the environment (Release vs Development/Debug, license file/session availability). Most “ABP-LIC-ERROR … need to log in” cases end up being environment/runtime validation (Release vs Debug +AbpLicense.bin/login), not missing module entitlements.4) Supported way to keep 8.1.1 running while you transition away
Yes:
- Run the container in Release (recommended).
- If you need a Dev/Test deployment in Development environment, use the
AbpLicense.binapproach orabp loginon that environment.
If you still can’t get it working after switching to Release, that becomes account/license-server-side and should be handled by ABP directly.
Sources
- ABP support thread confirming Release env fix + explaining need for
AbpLicense.binorabp loginfor Debug/Development: https://abp.io/support/questions/9640 - Related containerizing discussion referenced by ABP support: https://abp.io/support/questions/1471
- ABP CLI documentation (for
abp login): https://abp.io/docs/latest/cli - If it turns out to be license/account-side, contact: https://abp.io/contact
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.
Markdown supported.Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post) - Your issue is not about “template/CLI major version compatibility” of the