Open Closed

ABP-LIC-ERROR with a new license code on ABP 8.1.1 ("You need to log in using abp login") #10959


User avatar
0
webking-abp1 created

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:

  1. The AbpLicenseCode that has been in the application since March 2024 (an older code).
  2. A new AbpLicenseCode, generated on 2026-11-17 by creating a new Pro solution with ABP Studio CLI 3.1.6 (abp login --device, then abp new ... -t app-pro) with the account webking-abp1. The code is passed to the app as the AbpLicenseCode environment 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:

  1. 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)?
  2. Why does the message ask for abp login when AbpLicenseCode is set? Does version 8.1.1 also need a login token on the machine?
  3. Is anything else needed for the license to cover these packages (developer seat, organization setting)?
  4. 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!

Markdown supported.
Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)

1 Answer(s)
  • User Avatar
    0
    AI-Bot created
    Support Team ABP Agent
    • 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 if AbpLicenseCode is 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=Release
    

    This exact fix is confirmed by ABP support in a very similar “AbpLicenseCode is set but still asks for abp login” scenario (Azure container): once ASPNETCORE_ENVIRONMENT was set to Release, 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.bin or ABP CLI login on that machine

    ABP support’s guidance (again confirmed in the same thread) is:

    • If you run in Debug/Development, you must either:
      • Copy AbpLicense.bin from 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)

    This is why the message mentions abp login even when AbpLicenseCode exists: 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 produced AbpLicense.bin into 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.bin approach or abp login on 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.bin or abp login for 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)
Boost Your Development
ABP Live Training
Packages
See Trainings
Mastering ABP Framework Book
The Official Guide
Mastering
ABP Framework
Learn More
Mastering ABP Framework Book
Made with ❤️ on ABP v10.8.0-preview. Updated on November 16, 2026, 06:26
1
ABP Assistant
🔐 You need to be logged in to use the chatbot. Please log in first.