Knowledge Base
Published Jun. 30, 2025

Troubleshooting Unexpected Open Ports in Liferay PaaS

Written By

Kanchan Bisht

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.

Issue

  • When performing a network scan on a Liferay PaaS environment, ports 80, 443, and others appear to be in open state. Will this allow HTTP requests to be successful? 

Environment

  • Liferay PaaS

Resolution

This behavior is expected and does not represent a security threat. Liferay PaaS projects reside on a shared cluster, meaning firewall rules are shared across all projects on that cluster. The Load Balancer acts as a proxy via the Google Front End (GFE).

To verify your security and routing, follow these steps:

  1. Examine your project's LCP.json files.
  2. Verify that the "external": true setting is only applied to services you explicitly intend to expose.
  3. Confirm that no unexpected services are mapping to these ports.

Additional Information

  • While the firewall rules may show various ports as open (e.g., 8080, 9200), the cluster's routing service will not forward any requests to your specific environment unless you explicitly expose those ports within your configurations.
  • See Google's Open Ports documentation for more information.
Did this article resolve your issue ?

Knowledge Base