Diagnosing and Resolving Floating IP Connectivity Failures on DigitalOcean

The Problem: Floating IP Unreachability

\n

A Floating IP is a static public IPv4 address that can be reassigned across different Droplets (virtual private servers) within the same region. The most common failure occurs when a Floating IP is successfully assigned in the DigitalOcean Control Panel, but the application on the target Droplet remains unreachable via that IP.

\n

The primary takeaway: Assigning a Floating IP via the dashboard only routes traffic to the Droplet; it does not automatically configure the Droplet's internal network interface to accept that traffic. You must manually configure the OS to recognize the Floating IP as an alias.

\n\n

Diagnostic Matrix

\n\n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n

Symptom	Likely Cause	Diagnostic Tool
Ping fails; SSH via private IP works	Missing OS-level IP configuration	ip addr show
Connection timeout on specific port	Droplet Firewall or UFW blocking port	ufw status
IP assigned to wrong Droplet	Incorrect API association/Manual error	DO Control Panel / API
Intermittent connectivity	IP conflict or overlapping subnet	netstat -tunlp

\n\n

Step-by-Step Connectivity Verification

\n

\n
1. Verify Control Panel Association: Confirm the Floating IP is mapped to the correct Droplet ID in the Networking tab. If the association is missing, the traffic never reaches the hypervisor.
\n
2. Check Internal Interface: Run the following command on the target Droplet (requires sudo permissions):\n

   ip addr show

   \n Check if the Floating IP appears in the output. If you only see the Droplet's primary public IP and private IP, the OS is ignoring the Floating IP traffic.
\n
3. Test Local Port Listening: Ensure the service (e.g., Nginx or Apache) is listening on all interfaces (0.0.0.0) rather than just the localhost (127.0.0.1).\n

   sudo netstat -tunlp | grep :80

   \n
\n
4. Validate Cloud Firewalls: Check the DigitalOcean Cloud Firewall settings. Ensure the rules allow inbound traffic on the required ports for the Floating IP's source range.
\n

\n\n

Fixing the Configuration

\n\n

Scenario A: IP is assigned in Panel but missing in OS

\n

You must add the Floating IP as a secondary address to your primary network interface. For Ubuntu 22.04+ using Netplan, modify your configuration file (usually /etc/netplan/50-cloud-init.yaml).

\n

Configuration Example:

\n

network:\\n  version: 2\\n  ethernets:\\n    eth0:\\n      addresses:\\n        - 123.456.78.90/32 # Your Droplet's primary IP\\n        - 111.222.33.44/32 # Your Floating IP\\n

\n

Run sudo netplan apply to commit changes. Risk: Incorrect indentation in YAML files can disable network connectivity entirely. Always keep a separate SSH session open via the DigitalOcean Console for recovery.

\n\n

Scenario B: Firewall Blocking Traffic

\n

If the IP is configured but unreachable, check the Uncomplicated Firewall (UFW). Run this command on the Droplet:

\n

sudo ufw allow 80/tcp

\n

Verify the result with sudo ufw status.

\n\n

Rollback Procedure

\n

If network connectivity is lost after applying Netplan changes:

\n

\n
1. Access the Droplet via the DigitalOcean Recovery Console.
\n
2. Edit the /etc/netplan/ file to remove the Floating IP line.
\n
3. Run sudo netplan apply to restore the original network state.
\n

\n\n

Escalation Criteria

\n

Contact DigitalOcean Support if:

\n

\n
• The Floating IP is associated with a Droplet in the panel, but tcpdump -i eth0 icmp shows no incoming packets when pinging the IP.
\n
• The API returns a 422 Unprocessable Entity error when attempting to reassign the IP between two Droplets in the same region.
\n
• The account has reached the Floating IP limit despite the panel showing available slots.
\n