Submit Feedback
Legacy Knowledge Base
Published Sep. 10, 2025

Unable to install .cfg file after updating or upgrading to DXP 7.3 Fix Pack 1

Written By

Joel Garman

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

  • When placing a *.cfg file in the LIFERAY_HOME/osgi/configs folder an error is generated in the log:
    Unable to install .cfg file "{cfg-file-name}", please use .config file instead.
  • Files with the *.cfg extension placed in the LIFERAY_HOME/osgi/configs folder are not read.

Environment

  • Liferay DXP 7.3 Fix Pack 1 / Service Pack 1 and Above

Resolution

Liferay DXP 7.3 Fix Pack 1 contains LPS-118855 which removes the cfg file support by default. In order to continue to manage module settings either:

  1. Reformat all *.cfg files to *.config files.
  2. In a portal-ext.properties file set module.framework.file.install.enable.cfg=true to enable processing of the legacy *.cfg file format.

 

Additional Information

  • LPS-118855 was implemented as a consequence of removing Apache Felix File Install OSGi management agent.  The Apache Felix File Install libraries were removed in order to mitigate security vulnerabilities in the third-party library.

 

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