Challenge 1: load balancing using sticky sessions (ssl enabled)

We start configuring NGNINX to serve and act as a loadbalancer (extranet) and reverse proxy for multiple NGINX instances in your local area network (intranet). On the first Server (Server1) we will change the nginx.conf and the gateway.conf to act as loadbalancer and reverse proxy.

From now your Nextcloud binaries and data are shared using NFS. All files and data are delivered by Server1 which serves as NFS-Server. Please keep in mind to use a dedicated NFS-Server or an existing NAS like Synology.

For this Lab we simplified the entire topology by using Server1 for both, the loadbalancer and the NFS-Server. We highly recommend to separate it for security and performance reasons outside this Lab-environment!

Nextclud will now interact with your global remote database from all loadbalanced Nextcloud instances. Please keep in mind to set up a dedicated MariaDB-Server for security and perdormance reasons.

For this Lab we simplified the entire topology by using Server1 for all, the loadbalancer, the NFS-Server and the database server. We highly recommend to separate it for security and performance reasons outside this Lab-environment!