Submit Feedback
Legacy Knowledge Base
Published Sep. 10, 2025

After upgrading to stack v4, the portal shows the message "This server has not been activated with Liferay Connected Services"

Written By

Alfonso Crisci

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.
Note: please note that Liferay has renamed its Liferay Experience Could offerings to Liferay SaaS (formerly LXC) and Liferay PaaS (formerly LXC-SM).

Issue

  • After upgrading to stack v4, the portal shows the message "This server has not been activated with Liferay Connected Services" on the login page.

  • The build logs show:

    build-5278 [liferay-abc-xyz] [dxp] ERROR [fileinstall-/opt/liferay/osgi/modules][LicenseManager:?] Unable to register license
    build-5278 [liferay-abc-xyz] java.io.FileNotFoundException: /opt/liferay/data/license/DXPCloudInternal_DigitalEnterpriseUnlimitedEnterpriseWide_enterprise.li (Permission denied)

Environment

  • Liferay SaaS stack v4

Resolution

  1. Remove the compatibility variables LCP_BACKUP_VOLUME_UID and LCP_BACKUP_VOLUME_GID from the LCP.json file of the backup service.
  2. On the Cloud user interface, remove the backup service from the affected environment.
  3. On the affected environment, do a new deployment with the changes from step 1.
  4. Restart the liferay service.

Additional Information

  • Root cause: the /opt/liferay/data folder still uses the v3's owner:group (999:999 instead of v4's 1000:1000).

 

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