Webservers

Introduction

There will be several Webservers in the Home Lab. Each will be on it's own Virtual Machines and will be on the production VLAN. The MySQL databases will be on a separate VM on the same network so no connectivity problems from that. The Proxy server will forward all web traffic to the appropriate webserver.

SSL Config

There will be two setups for SSL/TLS one for the seaoffate.local and one for seaoffate.net.

Local DNS Names SSL Setup

We will do the SSL/TLS for the .local access first mainly because because it is better to see it working on a local level and if we did the global first there is a good chance we would never get a around to doing the local, in which case some of the access will be completely without any cert. It is part of the learning curve to generate SSL certificates. While it would be fairly easier to do a self cert for the local access it is better to experience the whole process from start to finish to get a complete understanding of how it is done and the failures that inevitably appear.

The Process Flow

The process flow is to get the Certificates generated on the webserver host, get it signed by the Certificate Authority then apply it to the webserver, once that is done the SSL config needs to be applied to the host, after that it we would make a config to the reverse proxy. The reverse proxy will have it's own certificate to use for all of the hosts that it is forwarding to and once the cert is applied it will not need to have it applied again, we would just refer to it in the individual SSL config.

webservers Purposes

four webservers with the primary job of serving websites have been defined.

Logan (Wiki)

logan has been setup as a webserver to have the wiki website. It' IP is prod.12 It can be accessed by logan.seaoffate.local, wiki.seaoffate.local or wiki.seaoffate.net

Lime (default)

The default website is hosted on lime. The IP is prod.10. It can be accessed by lime.seaoffate.local, www.seaoffate.local or www.seaoffate.local.

Fig (files)

not setup yet ip will is prod.11

Plum (Photo)

This one is to host the photo website, probably Piwigo. It can be accessed at plum.seaoffate.local, photo.seaoffate.local or plum.seaoffate.net. The Ip will be Prod.20. The setup here is to have a normal HD for the webserver but a NFS share for the base photos with only RO access. The actual directory where the photos are shared from will be another VM called strawberry (IP prod.21).

Website log files and locations

The Docroots are

/var/www/wiki.seaoffate.local/public_html

and

/var/www/seaoffate.local/public_html

and

/var/www/files.seaoffate.local/public_html

The access logs are seperate for each config

www.seaoffate on Lime

For the .net they are

/var/log/apache2/www.seaoffate.net-error.log
/var/log/apache2/www.seaoffate.net-access.log

and the local are

/var/log/apache2/lime.seaoffate.local-error.log
/var/log/apache2/lime.seaoffate.local-access.log

wiki.seaoffate on Logan

For the .net they are

/var/log/apache2/wiki.seaoffate.net-error.log
/var/log/apache2/wiki.seaoffate.net-access.log

and the .local are

/var/log/apache2/wiki.seaoffate.local-error.log
/var/log/apache2/wiki.seaoffate.local-access.log
/var/log/apache2/logan.seaoffate.local-error.log
/var/log/apache2/logan.seaoffate.local-access.log

Nginx Log Files

DocumentRoot /var/www/files.seaoffate.local/public_html DocumentRoot /var/www/files.seaoffate.local/public_html DocumentRoot /var/www/files.seaoffate.local/public_html