Reverse proxy

Introduction

A requirement I imposed myself on the project was that it was going to use a domain name + ssl; this implementation in my network requires a Reverse Proxy. I opted to chose the Nginx Reverse Proxy Manager Docker container for this.

Theory

In my specific configuration, in which I host multiple websites from my server my singular IP-adress needs to be able to serve multiple HTTP requests. Simply binding all port 80 traffic to one service isn’t in my interests; therefor I chose to use a Reverse Proxy. This enables me to have multiple http endpoints in my network cluster. See my network setup here:

In this example, it is possible to bind multiple host names and subdomains across various networks.

Implementation

I deployed my Reverse Proxy in my Portainer environment as can be seen here:

And then added my api.oksolution.nl as an endpoint that was to be pointed to my Rancher deployment, which can then handle its ingress.

The page itself (currently) serves no endpoint, but a working SSL configuration can be seen here: