Submit Feedback
Legacy Knowledge Base
Published Jun. 30, 2025

DXP 7.0 License not activated after deployment

Written By

Dia Seung

How To articles are not official guidelines or officially supported documentation. They are community-contributed content and may not always reflect the latest updates to Liferay DXP. We welcome your feedback to improve How To articles!

While we make every effort to ensure this Knowledge Base is accurate, it may not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with any feedback or concerns.

Legacy Article

You are viewing an article from our legacy "FastTrack" publication program, made available for informational purposes. Articles in this program were published without a requirement for independent editing or verification and are provided"as is" without guarantee.

Before using any information from this article, independently verify its suitability for your situation and project.

Issue

  • After deploying the provisioned Liferay license, the Liferay bundle license is not activated and "This instance is not registered." error is thrown. 
  • After going through the Activation Key Troubleshooting Guide, still having issues with the license.

Environment

  • DXP 7.0

Resolution

  • Verify that the license .xml file is copied to the Liferay deploy directory retaining its user:group ownership as liferay:liferay. 

  • Copy the license .xml file to the Liferay home directory, changing ownership of the file to liferay user and group while it was in the liferay user's home directory /usr/local/liferay/, changing permissions ('chmod 660' or higher), and then copying the file into the deploy directory as liferay user.

  • It was important to copy the file as liferay user, not as the root user, as copying into the deploy directory as root would cause the ownership of the license file to change from liferay:liferay to root:root and ultimately causes activation to fail. 

Additional Information

Did this article resolve your issue ?
Legacy Knowledge Base
Did this article resolve your issue ?