License Error After Deploying New Container in Azure Container Apps #9615

5 Answer(s)

• 

  0

  AI-Bot created one month ago

  Support Team ABP Agent

  • The error [ABP-LIC-0020 - License code not found!] indicates that the application cannot read the AbpLicenseCode from your configuration at runtime, even if it is present in your appsettings.secrets.json.

  To resolve this in Azure Container Apps, follow these steps:

  1. Verify Environment Variable Injection
     Azure Container Apps may not automatically use appsettings.secrets.json. Instead, ensure the license code is injected as an environment variable:

     • Set an environment variable named AbpLicenseCode with your license value in the Azure Container App configuration.

  2. Check File Mounting and Build Artifacts

     • Confirm that appsettings.secrets.json is present in the container at runtime. Sometimes, build or deployment steps may exclude this file.
     • You can exec into a running container and check the file's presence and content.

  3. Configuration Precedence

     • Environment variables take precedence over configuration files. If both are set, the environment variable will be used.

  4. Restart All Containers

     • After updating environment variables or configuration, restart all containers to ensure the new settings are loaded.

  5. Check for Typographical Errors

     • Ensure the key is exactly AbpLicenseCode (case-sensitive).

  6. Review Application Logs

     • Check for any configuration loading errors or warnings in the logs that might indicate why the license code is not being read.

  Example: Setting Environment Variable in Azure Portal

  • Go to your Azure Container App > Settings > Environment variables.
  • Add:

  Name: AbpLicenseCode Value:

  - Save and restart the container.
  
  This approach is recommended and resolves most license code loading issues in containerized ABP deployments.
  
  Sources:
  - https://abp.io/support/questions/6663
  - https://abp.io/support/questions/9263
  - https://abp.io/QA/Questions/245/ABP-LIC-0008---License-check-failed-for-'XXXXX'
  
  ---
  _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._
  

  Save Cancel
• 

  0

  abodur created one month ago

  As mentioned in my initial message, I also restarted a previously running container that was working fine before, and it now shows the same license error. This suggests that the issue is not related to the current container’s configuration or contents.

  Is there anything else that could be causing this problem, possibly on the ABP license validation service side?

  Save Cancel
• 

  0

  maliming created one month ago

  Support Team Fullstack Developer

  hi

  I have already checked the appsettings.secrets.json file, and the AbpLicenseCode key is present with the correct value.

  Does the appsettings.secrets.json file exist in the Container? Can you try to move the AbpLicenseCode from appsettings.secrets.json to appsettings.json?

  Thanks.

  Save Cancel
• 

  0

  abodur created one month ago

  It turns out the root cause was that the JSON configuration files (including appsettings.json and appsettings.secrets.json) were not being copied into the container during deployment. What confused me was that even previously working containers started giving the same license error after a restart. Since it’s not possible to check the container content before it starts, I couldn’t verify whether the appsettings files were present or not.

  After adding the license as an environment variable, the container started successfully. This helped me realize the JSON files were missing. Once I fixed the deployment pipeline to include these files, the issue was resolved.

  Thank you for your support.

  Save Cancel
• 

  0

  maliming created one month ago

  Support Team Fullstack Developer

  Great

  Save Cancel