Skip to main content

Floating IP — Troubleshooting

1. Cannot ping the public IP address after a successful association​

Symptom: The Floating IP has changed to Active status and the Private IP column shows the correct internal address, but pinging the Public IP from the internet receives no response.

Common cause: The Security Group attached to the Instance has no rule permitting ICMP (ping) traffic or the required protocol/port from external sources.

Resolution:

  1. Go to the Security Groups management page of the VPC (Network → Security Groups).
  2. Select the Security Group applied to the target Instance.
  3. Check the Inbound rules section:
    • To allow ping: add a rule with Protocol = ICMP, Direction = Ingress, CIDR = 0.0.0.0/0 (or restrict to a specific source IP).
    • To allow SSH: add a rule for TCP port 22.
    • To allow HTTP/HTTPS: add a rule for TCP port 80 / 443.
  4. Save and try pinging again.

Traffic passing through a Floating IP is still subject to Security Group rules. The Floating IP only performs NAT; allowing or blocking traffic is determined by the Security Group.

2. Floating IP remains in "Down" status after performing Associate​

Symptom: The Associate action was performed and confirmed successfully, but the IP status column still shows Down and the Private IP column is still empty.

Possible causes:

  • The operation is being processed asynchronously and has not completed yet.
  • An internal error occurred during the association but the interface has not yet displayed the Error status.

Resolution:

  1. Wait 30–60 seconds, then reload the page (F5 or the browser refresh button).
  2. If the status is still Down after 2–3 minutes, check whether the Instance is running normally (the Instance must be in Active/Running status).
  3. Try performing Disassociate and then Associate again.
  4. If the status changes to Error, contact technical support and provide the Public IP address and the time at which the operation was performed.

3. Cannot release (Release) a Floating IP​

Symptom: The Release option is hidden or disabled in the Actions menu, or clicking Release returns an error message.

Cause: The Floating IP is in Active status — meaning it is still associated with an Instance. The system does not allow releasing an IP while an active association exists.

Resolution:

  1. Confirm that the IP status column shows Active and that the Port / Private IP columns have values.
  2. Click the Actions menu → select Disassociate to detach the IP from the Instance.
  3. Wait for the status to return to Down.
  4. Click the Actions menu again → select Release to release the IP.

Warning: After releasing, the IP address is reclaimed and the original address cannot be recovered. Make sure you no longer need this address before proceeding.

4. The "Allocate IP address" button is greyed out and cannot be clicked​

Symptom: The Allocate IP address button is visible but cannot be clicked, or hovering over it shows a message related to a limit.

Cause: The organization or project has reached the quota (maximum number) of Floating IPs allowed to be allocated in the VPC or account.

Resolution:

  1. Review the current Floating IP list — check whether any addresses are in Down status and not in use. If so, Release them to free up slots.
  2. If all existing IPs are in use and more are still needed, contact the system administrator or support team to request a Floating IP quota increase.
  3. After the quota is adjusted or unused IPs have been released, reload the page and try again.