Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Multiple Apache Servers 1 Public IP Address

Status
Not open for further replies.

thetank

Programmer
Jul 29, 2011
3
US
Hello everyone!
I just had a question and was hoping to get some feed back.

The situation is that i have one physical server with one NIC that's running 3 virtual servers. Those virtual servers are a mixture of Ubuntu Linux and CentOS. Each server runs flawlessly with no problems.
On Server A i have LAMP installed hosting wordpress sites.
On Server B i have LAMP installed hosting some Drupal sites.
On the physical server I have Apache installed and am using it as a reverse proxy to send traffic from specific URLS to Server's A and B all from the same public IP address.
I really just wanted to get some advice and suggestions if this is the best way to go about setting up Apache for this situation.
Just for some additional information this is the config file on physical Apache doing the reverse proxy.

<virtualhost *:80>
ServerAdmin webmaster@web.com
ServerName exmaple.com
ProxyRequests off
ProxyPreserveHost on
<proxy *>
Order deny,allow
Allow from all
</proxy>
ProxyPass /SiteRoot ProxyPassReverse /SiteRoot ProxyPass /SiteRoot2 ProxyPassReverse /SiteRoot2 </VirtualHost>

On Server A and B have their config files for the respective sites as virtual hosts.
Thanks for you feedback greatly appreciate it!
 
Hi,

I'm actually going through the same issue: multiple hosted sites on a handful of web servers, with 5 public IPs. I'm trying to consolidate down to a single LAMP server to conserve heat and power, since the resources on that server are particularly high. I found a post last week that's very useful, and I'll be implimenting several of the fixes. Let me know what you think:
 
The second situation is fairly easy - you set up one physical server with named virtual hosts for each site, do all your config and get the content up for each site, and then just change the nameserver records to point to the new IP. 3 or 4 days later after the new IP address for all the sites has propagated across the web you can shut down all the old servers.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top