This is an optional offering. Once deployed, users are responsible for its maintenance and updates. Feel free to ask for feedback in the #peer-support channel on EWC RocketChat.

NGINX Proxy Manager is used to mange reverse proxy servers, streams and redirection hosts.

Other Nginx Proxy Manager features include:

  • Virtual host management
  • Ability to cache assets
  • Blocking of common exploits
  • Websocket support
  • Access list configuration
  • SSL and HTTP/2 support
  • Host redirection with HTTP code configuration
  • TCP and UDP stream support
  • User management
  • Nginx Proxy
  • Manager log auditing

Nginx is an extremely powerful web server and reverse proxy. The Nginx Proxy Manager is full-featured tool that helps to lower the barriers to entry for users who are interested in learning and working with the Nginx server.

How to provision NGINX Proxy Manager

If provisioning after October of 2025, we recommend deploying based on the community hub, to benefit form upcoming features or fixes.

Pre-requisites

Security Group

You may create security groups either via legacy Morpheus UI settings (available until end of 2026) OR via Community Hub Item deployment. Once your tenancy is onboarded into the EWC IAM, you may also create security groups via the EWC Cloud Management UI settings.

Create a designated security group with a descriptive name (e.g. "nginx-proxy-manager" ) and add to it the following rules:

NameDirectionRule TypeProtocolPort RangeSource TypeSourceDestination Type
HTTPSingressCustom RuleTCP443Network<private subnet IP range>Instance
HTTPingressCustom RuleTCP80Network<private subnet IP range>Instance
SSHingressCustom RuleTCP22Network<private subnet IP range>Instance
NPM - Admin frontendingressCustom RuleTCP8200Network<private subnet IP range>Instance

Make sure to replace the <private subnet IP range> placeholder accordingly. For example:

  • If the VM will connect to the private subnet which comes out-of-the-box on EUMETSAT tenancies, you can replace with 10.0.0.0/24
  • If connecting to the out-of-the-box subnet on EWCWF tenancies, replace with 192.168.1.0/24

Deployment based on the EWC Community Hub

Checkout the corresponding Community Hub Item.

Next steps

Related articles