[alper] said: Normally it's not suggested to run your production app in Debug mode as it'll run slower. But even if you want to run in Debug mode, you need to add the
AbpLicense.bin
file, which you get from your development computer or log in to ABP at the production server via ABP CLI.
Note that when you log in with your account on a different computer, it'll be counted as your new development computer.you can also check this question
Since our product is still in development and hasn't been officially launched, we need to set up a development or testing environment for team collaboration. In this development environment, we also need to read configuration parameters from other development environments based on environment variables. Therefore, we must set ASPNETCORE_ENVIRONMENT to 'Development'. What approach allows us to deploy such a development/test environment now, and then deploy to production once development is complete?
[alper] said: Set
ASPNETCORE_ENVIRONMENT
toRelease
.
It works now. What should I do if I want to deploy it as Development instead of Release? Do you have any suggestions?
[AI-Bot] said: To resolve the "ABP-LIC-ERROR - License check failed for 'Volo.Abp.AspNetCore.Mvc.UI.Theme.Commercial-v9.2.1.0'" error in Azure App Service, ensure the following:
- AbpLicenseCode Configuration
- The
AbpLicenseCode
must be available to your application at runtime. In Azure App Service, the recommended approach is to set it as an environment variable in the App Service configuration.- Go to your Azure App Service > Configuration > Application settings, and add:
Name: AbpLicenseCode Value:
- Save and restart your App Service. 2. **Check Configuration File Deployment** - If you use `appsettings.json` or `appsettings.secrets.json` to store the license code, ensure these files are actually deployed and present in the running environment. Missing configuration files are a common cause of this error. 3. **Environment Variable Precedence** - Environment variables override values in configuration files. If both are set, the environment variable will be used. 4. **Case Sensitivity** - The key must be exactly `AbpLicenseCode` (case-sensitive). 5. **Restart After Changes** - Always restart your App Service after updating environment variables or configuration files. 6. **Check for Typographical Errors** - Double-check for any typos in the key or value. 7. **Review Application Logs** - Check logs for any configuration loading errors or warnings. These steps resolve most license code loading issues in Azure App Service and containerized ABP deployments. Sources: - https://abp.io/support/questions/6663 - https://abp.io/support/questions/9615 - 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._
I'm sure the AbpLicenseCode is available to my application at runtime, and I have indeed set it as an environment variable in the App Service configuration.
Hello, We have purchased a Business License and used ABP Studio to generate a Layered Application, which we deployed to Azure App Service as our development environment. We are aware that AddDevelopmentEncryptionAndSigningCertificate cannot be used in applications deployed on IIS or Azure App Service. Therefore, we generated an openiddict.pfx certificate and confirmed that AbpLicenseCode is correctly configured as an environment variable. However, after redeployment, the AuthServer still reports the error: "License check failed for 'Volo.Abp.AspNetCore.Mvc.UI.Theme.Commercial-v9.2.1.0'". Could you advise what additional configurations are required to resolve this issue?
2025-07-20T09:17:09.3743695Z [09:17:09 ERR] ABP-LIC-ERROR - License check failed for 'Volo.Abp.AspNetCore.Mvc.UI.Theme.Commercial-v9.2.1.0'.
2025-07-20T09:17:09.3744212Z You need to log in using the command abp login <username>
.
2025-07-20T09:17:09.3744255Z For more information, contact to license@abp.io.