Skip to main content

Apache - Host 2 Websites on the same IP and Port

The apache webserver is currently (at the date of writing this (08/2018)) the most popular web server for serving content on the internet. The Functionality we'll look at in this article is called 'Virtual Hosts'.

A virtual host is essential another domain running on the same server instance of apache.

For this demonstration, I'm going to use a CentOS 7.5.

First, update your system:
 [archy@websrv ~]$ sudo yum -y update

Next install apache on the server:
 [archy@websrv ~]$ sudo yum -y install httpd

By default, the webserver will not start on boot so we'll change that and start it for now:
 [archy@websrv ~]$ sudo systemctl enable httpd.service  
 [archy@websrv ~]$ sudo systemctl start httpd.service

By now your webserver is already serving the default-welcome page. This can be checked by curl or simply pointing your browser to the server's address. But since I don't have any firewall-rules set up yet, I'm going to use curl.
 [archy@websrv ~]$ curl localhost

This should return the source code for the default website.
Let's create the directory structure I'm going to use. This structure was originally introduced by debian developers but it makes it easy to keep track of enabled virtual hosts and inactive ones.
 [archy@websrv ~]$ mkdir -p /etc/httpd/sites-available  
 [archy@websrv ~]$ mkdir -p /etc/httpd/sites-eanbled

Your configs will go into /etc/httpd/sites-available and then symlinked to /etc/httpd/sites-enabled.
We'll also have to make apache aware that it should include these directories.

