Why is the public IP of a service changing?
Written By
Alfonso Crisci
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
- Checking the web address for a service, for example
webserver-acme-test--ports.lfr.cloud, administrators may notice an unexpected change in the public IP address.
Resolution
- In your internal architecture, point the devices to the hostname instead.
Additional Information
- The behavior is expected as, according to Google documentation's Ephemeral and static IP addresses, only the
static option will guarantee that the IP won't change. Ephemeral IPs can change if resource attached to it is restarted or deleted.
- Only the Load-balancer can create static IPs, the IPs linked to the URL created through the "ports" tag are of ephemeral type, and can change.
- A new feature to be possibly implemented on new versions will allow Liferay Cloud to handle IPs as static. At the moment of writing this article, there is no confirmation whether such feature will be developed and in case it will, the final date for it to be available to customers is unknown.
Did this article resolve your issue ?