How to Install Nginx Proxy Manager (Docker & Ubuntu Guide) [2026]

Q: How to Install Nginx Proxy Manager (Docker & Ubuntu Guide) [2026]

To install Nginx Proxy Manager (NPM), the industry-standard method is using Docker Compose, which simplifies dependency management. First, ensure you have Docker and Docker Compose installed on your host. Then, create a `docker-compose.yml` file that defines the NPM service, mapping necessary ports (80, 443, 81) and attaching a persistent Docker volume to retain configuration data. Once deployed, access the web interface via port 81, log in with the default credentials (admin@example.com / chang

Question

Proxy Basics

How to Install Nginx Proxy Manager (Docker & Ubuntu Guide) [2026]

7 min read

Updated January 5, 2026

Share:

Accepted Answer

How to Install Nginx Proxy Manager: The Ultimate 2025 Guide

Nginx Proxy Manager (NPM) has become the de-facto standard for managing reverse proxies, particularly for those running complex scraping operations or self-hosted services. As a senior proxy expert, I prefer NPM over raw Nginx configurations because it abstracts away the complexity of SSL termination and Lua scripting, offering a GUI that drastically reduces configuration errors.

Prerequisites for Installation

Before deploying, ensure your server environment meets the following requirements:

1. Operating System: Ubuntu 20.04/22.04 LTS or Debian 11+ (Recommended) or a Proxmox LXC container. 2. Hardware: Minimum 1GB RAM (2GB recommended for high throughput), 10GB Disk space. 3. Networking: A public IP address with ports 80 and 443 open to the internet. 4. Dependencies: Docker Engine and Docker Compose (or Docker Compose V2).

---

Method 1: The Docker Compose Method (Recommended)

This is the most stable method for 2025. It ensures your configuration persists across updates and allows for easy portainer integration.

Step 1: Install Docker and Docker Compose

If you haven't already, execute the following commands on your Ubuntu/Debian server:

curl -sSL https://get.docker.com | sh sudo usermod -aG docker $USER Log out and back in for group changes to take effect

Step 2: Create the Directory Structure

Organization is key for managing multiple proxies. Create a dedicated directory for your NPM instance and the data volume.

mkdir -p npm/data

mkdir -p npm/letsencrypt

Step 3: Configure docker-compose.yml

Navigate into your npm directory and create the configuration file.

cd npm

nano docker-compose.yml

Paste the following optimized configuration. This setup uses the official jc21/nginx-proxy-manager image and maps the necessary ports.

version: '3.8' services: app: image: 'jc21/nginx-proxy-manager:latest' restart: unless-stopped ports: - '80:80' # Public HTTP Port - '443:443' # Public HTTPS Port - '81:81' # Admin Web Port environment: # These are the default settings: DB_SQLITE_FILE: "/data/database.sqlite" # For high availability, you can switch to MySQL: # DB_MYSQL_HOST: "db" # DB_MYSQL_USER: "npm" # DB_MYSQL_PASSWORD: "npm" # DB_MYSQL_NAME: "npm" volumes: - ./data:/data - ./letsencrypt:/etc/letsencrypt # Uncomment if you want to map custom Nginx config files # - ./custom:/custom # networks: # - proxy-tier

# Optional: MariaDB Database Container # db: # image: 'jc21/mariadb-aria:10.11' # restart: unless-stopped # environment: # MYSQL_ROOT_PASSWORD: 'npm' # MYSQL_DATABASE: 'npm' # MYSQL_USER: 'npm' # MYSQL_PASSWORD: 'npm' # volumes: # - ./mysql:/var/lib/mysql

Step 4: Deploy the Container

Run the following command to pull the image and start the service in detached mode.

docker compose up -d

Step 5: Initial Login

1. Open your browser and navigate to http://:81. 2. Default Email: admin@example.com 3. Default Password: changeme 4. Immediate Action: Change your password immediately to secure your proxy dashboard.

---

Method 2: Installation via Portainer

If you prefer managing your Docker infrastructure through a GUI (Portainer), the process is streamlined for container management.

1. Log in to your Portainer instance. 2. Select Stacks -> Add Stack. 3. Name the stack nginx-proxy-manager. 4. In the Editor, paste the YAML content provided in Method 1. 5. Click Deploy the stack.

*Note: When using Portainer, ensure you have mapped the volumes correctly within the Portainer UI so your data survives container recreations.*

---

Method 3: Native Installation (Ubuntu/Debian)

*Warning: This method is harder to maintain and update. Only use this if you cannot use Docker.*

1. Install Dependencies:

sudo apt update

sudo apt install nginx nodejs npm git

2. Clone the Repo and Build: NPM requires a specific build process. The Docker method is preferred because the native installation involves managing Node.js versions and background services (PM2) manually.

git clone https://github.com/NginxProxyManager/nginx-proxy-manager.git

cd nginx-proxy-manager npm install npm run build

*For the sake of stability, I strongly recommend sticking to Method 1 (Docker).*

---

Expert Configuration: Proxy Hosts & SSL

Once logged in, follow these steps to set up a reverse proxy, which is the core use case for web scrapers and proxy managers.

Creating a Proxy Host

1. Navigate to Hosts -> Proxy Hosts. 2. Click Add Proxy Host. 3. Domain Names: Enter your domain (e.g., scrape-proxy.yourdomain.com). 4. Scheme: http 5. Forward Hostname/IP: The internal IP address of your scraping target (e.g., 192.168.1.50). 6. Forward Port: 8080 (or the port your target application is running on).

SSL Certificates (Let's Encrypt)

NPM automates this via ACME.

1. In the SSL tab of the Proxy Host, select Request a new SSL Certificate. 2. Select Force SSL (This redirects HTTP to HTTPS). 3. Select HTTP-01 or DNS-01 challenge. *Pro Tip: Use DNS-01 if you are managing internal APIs that aren't public yet, or if you want wildcard certificates.* 4. Agree to the Terms of Service and click Save.

Python Integration for Scrapers

When using NPM as a gateway for your scraping stack, you point your Python requests to the NPM IP. Here is a Python snippet utilizing the requests library, assuming NPM is routing traffic to your internal rotating proxy service:

import requests
The URL you set up in Nginx Proxy Manager
proxy_url = "http://scrape-proxy.yourdomain.com"
target_url = "https://httpbin.org/ip"
try: # We are routing our request THROUGH the NPM gateway response = requests.get(target_url, proxies={ "http": proxy_url, "https": proxy_url }, timeout=10)
print(f"Status Code: {response.status_code}") print(f"Response Body: {response.text}")
except requests.exceptions.ProxyError as e: print("Proxy Connection Error:", e)

Comparison: NPM vs. Standard Nginx

As a senior expert, I often get asked why not just edit nginx.conf. Below is a comparison to illustrate why NPM is superior for management.

Troubleshooting Common Issues

1. 502 Bad Gateway: This usually means NPM cannot reach your backend container. Check your internal IP addresses and ensure they are on the same Docker network. 2. Port 80 Already in Use: If Apache is running on your host, you must stop it (sudo systemctl stop apache2) before NPM can bind to port 80. 3. SSL Failures: Ensure port 80 is open to the public, as Let's Encrypt uses port 80 for the HTTP-01 challenge validation, even if you are requesting an HTTPS certificate.

Conclusion

Installing Nginx Proxy Manager via Docker is the most efficient way to manage your reverse proxy needs in 2025. It provides a robust, secure, and scalable solution for routing traffic to your web scrapers, self-hosted apps, or internal APIs. By utilizing the Docker Compose method, you ensure that your configuration is portable and resilient to host updates.