Submit Feedback
Legacy Knowledge Base
Published Sep. 10, 2025

Glowroot page broken using a custom portal context

Written By

Daniel Mijarra

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

  • If we define a context other than ROOT in our portal, for example myportal, the Glowroot administration pages are not displayed or are displayed with visual errors.

Environment

  • Liferay DXP 2023.Q4

Resolution

  • Currently, to use Glowroot with a custom context other than ROOT, it is necessary to apply these settings:

    • Edit $LIFERAY_HOME/glowroot/admin.json and specify the contextPath:
      ...
      "web": {
          "port": 4000,
          "bindAddress": "127.0.0.1",
          "contextPath": "/myportal/o/glowroot",
          "sessionTimeoutMinutes": 30,
          "sessionCookieName": "GLOWROOT_SESSION_ID"
      },
      ...

    • Inside $LIFERAY_HOME/osgi/configs, it is necessary to add the configuration file com.liferay.glowroot.proxy.internal.servlet.GlowrootProxyServlet.config indicating the contextPath (it will be necessary to restart the server for the configuration to take effect), as an example:

      servlet.init.targetUri="http://localhost:4000/myportal/o/glowroot"

Additional Information

 

 

 

 

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