Question

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

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.


Submit an answer


This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

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.

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.

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 icmp_seq 0 Request timeout for icmp_seq 1 Request timeout for icmp_seq 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.

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.

Try DigitalOcean for free

Click below to sign up and get $200 of credit to try our products over 60 days!

Sign up

Become a contributor for community

Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.

DigitalOcean Documentation

Full documentation for every DigitalOcean product.

Resources for startups and SMBs

The Wave has everything you need to know about building a business, from raising funding to marketing your product.

Get our newsletter

Stay up to date by signing up for DigitalOcean’s Infrastructure as a Newsletter.

New accounts only. By submitting your email you agree to our Privacy Policy

The developer cloud

Scale up as you grow — whether you're running one virtual machine or ten thousand.

Get started for free

Sign up and get $200 in credit for your first 60 days with DigitalOcean.*

*This promotional offer applies to new accounts only.