I started testing the floating IP feature and I am running into a few problems:

I am able to assign a floating IP to a droplet.
According to the documentation, as this is a brand new droplet, it should already have an ‘anchor’ IP to use.
However when I try use curl with –interface

I get:
curl: (45) bind failed with errno 99: Cannot assign requested address
curl: (6) Could not resolve host: Pragma; Unknown error

Initially I’d thought the issue is somehow related to curl IPv6 bugs so I spun up another droplet with IPv6 disabled and I am still getting the error.

The second issue I have is trying to automate this process using REST API (initially using curl as well).
When running an API call I get:
“"Due to limited availability we have temporarily disabled IP reservation in this region.”“ however the same funtionality is working fine using website admin UI.

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.

Submit an Answer
2 answers

Hello friend!

My first thought is that the web server may be bound to the droplet’s public IP rather than If you run “netstat -tulpn” you should be able to see if that is true. Ideally you want the web server to bind to every interface in this case, and that would allow it to pass through the anchor IP.

Kind Regards,

is it mentioned anywhere in the docs?
I have been charged a lot but I wasted a lot of time assuming this would work like AWS Elastic IP.