lush3ng
By:
lush3ng

How to setup Vestacp when using Floating IP ?

December 4, 2015 2.6k views
Control Panels

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.

1 comment
3 Answers

Hi there!

So I noticed when you install VestaCP it takes our anchor IP (for floating IPs) and makes it the default IP address. What you have to do is login, click on the Web tab, click Edit next to your site, and change the IP address to the public IP address on your droplet. This will rewrite the web server configuration and bind it to the proper address.

If I can be of any further assistance, please be sure to let me know.

Kind Regards,
Jarland
Platform Support Specialist

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)

Have another answer? Share your knowledge.