Reverse Proxy management using Nginx Proxy Manager

Managing proxy hosts can be tedious sometimes. By using so-called Nginx Proxy Manager, you can manage your proxy hosts easily and swiftly thanks to its user-friendly web interface.

However, NPM (Nginx Proxy Manager) currently does not support Load Balancing configuration. But, for basic proxying use cases, this is more than enough! So, let’s jump on to it, shall we?

TLDR Guide

1. Install docker-ce and docker-compose
2. Create new folder npm or nginxproxymanager or anything else.
3. Save these lines as docker-compose.yaml in the folder

version: '3'
services:
  app:
    image: 'jc21/nginx-proxy-manager:latest'
    restart: unless-stopped
    ports:
      - '80:80'
      - '81:81'
      - '443:443'
    volumes:
      - ./data:/data
      - ./letsencrypt:/etc/letsencrypt

4. Run the stack

docker-compose up -d

5. Access the admin UI via http://YOUR-IP:81 . Remember, it’s PORT 81.
6. Default credentials

Email:    admin@example.com
Password: changeme

7. Change the default login.
8. Enjoy!

Prerequisites

1. Port 80, 81, and 443 allowed on Firewall and Security Profile.
2. A domain name, at least.

Installation Steps

This installation guide would be OS-agnostic as this will run on any system with docker installed.

Assuming that docker-ce and docker-compose has been installed on your server. (Otherwise, check out this article and see only the docker installation part)

First, create a docker network with any name you wish:

docker network create proxy_network

Create a folder wherever you like and give it a name:

mkdir /opt/nginx_proxy
cd /opt/nginx_proxy

Then, save the following configuration as docker-compose.yaml :

version: '3'
services:
  app:
    image: 'jc21/nginx-proxy-manager:latest'
    restart: unless-stopped
    ports:
      - '80:80'
      - '81:81'
      - '443:443'
    volumes:
      - ./data:/data
      - ./letsencrypt:/etc/letsencrypt

networks:
  default:
    external:
      name: proxy_network

It’s a very basic configuration that will use SQLite as the database. So, if you wish to use MySQL/MariaDB instead, please use the following, and change the appropriate values:

version: '3'
services:
  app:
    image: 'jc21/nginx-proxy-manager:latest'
    restart: unless-stopped
    ports:
      - '80:80'
      - '81:81'
      - '443:443'
    volumes:
      - ./data:/data
      - ./letsencrypt:/etc/letsencrypt
    environment:
      DB_MYSQL_HOST: "DB_HOST"
      DB_MYSQL_PORT: DB_PORT
      DB_MYSQL_USER: "DB_USER"
      DB_MYSQL_PASSWORD: "DB_PASS"
      DB_MYSQL_NAME: "DB_NAME"

networks:
  default:
    external:
      name: proxy_network

Then, bring up the stack:

docker-compose up -d

Lastly, wait until the process is done.

Your NPM (Nginx Proxy Manager) should be accessible via http://YOUR_IP:81

Initial Setup

On the login page, enter the default NPM credentials as follows:

Email:    admin@example.com
Password: changeme

After successfully logged in, a dialog box will show up and it will let you change the default credentials.

Now, NPM is ready! Yay~

Adding your first proxy host

NPM offers 4 types of proxy passes. Basic proxy pass called Proxy Hosts, redirection hosts, proxy streaming, and 404 hosts. This article will only cover the Proxy Hosts section, and I leave it to you to discover the rest 😉

For your very first proxy host configuration, why don’t just proxy the NPM dashboard? Accessing it directly via IP:port is ugly! Now, let’s create it!

First, make sure you already create an A record for your domain/subdomain that points to this very server via your DNS manager. How to do it is depends on your registrar/domain name provider.

On the dashboard, click on the Proxy Hosts button. It should show something like this:

Click Add Proxy Host. And then, fill in the required fields as follows:

As the proxy host is located on the same machine, I prefer to put its private IP. Putting the public IP will work too. Make sure the forwarded port is 81. You also have some options whether you want to cache assets, enable WebSockets support, and block common exploits. Here, I will enable the Block Common Exploits.

Move forward to the SSL tab, unless you’re using Cloudflare SSL (which is automatically provided by default), you can use LetsEncrypt to generate a valid SSL certificate. And do not forget to enable the options you want.

If you’re using Cloudflare, do not enable Force SSL option as it will result in redirection loop.

Finally, click Save. Your Proxy Hosts page should now list your very first proxy host.

Now, the moment of truth. Try to access the URL:

Hooray, it is working.

Conclusion

That’s way too easy, right? Now, you’re able to deploy your own Nginx Proxy Manager using docker-compose and manage your proxy hosts using a dead-simple user interface.

for more IT knowledge, you can access it freely in Cloud Raya’s knowledge base and blog. Or, for real exciting experience you can also sign up in Cloud Raya and find what can you do in our dashborad.