Connecting to floating IP within the same datacenter

It looks like there’s a bug in routing floating IPs. When connecting from another droplet within the same datacenter through floating IP, the connection sometimes works and sometimes doesn’t. Using droplet’s own IP address immediately resolves the problem at the cost of losing floating IP functionality.

That means floating IPs are presently useless for backend servers. It also means it is impossible to publish application APIs through floating IP address, because there is always some non-trivial probability that some API client happens to be in the same datacenter.

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.

Want to learn more? Join the DigitalOcean Community!

Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.

I just got bit by this with crazy timeouts when trying to access my own droplet by its DNS name which is tied to the floating IP.

What is going on with this? Any plans to fix it?

I’m also experiencing this issue. Very annoying that you have to ping to fix it. Spent 2 days trying to troubleshoot this and finally found this post. Please fix @BrookDO

Hi Robert,

This is a known issue, and we are working on a resolution. Currently, the workaround is to ping the public IP of the Droplet with the Floating IP to populate the ARP table.