Part 5: How to set up NGINX Proxy Manager using Docker Compose

Anebula is reader-supported. When you buy through links on our site, we may earn an affiliate commission.

This guide is part of the How to host multiple sites on one virtual machine with Docker series where you learn how to create a virtual machine (VM) to host multiple websites and apps. In this series, we will host a WordPress blog, a Ghost blog, a Matamo Analytics app, and much more!

Up to this point, we have purchased a domain and set up the domain with Cloudflare DNS, we created a VM on Digital Ocean, then we connected to that VM using Visual Studio Code. Now it is time to set up NGINX Proxy Manager via Docker.

Step 1: SSH into your Virtual Machine

Before we can set up NGINX Proxy Manager, we need to SSH into our machine. Follow the steps from the previous post to SSH in. Alternatively, here is a quick summary – Open VSC > Remote Explorer > Connect. Then enter your SSH key passphrase.

Step 2: Create a Docker network

We need to create a Docker network so that multiple Docker Compose instances can see the proxy.

In VSC, open up the terminal by going to Terminal > New Terminal, then enter the following command.

docker network create nginx-proxy

This will create a new network called nginx-proxy. Once it’s created you won’t need to come back and edit it in any way.

Step 3: Set up NGINX Proxy Manager

This step will walk you through getting NGINX Proxy Manager up and running and available on the world wide web.

In the /root directory, create a new folder “docker-stack” with a sub-folder “nginx-proxy-manager”. Ex:

/root/docker-stack/nginx-proxy-manager

Then in the nginx-proxy-manager folder, create a file called docker-compose.yml and paste in the following.

version: "3"
services:
  npm:
    image: 'jc21/nginx-proxy-manager:latest'
    restart: unless-stopped
    ports:
      # These ports are in format <host-port>:<container-port>
      - '80:80' # Public HTTP Port
      - '443:443' # Public HTTPS Port
      - '81:81' # Admin Web Port
      # Add any other Stream port you want to expose
      # - '21:21' # FTP
    # expose:
    #   - '81'
    volumes:
      - ./data:/data
      - ./letsencrypt:/etc/letsencrypt

networks:
  default:
    name: nginx-proxy
    external: true

The docker-compose.yml file contains information on how to start and configure a docker container.

Now in the terminal navigate to the project folder and start up the container.

cd docker-stack/nginx-proxy-manager
docker compose up -d

This will take a minute the first time you run it since it needs to download the image, once ready it will start your container and you’ll have NPM running.

Now we can access NPM from a browser. Go to your IP address and port 81.

Ex: 157.230.xxx.xxx:81/login

Use the IP for your own virtual machine.

Now enter the default username and password:

Email:    [email protected]
Password: changeme

Fill out the next form with your full name, nickname, and email address.

Then create a good strong password.

Step 4: Add Cloudflare Origin Server Key

Log into Cloudflare, click on the website that you set up in Part 2: How to set up a site with Cloudflare DNS, then on the main menu click on SSL > Origin Server

Then Create Certificate, leave everything as default then click Create

cloudflare ssl origin server

cloudflare create certificate 1

cloudflare create certificate 2

cloudflare create certificate 3 copy and save pem

npm add custom SSL certificate

cloudflare create certificate 5 upload files

Now copy the certificate and private keys into a notepad and save.

Now in NPM, go to SSL Certificates > Add SSL Certificate > Custom

Step 5: Set up Cloudflare DNS for NPM

No website setup is complete without proper HTTPS setup. Let’s create a subdomain so that it can point to our NPM instance.

Go into Cloudflare then click on DNS > Add Record

Fill out the record according to the following info.

Lastly, let’s go to SSL/TLS and then switch the mode to Full (Strict). This will encrypt the entire connection from the clients to Cloudflare and then to your origin server.

Part 6: Set up NPM to proxy itself

This next part will set up NPM to proxy itself so that the NPM management site is under a subdomain with SSL.

Go back into NPM then click on Host > Proxy Hosts > Add Proxy Host.

Switch to the SSL tab, select your SSL Certificate that you set up in step 4, turn on Force SSL then click save.

Now open a new browser tab and go to your hostname and voila! You now have NPM behind HTTPS.

Now keep in mind that NPM is still available via the IP address so we need to fix that.

Step 7: Remove NPM container to host mapping

Go into VSC again and bring down the docker compose instance

docker compose down

Then edit docker-compose.yml to comment out the original 81:81 mapping and uncomment the expose property.

By doing so, host port 81 will not be directly tied to container port 81 which closes a security hole. Instead, NPM will be the only container that can proxy traffic through to itself on port 81. Then save the file and bring up the docker compose.

docker compose up -d

Your docker-compose.yml should look like this

version: "3"
services:
  npm:
    image: 'jc21/nginx-proxy-manager:latest'
    restart: unless-stopped
    ports:
      # These ports are in format <host-port>:<container-port>
      - '80:80' # Public HTTP Port
      - '443:443' # Public HTTPS Port
      # - '81:81' # Admin Web Port
      # Add any other Stream port you want to expose
      # - '21:21' # FTP
    expose:
      - '81'
    volumes:
      - ./data:/data
      - ./letsencrypt:/etc/letsencrypt

networks:
  default:
    name: nginx-proxy
    external: true

That’s it! Now you have NPM proxying itself with SSL enabled. In a later guide, we will add Cloudflare Firewall rules so that we can limit who can access your NPM admin site.

Continue with Part 6: How to set up multiple WordPress sites on Docker.