Open the /etc/httpd/conf/httpd.conf in your favorite text-editor and add the IncludeOptional-line at the end of the config file:
 [archy@websrv ~]$ sudo vim /etc/httpd/conf/httpd.conf  

 IncludeOptional sites-enabled/*.conf

Apache is now configured accordingly. Next we'll have to create the virtual host's config files.
 [archy@websrv ~]$ sudo vim /etc/httpd/sites-available/test1.archyslife.lan.conf  

 <VirtualHost *:80>  
     ServerAdmin webmaster@archyslife.lan  
     DocumentRoot /var/www/test1.archyslife.lan  
     ServerName test1.archyslife.lan  
     <Directory /var/www/test1.archyslife.lan/>  
         Options Indexes FollowSymlinks MultiViews  
         AllowOverride None  
         Order allow,deny  
         allow from all  
     </Directory>  
     ErrorLog /var/log/httpd/test1.archyslife.lan.error.log  
     LogLevel warn  
     CustomLog /var/log/httpd/test1.archyslife.lan.access.log combined  
     ServerSignature on  
 </VirtualHost>  


 [archy@websrv ~]$ sudo vim /etc/httpd/sites-available/test2.archyslife.lan.conf  

 <VirtualHost *:80>  
     ServerAdmin webmaster@archyslife.lan  
     DocumentRoot /var/www/test2.archyslife.lan  
     ServerName test2.archyslife.lan  
     <Directory /var/www/test2.archyslife.lan/>  
         Options Indexes FollowSymlinks MultiViews  
         AllowOverride None  
         Order allow,deny  
         allow from all  
     </Directory>  
     ErrorLog /var/log/httpd/test2.archyslife.lan.error.log  
     LogLevel warn  
     CustomLog /var/log/httpd/test2.archyslife.lan.access.log combined  
     ServerSignature on  
 </VirtualHost>

The virtual hosts are created now, let's enable them. As mentioned before, they need to be symlinked to the /etc/httpd/sites-enabled directory:
 [archy@websrv ~]$ sudo ln -s /etc/httpd/sites-available/test1.archyslife.lan.conf /etc/httpd/sites-enabled/  
 [archy@websrv ~]$ sudo ln -s /etc/httpd/sites-available/test2.archyslife.lan.conf /etc/httpd/sites-enabled/

Next, we'll have to create the folder-structure for the virtual hosts:
 [archy@websrv ~]$ sudo mkdir -p /var/www/test1.archyslife.lan  
 [archy@websrv ~]$ sudo mkdir -p /var/www/test2.archyslife.lan

With the folders created, let's create a basic index.html to be served:
 [archy@websrv ~]$ sudo vim /var/www/test1.archyslife.lan/index.html  

 <html>  
  <head>  
   <title>Welcome to test1.archyslife.lan</title>  
  </head>  
  <body>  
   <h1>This is the page test1.archyslife.lan</h1>  
  </body>  
 </html>  


 [archy@websrv ~]$ sudo vim /var/www/test2.archyslife.lan/index.html  

 <html>  
  <head>  
   <title>Welcome to test2.archyslife.lan</title>  
  </head>  
  <body>  
   <h1>This is the page test2.archyslife.lan</h1>  
  </body>  
 </html>

The apache is now configured. Let's restart and test the config:
 [archy@websrv ~]$ sudo systemctl restart httpd.service

Next add the server's IP address to the /etc/hosts file with the according fqdns.
 [archy@websrv ~]$ sudo vim /etc/hosts  

 172.31.0.100  test1.archyslife.lan  
 172.31.0.100  test2.archyslife.lan

Run curl with the domains and you should get your index.html's sourcecode back:
 [archy@websrv ~]$ curl test1.archyslife.lan  

 <html>  
  <head>  
   <title>Welcome to test1.archyslife.lan</title>  
  </head>  
  <body>  
   <h1>This is the page test1.archyslife.lan</h1>  
  </body>  
 </html>  


 [archy@websrv ~]$ curl test2.archyslife.lan  

 <html>  
  <head>  
   <title>Welcome to test2.archyslife.lan</title>  
  </head>  
  <body>  
   <h1>This is the page test2.archyslife.lan</h1>  
  </body>  
 </html>

Last step, adding firewall rules. To make our webserver available from public, add the port 80 to the firewall.
 [archy@websrv ~]$ sudo firewall-cmd --add-service=http --permanent  
 [archy@websrv ~]$ sudo firewall-cmd --reload

That concludes the setup.

Feel free to comment and / or suggest a topic.
Labels:

Comments

Post a Comment

Popular posts from this blog

Dynamic DNS with BIND and ISC-DHCP

I personally prefer to work with hostnames instead of ip-addresses. If you have anything like freeipa or active directory, it will do that for you by registering the client you added to your realm to the managed dns and edit the records dynamically. We can achieve the same goal with just bind and isc-dhcp. I'll use a raspberry pi with raspbian 9 for this setup. So here is a quick tutorial on how to configure the isc-dhcp-server to dynamically update bind. First set a static ip to your server. [archy@ddns ~]$ sudo vim /etc/network/interfaces # interfaces(5) file used by ifup(8) and ifdown(8) # Please note that this file is written to be used with dhcpcd # For static IP, consult /etc/dhcpcd.conf and 'man dhcpcd.conf' # Include files from /etc/network/interfaces.d: source-directory /etc/network/interfaces.d auto eth0 iface eth0 inet static address 172.31.30.5 network 172.31.30.0 broadcast 172.31.30.255 netmask 255.255.255.0 ...
Post a Comment
Read more

LACP-Teaming on CentOS 7 / RHEL 7

What is teaming? Teaming or LACP (802.3ad) is a technique used to bond together multiple interfaces to achieve higher combined bandwith. NOTE: every clients speed can only be as high as the single link speed of one of the members. That means, if the interfaces I use in the bond have 1 Gigabit, every client will only have a maximum speed of 1 Gigabit. The advantage of teaming is, that it can handle multiple connections with 1 Gigabit. How many connections depends on the amount of your network cards. I'm using 2 network cards for this team on my server. That means I can handle 2 Gigabit connections at full rate on my server provided the rest of the hardware can deliver that speed. There also exists 'Bonding' in the Linux world. They both do the same in theory but  for a detailed comparison check out this  article about teaming in RHEL7 . To create a teaming-interface, we will first have to remove all the interface configurations we've done on the (soon to be) sla...
8 comments
Read more

Push logs and data into elasticsearch - Part 2 Mikrotik Logs

This is only about the setup of different logging, one being done with Filebeat and the other being done with sending logging to a dedicated port opened in Logstash using the TCP / UDP Inputs. Prerequesites: You'll need a working Elasticsearch Cluster with Logstash and Kibana. Start by getting the Log Data you want to structure parsed correctly. Mikrotik Logs are a bit difficult since they show you Data in the interface which is already enriched with Time / Date. That means a message that the remote logging will send to Logstash will look like this: firewall,info forward: in:lan out:wan, src-mac aa:bb:cc:dd:ee:ff, proto UDP, 172.31.100.154:57061->109.164.113.231:443, len 76 You can check them in the grok debugger and create your own filters and mapping. The following is my example which might not fit your needs. Here are some custom patterns I wrote for my pattern matching: MIKROTIK_DATE \b(?:jan(?:uary)?|feb(?:ruary)?|mar(?:ch)?|apr(?:il)?|may|jun(?:e)?|jul(?...
9 comments
Read more

FreeIPA - Integrating your DHCPD dynamic Updates into IPA

I recently went over my network configuration and noticed that the dhcp-leases were not pushed into the IPA-DNS yet. So I thought, why not do it now. The setup is very similar to setting it up on a single bind instance not managed by IPA (I've already written a guide about this here ). My setup is done with the following hosts: ipa01.archyslife.lan - 172.31.0.1 inf01.archyslife.lan - 172.31.0.5 First of all, create a rndc-key: [archy@ipa01 ~]$ sudo rndc-confgen -a -b 512 This will create the following file '/etc/rndc-key' [archy@ipa01 ~]$ sudo cat /etc/rndc.key key "rndc-key" { algorithm hmac-md5; secret "secret_key_here=="; }; We also need to make named aware of the rndc-key and allow our remote dhcp server to write dns entries: [archy@ipa01 ~]$ sudo vim /etc/named.conf ... include "/etc/rndc-key"; controls { inet 172.31.0.1 port 953 allow { 172.31.0.5; } keys ...
2 comments
Read more

SSSD - Debugging PAM permission denied

Sometimes there's weird errors in IT that occur on random chance. I've had such an encounter with SSSD in combination with IPA(+AD-Trust) recently, where only sometimes, a connection to one of the IPA-Servers would fail with this error: Jul 13 13:36:42 ipa02.archyslife.lan sshd[3478]: pam_sss(sshd:account): Access denied for user runner: 4 (System error) Jul 13 13:36:42 ipa02.archyslife.lan sshd[3478]: fatal: Access denied for user runner by PAM account configuration [preauth] In my case, it was only happening sometimes when running a basic system setup role using ansible on every host in the entire environment. This way, there was no consistent pattern besides being the same host every time if it failed. First up, add the 'debug_level=X' to every section required in the /etc/sssd/sssd.conf where X is a number from 1 to 10 with 10 being the most verbose. Afterward, restart sssd and check the logs for any obvious problems. 1) If you are using local users, check the...
Post a Comment
Read more