Report this

What is the reason for this report?

How to setup Vestacp when using Floating IP ?

Posted on December 4, 2015

I am using one droplet with CentOS and Vestacp installed on them. Also I assigned a Floating IP to that droplet. In Vestacp i created two accounts for my two domains. At the registrar I pointed them to the digitalocean NS servers. In the domain section of digitalocean I created entries for the two domains. Both of the domains respond at ping requests from the floating IP. The problem is that when I try to access the domain by http I land on the cgi-sys/defaultwebpage.cgi page.

Please if you could tell me what further settings must I operate in Vestacp so that both of my domains work.

Thank you in advance.



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!

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.

Me too having issues.

  1. Created a new droplet with ip ‘1’
  2. setup my vestacp - ubuntu16-apache2+Nginx > everything works well. I deployed few sites, and all works well.
  3. assigned a floating ip to my droplet ip’2’
  4. i added this ip ‘2’ into my existing vestacp ip’s NAT field.
  5. now my vestacp shows my servers IP->NAT ip.
  6. But on my cloudflare, if i pointing to ip ‘2’, it not working. But still works with ip’1’.
  7. the main reason we need floating ip is , if we want to run our sites with backup droplet, but we dont want to change the domain’s A records (as it should point to our floating ip always).
  8. How to make this work?

Realized the issue. Somehow the droplet’s original 'AnchorIP (eg 10.0.1.15) is missing from vestacp’s IP list on the dashboard. Added the Anchor IP with subnet mask, then tested working fine.

The theme is : the floating IP is always looking for the AnchoIP of the droplet, not the public IP. So, our vestacp server should listen the anchorip too as one of a ip on the webserver (by default it will)

  1. find your anchor ip by running this command
curl -s http://169.254.169.254/metadata/v1/interfaces/public/0/anchor_ipv4/address
  1. Add the anchor IP on vesta yourdomain.com:8083/list/ip/ PS: use the same Netmask your public ip is using

  2. Change your website IP from the private IP to the anchor IP yourdomain:8083/edit/web/?domain=yourdomain --> IP Address

That’s it, you are listening to the floating ip

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.