Question

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

Posted July 31, 2016 10.3k views
UbuntuDigitalOceanDNSLinux CommandsHigh Availability

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.

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

×
6 answers

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.

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

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.

Submit an Answer