Troubleshoot floating IPs

Cause

The order waits for its invoice, the hold on its address has expired, or we could not assign the address. The Status column says which, and an error shows under it when the last attempt failed.

Fix

For Awaiting payment, select Open invoice and pay it. We cancel an order whose invoice is still unpaid after two days, by default. For Hold expired, cancel the order and place a new one. If an error stays under a paid order, contact support. Follow the order explains each status.

Cause

The floating IP's service is not active. Its first invoice is unpaid, or we suspended it.

Fix

Pay the open invoice from the Orders tab or the floating IP's Billing tab. A suspension also detaches the floating IP, so attach it again after you pay.

Cause

The address is attached to another target, the server already has a floating IP, the floating IP is suspended, or every host of the subnet is in use. The message under the form names the cause.

Fix

Follow the entry for that message in Attach and detach a floating IP.

Cause

An instance sets up its addresses when it starts, so a new address does nothing until the instance restarts from the dashboard. On a server, the message after attaching may say the address applies when the server next starts. A firewall inside the machine, or a DDoS Shield rule, can also drop the traffic.

Fix

Restart the instance from its header, as Start, stop and restart an instance describes, or restart the server. Check that the firewall inside the machine allows the port. Then check the address's Shield tab, as the next entry describes.

Cause

A rule matches the traffic, or When no rule matches is Drop and no Allow rule names it. A rule with a prefix that has no length, or with a port in the second box alone, matches everything. In the Standard and Custom modes, only TCP, UDP and ICMP reach the address.

Fix

Open the address's Shield tab and correct the rules, as Change a floating IP's DDoS protection describes. The Events tab of DDoS Shield shows attacks on your addresses.

Cause

Resolvers still hold the old answer, or we do not host the reverse zone that covers the address. A hostname whose A record points elsewhere also fails the check mail servers make.

Fix

Ask our nameserver directly with dig -x 203.0.113.10 @ns1.coritan.com +short, and follow Set reverse DNS for a floating IP for what the answer means.

Cause

We suspended it, usually for an unpaid invoice, which detaches it. An instance or server that ends also leaves the floating IPs attached to it detached, and they stay on your account.

Fix

Pay the open invoice if there is one, then attach the floating IP again.

Cause

The IPv4 address that comes with a Cloud Compute instance ends with the instance, even when you attached it somewhere else.

Fix

You cannot get the address back. For an address that must outlast an instance, order a floating IP on its own and attach it to the instance.

Cause

A single address costs nothing only while it is an instance's primary address. It was detached, moved to a server, or replaced as primary by another address.

Fix

Make it the primary address of an instance again, or cancel it if you no longer need it. What a floating IP costs has the rules.

Contact support with the floating IP's address and its Service ID, which the Overview and Billing tabs show. For problems inside an instance, see Troubleshoot instances.