Floating IPs in xneelo Cloud

This is a new feature; try it at no charge and share your feedback via Live Chat. Learn more

A floating IP is a public IP address you can allocate to your project and dynamically assign to any instance. It makes the instance reachable from the internet while keeping private networks secure.

Floating IPs are charged at a rate per hour – see our cloud pricing and pricing rules.

Read on to learn what a floating IP is, when to use one, and how to allocate, associate, and release floating IPs in your cloud project.


  • What is a floating IP?

    A floating IP is a public IP address that you can allocate to your project.

    You can assign (associate) a floating IP to any instance or network port, and disassociate it at any time. 

    Floating IPs are typically assigned to instances to provide internet access. Floating IPs can also be attached to router ports, but this is only recommended for advanced networking setups.





  • When to use a floating IP

    Floating IPs are most often used to give instances on a private network internet access. They can also be reassigned between resources without changing DNS records.

    A floating IP can only be associated with an instance or network port that is attached to a private network.

    Floating IPs are useful when you need to:

    • Expose a web server or API to the internet.
    • Provide remote admin access (via SSH/RDP) through a public IP.
    • Move a public IP between instances during failover or maintenance.
    • Assign a stable public IP for partners or external services to allowlist.





  • Allocate a floating IP to your project

    Before you can use a floating IP, you need to allocate one from the public pool. 

    Note: The floating IP will be charged for the duration it is allocated to your project.

    STEPS

    1. 1
      In the Cloud dashboard, go to Network > Floating IPs.
    2. 2
      Select the Allocate IP to Project button.
    3. 3
      Provide a clear description for easy identification later.
    4. 4
      Select Allocate IP to confirm.

    The new floating IP will appear in your list, ready to be associated.





  • Associate a floating IP to an instance

    You can link a floating IP to an available interface (port) of an instance on a private network.

    A floating IP can only be attached to a single port.

    See more on interfaces on cloud instances. 

    Note: Only ports with an IP on a private network can be associated.

    STEPS

    1. 1
      In the Cloud dashboard, go to Network > Floating IPs.
    2. 2
      Find the floating IP in the table.
    3. 3
      In the Actions column, select Associate.
    4. 4
      Choose the floating IP and interface (port) you want to associate it to.
    5. 5
      Select Associate to confirm.

    Note: Make sure the security groups for that interface allow inbound traffic (e.g. port 80/443 for a web server, port 22 for SSH).





  • Disassociate a floating IP from an instance

    You can remove the association between a floating IP and an instance interface without deleting the IP.

    STEPS

    1. 1
      In the Cloud dashboard, go to Network > Floating IPs.
    2. 2
      Find the floating IP and select Disassociate.
    3. 3
      Select Disassociate to confirm.

    The floating IP will remain allocated to your project but won’t be linked to any interface.





  • Release a floating IP from your project

    If you no longer need a floating IP, you can release it back to the pool. The IP will be removed from your project, and will no longer be charged.

    STEPS

    1. 1
      In the Cloud dashboard, go to Network > Floating IPs.
    2. 2
      Find the floating IP and select Release.
    3. 3
      Select Release Floating IP to confirm.





  • Troubleshoot floating IP connectivity

    If a floating IP is not reachable:

    • Check that it’s associated with the correct instance interface.
    • Verify the interface is on a private network with a router connected to the external network.
    • Confirm the correct security group rules allow inbound traffic on attached instance or port.
    • Ensure the instance operating system has the vNIC configured with the right IP.

    Test connectivity from outside your network (e.g. ping or curl).



Related Posts: