Floating IP can't be accessed via browser, ping and ssh

July 31, 2016 7.7k views
DNS DigitalOcean High Availability Linux Commands Ubuntu

I've added a floating IP but the IP address just won't work. Pinging the newly created floating IP will get request timeout for icmp_seq 0. SSH also doesn't work.
I have tried changing my domain name A record to the floating IP but then the website just won't load anymore and I am forced to change it back to the original IP.

6 Answers
tishma September 15, 2016
Accepted Answer

In my case - it was a missing firewall rule that prevented my droplet from responding. The thing is that I've assigned the floating IP while my droplet was off. However, I've unassigned, and when assigning again, I got the nice popup with hint that droplets created before some time in 2015 must manually be added a firewall rule. After I did that all was good.

  • Thank you very much. Following the pop up after unassign and assinging worked!

  • My droplet wasn't powered off when I assigned the floating IP, but I never got the firewall upgrade notification. Taking off the IP and assigning it again fixed the issue for me.

Please make sure that you have assigned the floating IP to your droplet. There is a tutorial available on it here: https://www.digitalocean.com/community/tutorials/how-to-use-floating-ips-on-digitalocean

by Melissa Anderson
A DigitalOcean Floating IP is a publicly-accessible static IP address that can be mapped to one of your Droplets. A Floating IP can also be instantly remapped, via the DigitalOcean Control Panel or API, to one of your other Droplets in the same datacenter. This instant remapping capability grants you the ability to design and create High Availability (HA) server infrastructures by adding redundancy to the entry point, or gateway, to your servers.
  • Sorry, I forgot to mention that I have followed that exact tutorial and it's not working as per the question. My screen looks exactly like the screenshots in the tutorial (obviously with the differences being the IP and the Droplet name).

    • Can you ping the droplet IP directly?

      • Yes, I have been using that Droplet for sometime now. I can SSH into the IP directly, pinging it and use it with domain names.

        I don't know if this helps, but both my Droplet are in LON1.

        • It sounds like the Floating IP has not been assigned properly. Try assigning your Floating IP to the Droplet again.

          • I've just tried that again, it still doesn't work.
            Here are my replication steps on reassigning:

            1. Go to Networking > Floating IPs https://cloud.digitalocean.com/networking/floating_ips
            2. In the Assign a Floating IP section, click on Search for a Droplet then select my Droplet, say Foo.
            3. Wait for the website to load and I get the new section "Floating IPs" with these information LON1 -> Foo 512MB / 20GB / LON1.
            $ ping
            PING ( 56 data bytes
            Request timeout for icmp_seq 0
            Request timeout for icmp_seq 1
            Request timeout for icmp_seq 2
            --- ping statistics ---
            4 packets transmitted, 0 packets received, 100.0% packet loss
          • @nelsyeung That's very odd. Do you have a firewall setup on the server that might be blocking the floating ip?

          • I have only really used this tutorial: https://www.digitalocean.com/community/tutorials/additional-recommended-steps-for-new-ubuntu-14-04-servers for setting up the firewall, so I don't think that I have anything that's blocking it?

            by Justin Ellingwood
            After setting up the bare recommended configuration for a new server, there are often some additional steps that are highly recommended in most cases. In this guide, we'll continue the initial configuration by tackling some recommended, but optional procedures.

I just had the same problem. I created a floating IP to a droplet that was created two years ago and I couldn't ping that floating IP. But after that I tried to create a new floating IP and point it to a newly created droplet and everything works OK. So, as I suppose that is because of the age of the first droplet.

I am facing the exact same issue after assigning floating IP to a droplet.

PING 159.89.XXX.XXX (159.89.XXX.XXX): 56 data bytes
Request timeout for icmpseq 0
Request timeout for icmp
seq 1
Request timeout for icmpseq 2
Request timeout for icmp
seq 3
Request timeout for icmp_seq 4

So, I followed above instructions and unassigned, then reassigned the floating IP, which worked for a minute. After couple of hours, it stopped working and gave the same result as above.

The droplet where I am facing this issue is:

8 GB Memory / 30 GB Disk / NYC3 - Ubuntu LEMP on 16.04

I need for this to work so that I can move the Floating IP to the new server I have created via snapshot and updated the server, but until this works on the existing server, I can not assign it to the new server.

Any help / guidance will be much appreciated.

If you run tcpdump on the host the floating IP is intended to point to you may see that incoming traffic is from the internal (10.x.x.x) network.

Adjust your services accordingly to ensure incoming data can flow from the DO service that hosts your floating IP to your primary Droplet.

Go to Networking >> Floating IPs >> Select your expected floating IP >> More >> Reassign and a Pop-up window will come up saying you to run some commands for you old Droplet.

Have another answer? Share your knowledge.