You can actually simplify that if they're all going to the same place by listing all the IP addresses in the one VirtualHost container of the main site:dave9000 said:Sure you can. Its going to have to be done manually but it can be done. Apache will always default to the first entry for a ip address if it does not find a valid virtual host entry so therefor just add 5 entries to the httpd.conf 1 for each address and set the path to the web you wish to display.
DocumentRoot /path to web
DocumentRoot /path to web
Add additional entries to the VirtualHost container according to your needs
Resurrecting once again since we are looking once more into setting this up. We need cPanel to accept web traffic (and preferably also mail traffic) FROM more than one IP TO a single cPanel account.Hate to dig up an old thread but I'm looking at this a couple years later and wondering if anything has changed with the procedure. We are running WHM/Cpanel and when viewing the httpd.conf it shows that these lines should not be edited and that an include file should be used instead.
To give a little background, we are looking into getting some redundancy for our server's internet connection and need to know how to setup the WHM/Cpanel server itself to accept traffic on both the primary and the secondary (failover) IP addresses. We will be using dnsmadeeasy to handle the DNS part of the equation, we just need to make sure the server is ready to accept the traffic once people are directed to the new IP.
In short, what needs to be done to set this up to work properly on our WHM/CPanel server?
Thanks for the reply. We aren't looking for traditional "failover" in terms of the server itself, just in terms of the internet connection to the server. Web hosting is not our primary business and we maintain our own server with about 30 sites located our office. Our primary connection is via Cable which isn't 100% reliable, so our main concern is having a backup connection (DSL most likely) that will allow the sites/email to remain live while whatever issues with the primary connection are resolved.The configuration part really has not changed and remains the same as
it was back when this thread originally began despite the current use
of include files.
You would need to expand the virtualhost container to include the new IPs
and then of course update your DNS zone files to also resolve the new IPs.
Now if this is all on one server with a single network interface running
multiple IPs, there is no real tactical advantage to doing this and it
won't do anything in terms of "load balance" or "failover" because you
are running off of the same physical machine so one down is all down.
If you are dealing with multiple physical network interfaces, that might
be a different issue but again limited if you are running the same server
as would be the case for this sort of configuration.
To have any kind of real "failover" type configuration for multiple IPs,
those IPs would actually be on different servers and the DNS would be
setup to load balance between the multiple servers running mirrored
accounts between each other each on their own IP but with the
same domain address.
<VirtualHost[% FOREACH ipblock IN vhost.ips %] [% ipblock.ip %]:[% ipblock.port %][% END %]>
<VirtualHost[% FOREACH ipblock IN vhost.ips %] [% ipblock.ip %]:[% ipblock.port %][% END %][b] x.x.x.x:80 y.y.y.y:80 z.z.z.z:80[/b]>
|Thread starter||Similar threads||Forum||Replies||Date|
|B||CloudLinux VM with multiple FO IPs on top of Proxmox (OVH)||General Discussion||1|
|S||Is it safe to have multiple shared IPs||General Discussion||6|
|G||Protecting from IPs with multiple concurrent requests||General Discussion||2|
|H||multiple shared IPs.||General Discussion||3|
|Varnish Issues with Multiple IPs||General Discussion||1|