How to setup virtual hosts to point to two diffrent directories

From what I can see, there are a few problems, and could be more. For beginners, while you have told Apache where to find the root for each server, you haven't given Apache permission to "serve" files from those directories. Nor have you told Apache that these are virtual hosts. There are other things you need to do with the virtual host conf files, but at a minimum you need to give Apache permission to server the files in the directory, and you need to tell Apache that this is a virtual host definition. Modified for only this minimum, the two files look like this:

This is the new virtual host file (/etc/apache2/sites-available/wasamar.com.ng.conf):

<VirtualHost *:80> ServerName wasamar.com.ng ServerAlias www.wasamar.com.ng ServerAdmin [email protected] DocumentRoot /var/www/html/wasamar/public # Available loglevels: trace8, ..., trace1, debug, info, notice, warn, # error, crit, alert, emerg. # It is also possible to configure the loglevel for particular # modules, e.g. #LogLevel info ssl:warn ErrorLog ${APACHE_LOG_DIR}/error.log CustomLog ${APACHE_LOG_DIR}/access.log combined # For most configuration files from conf-available/, which are # enabled or disabled at a global level, it is possible to # include a line for only one particular virtual host. For example the # following line enables the CGI configuration for this host only # after it has been globally disabled with "a2disconf". #Include conf-available/serve-cgi-bin.conf # At least you need to make the folder accessable for serving by the server. # Versions of Apache, and modules installed can make a difference in what's inside # the Directory directive. But as an example: <Directory "/var/www/html/wasamar_ts/public"> <IfModule mod_authz_core.c> Require all granted </IfModule> <IfModule !mod_authz_core.c> Order allow,deny Allow from all </IfModule> </Directory> </VirtualHost> 

This is the new virtual host file (/etc/apache2/sites-available/ts.wasamar.com.ng.conf):

<VirtualHost *:80> ServerName ts.wasamar.com.ng ServerAlias www.ts.wasamar.com.ng ServerAdmin [email protected] DocumentRoot /var/www/html/wasamar_ts/public/ # Available loglevels: trace8, ..., trace1, debug, info, notice, warn, # error, crit, alert, emerg. # It is also possible to configure the loglevel for particular # modules, e.g. #LogLevel info ssl:warn ErrorLog ${APACHE_LOG_DIR}/error.log CustomLog ${APACHE_LOG_DIR}/access.log combined # For most configuration files from conf-available/, which are # enabled or disabled at a global level, it is possible to # include a line for only one particular virtual host. For example the # following line enables the CGI configuration for this host only # after it has been globally disabled with "a2disconf". #Include conf-available/serve-cgi-bin.conf # At least you need to make the folder accessable for serving by the server. # Versions of Apache, and modules installed can make a difference in what's inside # the Directory directive. But as an example: <Directory "/var/www/html/wasamar_ts/public"> <IfModule mod_authz_core.c> Require all granted </IfModule> <IfModule !mod_authz_core.c> Order allow,deny Allow from all </IfModule> </Directory> </VirtualHost> 

In both cases the change is adding the first line, and the last ten lines. Inside the directive you probably need other things, such as Options and AllowOverride for example.

For all this to work, you also need something more in your main conf file, probably httpd.conf in some directory, likely /etc/apache2/. What's needed is an instruction to include these new files in the configuration. at its simplest, based on the paths given, it would look like these:

Include sites-available/wasamar.com.ng.conf Include sites-available/ts.wasamar.com.ng.conf 

If you only include virtual hosts in the sites-available directory, then you can use

Include sites-available/*.conf 

That will include any .conf file placed there, so you can create additional hosts as needed and not have to add a line to httpd.conf everytime you do.

You can learn a lot, and spend days reading, and re-reading, the Apache documentation online, or probably included with your installation of Apache locally. It may seem like a lot, but it is time well spent.