Note: please note that Liferay has renamed its Liferay Experience
Could offerings to Liferay SaaS (formerly LXC) and
Liferay PaaS (formerly LXC-SM).
Issue
- Sometimes it is necessary to connect the Liferay DXP running on the Liferay Cloud with some internal/private system, such as an Active Directory, SMTP etc.
- Due to security reasons, it is common that internal networks have firewalls to prevent unwanted IP address from reaching their systems.
- How do you know from which IP address Liferay DXP will send a request? You can find it here! :-)
Environment
- Liferay Cloud.
Resolution
- It depends on the location of your cluster:
Location Outbound IP address asia-northeast1-p8-c1 (Tokyo) 34.85.61.215 asia-northeast2-p18-c1 (Osaka) 34.97.179.250 asia-south1-c1 (Mumbai) 34.93.211.61 australia-southeast1-c1 (Sydney) 35.244.115.208 europe-north1-t2-c1 (Hamina) 35.228.20.70
europe-north1-p9-c1 (Hamina) 35.228.58.165
europe-west2-p2-c1 (London) 35.246.27.254
europe-west3-c1 (Frankfurt) 35.234.83.7 europe-west3-p6-c1 (Frankfurt) 34.107.19.222 northamerica-northeast1-p7-c1 (Montreal) 34.95.49.93 southamerica-east1-p3-c1 (São Paulo) 34.95.213.33 us-east4-t1-c1 (Virginia, cluster specific to trial accounts) 34.86.185.18 us-central1-c1 (Iowa) 35.193.23.53 us-west1-p1-c1 (Oregon) 35.203.178.209
- If your Liferay SaaS project is hosted on a private cluster, Liferay will not share it's IP publicly. Instead, you can run the following Groovy script under Control Panel > Server Administration > Script:
out.println("curl https://ifconfig.me".execute().text)
- This is to make Liferay DXP's container to establish a connection to the IP identification service https://ifconfig.me, which will then reply with the container IP it received the connection from. (ifconfig.me is a 3rd party service, not affiliated with Liferay).
Additional Information