Legacy Knowledge Base
Published Jul. 2, 2025

Blocking IPs in Liferay Cloud

Written By

Matheus Monteiro

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

  • You do not want a specific IP (or a range of IP addresses) to access your websites in Liferay Cloud.

Environment

  • Liferay PaaS

Resolution

  • You need to go to /webserver/configs/common/conf.d and edit the liferay.conf file (you can create another .conf file instead if you prefer), adding the following:
location / {
deny aaa.bbb.ccc.ddd;
}

 

Where aaa.bbb.ccc.ddd is the IP address you want to block.

  • The default nginx.conf has a directive include /etc/nginx/conf.d/*.conf; which will automatically load any .conf files in /webserver/configs/{ENV}/conf.d. If you haven't removed such directive you can simply deploy a new file, like blacklist.conf in that folder with contents like below:
deny 200.248.134.2;
deny 192.168.1.0/24;
  • You can deny multiple IP address by adding multiple lines of "deny" or use the CIDR notation to specify a range of IP addresses.
Did this article resolve your issue ?

Legacy Knowledge Base