Skip to main content





How to set up NGINX as a Reverse Proxy

  • Edit
    Collaborate with us
    Edit this page on GitHub
  • This document is part of the document How to automate Docker container deployment with Jenkins and instructs you how to set up NGINX as a reverse proxy for the test scenario.

    In this example, we use two additional servers:

    • Windows Server for a Container
    • Linux Server for NGINX

    Additional settings for the OutSystems Machine

    The setup for this machine is explained in How to automate Docker container deployment with Jenkins, but if you are using NGINX as the reverse proxy, you need to do these additional settings:

    Windows Server - Containers Machine

    • Windows Server 2016
    • Docker Enterprise Edition (latest version)
    • Jenkins (version 2+ 64 bit)
    • The executables pscp.exe and plink.exe from PuTTY (latest stable version)

    Linux Server - NGINX Machine

    • A Linux distro of your liking
    • NGINX (latest version) to be used as a reverse proxy

    1. Configure the network

    Configure your network like this:

    • The NGINX machine is publicly accessible (e.g
    • The OutSystems Machine is accessible from the address defined in the Global Deployment Zone (e.g
    • The Container Machine is accessible from the given address defined in a Deployment Zone (e.g
    • Both the OutSystems Machine and the Containers Machine are accessible to the NGINX machine (via ports 80 and 443)
    • The Container Machine is accessible to the OutSystems Machine from the port configured for Jenkins (the default is 8080)
    • Both the OutSystems Machine and the Containers Machine can reach the OutSystems database

    2. Configure NGINX

    These are the basic NGINX configuration steps for to test a deployment scenario. Adapt it to your requirements.

    1. Copy the contents of the general NGINX configuration file to /etc/nginx/nginx.conf. The file has the basic common settings for the NGINX service.

    2. After adapting server NGINX configuration file to your scenario, as instructed in the comments, copy its contents to /etc/nginx/conf.d/testing_containers.conf. This configuration file has settings more specific for our test scenario, namely how to handle SSL Offloading/Termination.

    3. Configure a user with read/write privileges to, at least, the /etc/nginx/conf.d/ folder and with the permissions to restart the NGINX service. The DockerEEPlusNGiNX module needs these user credentials to copy the location config files to that folder and restart the NGINX service to apply the changes.

    3. Configure the DockerEEPlusNGiNX Container Automation module

    In the Container Machine:

    1. Place the pscp and plink executables to C:\putty\ (this is the default folder).

    2. Go to your local DockerEEPlusNGiNX module Settings file and configure the settings as described by the comments. This file groups various required settings to the module, such as which machine to connect, what user credentials to use, and where to find the required executables.

    • Was this article helpful?