- Description
- Reference API
- Prerequisites
- Installation
- Settings
- Usage
- Options
- Examples
- Important Notice
- TODO
Warning
The --restore command is disabled (a fix is in progress).
Check the latest release with major improvements and fixes.
π οΈ This script allows you to efficiently manage Nginx Proxy Manager via its API. It provides advanced features such as proxy host creation, user management, and configuration display, while also integrating a backup system (BACKUP) with a user-friendly interface.
It simplifies task automation, including proxy creation, SSL certificate management, and full reverse proxy administration.
π Automatically generates and manages tokens, ensuring their validity, so you don't have to worry about token expiration.
French description:
Ce script permet de gérer Nginx Proxy Manager via son API de manière simple et efficace. Il offre des fonctionnalités avancées telles que la création de hosts proxy, la gestion des utilisateurs et l'affichage des configurations, tout en intégrant un système de sauvegarde (BACKUP) avec une interface conviviale.Il facilite l'automatisation des tÒches courantes, comme l'ajout de proxies, la gestion des certificats SSL et l'administration complète de vos reverse proxies.
https://github.com/NginxProxyManager/nginx-proxy-manager/tree/develop/backend/schema
Required basic dependencies.
The script will automatically check if they are installed and will download them if necessary:curl
jq
wget https://raw.githubusercontent.com/Erreur32/nginx-proxy-manager-Bash-API/main/npm-api.sh
chmod +x npm-api.sh
# Run the script.
./npm-api.sh
Important
(Optional) You can create a configuration file named npm-api.conf
with these 4 required variables.
To ensure the script is functional, edit these 4 variables (mandatory).
# npm-api.conf
## Nginx proxy IP address (your Nginx IP/port)
NGINX_IP="127.0.0.1"
NGINX_PORT="81"
## Existing user (user and password) on NPM
API_USER="admin@example.com"
API_PASS="changeme"
# Optional (only if you want in other /path than script directory)
# DATA_DIR="/path/nginx_backup/dir"
./npm-api.sh [OPTIONS]
./npm-api.sh --help
./npm-api.sh --show-default
Options available: (see --examples for more details)
-y Automatic yes prompts!
--info Display Script Variables Information
--show-default Show Default settings for host creation
--check-token Check Check current token info
--backup πΎ Backup All configurations to a different files in $DATA_DIR
Proxy Host Management:
ββββββββββββββββββββββββββββββββββββββββ
--host-search domain Search Proxy host by domain name
--host-list List All Proxy hosts (to find ID)
--host-show π Show Full details for a specific host by ID
--host-create domain -i forward_host -p forward_port [options]
Required:
domain Domain name (required)
-i forward-host IP address or domain name of the target server (required)
-p forward-port Port of the target server (required)
optional: (Check default settings,no argument needed if already set!)
-f FORWARD_SCHEME Scheme for forwarding (http/https, default: http)
-c CACHING_ENABLED Enable caching (true/false, default: false)
-b BLOCK_EXPLOITS Block exploits (true/false, default: true)
-w ALLOW_WEBSOCKET_UPGRADE Allow WebSocket upgrade (true/false, default: true)
-l CUSTOM_LOCATIONS Custom locations (JSON array of location objects)
-a ADVANCED_CONFIG Advanced configuration (string)
--host-enable π Enable Proxy host by ID
--host-disable π Disable Proxy host by ID
--host-delete π Delete Proxy host by ID
--host-update π [field]=value Update One specific field of an existing proxy host by ID
(eg., --host-update 42 forward_host=foobar.local)
--host-acl-enable π access_list_id Enable ACL for Proxy host by ID with Access List ID
--host-acl-disable π Disable ACL for Proxy host by ID
--host-ssl-enable π [cert_id] Enable SSL for host ID optionally using specific certificate ID
--host-ssl-disable π Disable SSL, HTTP/2, and HSTS for a proxy host
--cert-list List ALL SSL certificates
--cert-show domain Or π List SSL certificates filtered by [domain name] (JSON)
--cert-delete domain Or π Delete Certificate for the given 'domain'
--cert-generate domain [email] Generate Let's Encrypt Certificate or others Providers.
β’ Standard domains: example.com, sub.example.com
β’ Wildcard domains: *.example.com (requires DNS challenge)
β’ DNS Challenge: Required for wildcard certificates
- Format: dns-provider PROVIDER dns-api-key KEY
- Providers: dynu, cloudflare, digitalocean, godaddy, namecheap, route53, ovh, gcloud, ...
--user-list List All Users
--user-create username password email Create User with a username, password and email
--user-delete π Delete User by username
--access-list List All available Access Lists (ID and Name)
--access-list-show π Show detailed information for specific access list
--access-list-create Create Access Lists with options:
β’ --satisfy [any|all] Set access list satisfaction mode
β’ --pass-auth [true|false] Enable/disable password authentication
β’ --users "user1,user2" List of users (comma-separated)
β’ --allow "ip1,ip2" List of allowed IPs/ranges
β’ --deny "ip1,ip2" List of denied IPs/ranges
--access-list-delete π Delete Access List by access ID
--access-list-update π Update Access List by access ID with options:
β’ --name "new_name" New name for the access list
β’ --satisfy [any|all] Update satisfaction mode
β’ --pass-auth [true|false] Update password authentication
β’ --users "user1,user2" Update list of users
β’ --allow "ip1,ip2" Update allowed IPs/ranges
β’ --deny "ip1,ip2" Update denied IPs/ranges
βββββββββββββββββββββββββββββββββββββββββ
--examples π Examples commands, more explicits
--help π It's me
π¦ Backup First !
./npm-api.sh --backup
π Host Creation:
# Basic host creation
./npm-api.sh --host-create domain.com -i IP -p PORT [-b true/false] [-c true/false] [-w true/false] [-h true/false]
# Create host with SSL certificate and enable SSL (all-in-one)
./npm-api.sh --host-create domain.com -i IP -p PORT [options] --cert-generate --host-ssl-enable -y
# Create host with SSL certificate and enable SSL (with specific domain)
./npm-api.sh --host-create domain.com -i IP -p PORT [options] --cert-generate domain.com --host-ssl-enable -y
# Create host with custom options
./npm-api.sh --host-create example.com -i 192.168.1.10 -p 8080 \
-f https \ # Forward scheme
-b true \ # Block exploits
-c true \ # Enable caching
-w true \ # Enable websocket
-h true \ # Enable HTTP/2
-y # Auto confirm
π€ Automatic operations (no prompts):
./npm-api.sh --host-create example.com -i 192.168.1.10 -p 8080 -y
./npm-api.sh --host-delete 42 -y
./npm-api.sh --host-ssl-enable 10 -y
π Information and Status:
./npm-api.sh --info # Show configuration and dashboard
./npm-api.sh --show-default # Show default settings
./npm-api.sh --check-token # Verify token validity
./npm-api.sh --host-search domain.com # Search for a specific domain
./npm-api.sh --host-list # List all hosts
./npm-api.sh --host-list-full # List hosts with details
./npm-api.sh --host-show 42 # Show specific host details
π SSL Management:
# List all certificates
./npm-api.sh --list-ssl-cert
# Generate standard Let's Encrypt certificate
./npm-api.sh --cert-generate domain.com [email] [dns_provider] [dns_credentials] [-y]
# Generate wildcard certificate with Cloudflare
./npm-api.sh --cert-generate "*.example.com" \
--cert-email admin@example.com \
--dns-provider cloudflare \
--dns-credentials '{"dns_cloudflare_email":"your@email.com","dns_cloudflare_api_key":"your_api_key"}'
# Delete certificate
./npm-api.sh --delete-cert domain.com
# Enable SSL for host
./npm-api.sh --host-ssl-enable HOST_ID
# Generate certificate and enable SSL for existing host
./npm-api.sh --cert-generate domain.com --host-ssl-enable -y
π Complete Examples with Wildcard Certificates:
# Create host with wildcard certificate using Cloudflare DNS
./npm-api.sh --host-create "*.example.com" -i 192.168.1.10 -p 8080 \
--cert-generate "*.example.com" \
--cert-email admin@example.com \
--dns-provider cloudflare \
--dns-credentials '{"dns_cloudflare_email":"your@email.com","dns_cloudflare_api_key":"your_api_key"}' \
--host-ssl-enable -y
# Same with DigitalOcean DNS
./npm-api.sh --host-create "*.example.com" -i 192.168.1.10 -p 8080 \
--cert-generate "*.example.com" \
--cert-email admin@example.com \
--dns-provider digitalocean \
--dns-credentials '{"dns_digitalocean_token":"your_token"}' \
--host-ssl-enable -y
# Same with GoDaddy DNS
./npm-api.sh --host-create "*.example.com" -i 192.168.1.10 -p 8080 \
--cert-generate "*.example.com" \
--cert-email admin@example.com \
--dns-provider godaddy \
--dns-credentials '{"dns_godaddy_key":"your_key","dns_godaddy_secret":"your_secret"}' \
--host-ssl-enable -y
π‘οΈ Access Control Lists:
# List all access lists
./npm-api.sh --list-access
# Show detailed information for specific access list
./npm-api.sh --access-list-show 123
# Create a basic access list
./npm-api.sh --access-list-create "office" --satisfy any
# Create access list with authentication
./npm-api.sh --access-list-create "secure_area" --satisfy all --pass-auth true
# Create access list with users
./npm-api.sh --access-list-create "dev_team" --users "john,jane,bob" --pass-auth true
# Create access list with IP rules
./npm-api.sh --access-list-create "internal" --allow "192.168.1.0/24" --deny "192.168.1.100"
# Create comprehensive access list
./npm-api.sh --access-list-create "full_config" \
--satisfy all \
--pass-auth true \
--users "admin1,admin2" \
--allow "10.0.0.0/8,172.16.0.0/12" \
--deny "10.0.0.50,172.16.1.100"
# Update an existing access list
./npm-api.sh --access-list-update 42
# Delete an access list (with confirmation)
./npm-api.sh --access-list-delete 42
# Delete an access list (skip confirmation)
./npm-api.sh --access-list-delete 42 -y
# Enable ACL for a host
./npm-api.sh --host-acl-enable 42,5 # Enable ACL ID 5 for host 42
# Disable ACL for a host
./npm-api.sh --host-acl-disable 42 # Disable ACL for host 42
π₯ User Management:
./npm-api.sh --create-user newuser password123 user@example.com
./npm-api.sh --delete-user 'username'
./npm-api.sh --list-users
π§ Advanced Examples:
# Custom Nginx configuration
./npm-api.sh --host-create example.com -i 192.168.1.10 -p 8080 \
-a 'proxy_set_header X-Real-IP $remote_addr;'
π‘οΈ Custom locations:
./npm-api.sh --host-create example.com -i 192.168.1.10 -p 8080 \
-l '[{"path":"/api","forward_host":"192.168.1.11","forward_port":8081}]'
# Update specific fields
./npm-api.sh --update-host 42 forward_scheme=https
./npm-api.sh --update-host 42 forward_port=8443
π Full options:
./npm-api.sh --host-create example.com -i 192.168.1.10 -p 8080 \
-f https -c true -b true -w true \
-a 'proxy_set_header X-Real-IP $remote_addr;' \
-l '[{"path":"/api","forward_host":"192.168.1.11","forward_port":8081}]'
./npm-api.sh --backup
# Full backup of all configurations
./npm-api.sh --backup
# This will create a backup in the following structure:
π data/
βββ π backups/
βββ π [IP]_[PORT]/
βββ π .access_lists/ # Access list configurations
βββ π .Proxy_Hosts/ # All proxy host configurations
β βββ π [DOMAIN]/ # Directory for each domain
β β βββ π logs/ # Log directory
β β βββ π ssl/ # SSL directory
β β β βββ π certificate_meta.json # Certificate metadata
β β β βββ π certificate.pem # Certificate
β β β βββ π chain.pem # Chain of certificates
β β β βββ π private.key # Private key
β β βββ π nginx.conf # Nginx configuration
β β βββ π proxy_config.json # Proxy configuration
β βββ π all_hosts_[DATE].json # List of all hosts
β βββ π all_hosts_latest.json # Symlink to latest backup
βββ π .settings/ # NPM settings
βββ π .ssl/ # SSL certificates
βββ π .user/ # User configurations
βββ π full_config.json # Complete backup file
βββ π token/
βββ π token.txt # Authentication token
βββ π expiry.txt # Token expiry date
-
Proxy Hosts (
/.Proxy_Hosts/
)- Individual host configurations
- Nginx configurations
- Complete host list with timestamps
-
SSL Certificates (
/.ssl/
)- Certificates and private keys
- Certificate metadata
- Chain certificates
-
Access Lists (
/.access_lists/
)- Access list configurations
- Client authorizations
- Access rules
-
Users (
/.user/
)- User accounts
- Permissions
- Authentication settings
-
Settings (
/.settings/
)- Global NPM settings
- System configurations
- Default parameters
The token/
directory contains:
- Authentication tokens
- Token expiry information
- One file per NPM instance
The --host-update
command allows you to update specific fields of an existing proxy host in Nginx Proxy Manager without recreating it.
Simply specify the proxy host ID and the field you want to update, like this:
./npm-api.sh --update-host 42 forward_host=new.backend.local
Field Name | Type | Description |
---|---|---|
domain_names |
array |
List of domains handled by this proxy. |
forward_host |
string |
The destination (backend) hostname or IP. |
forward_port |
integer |
The destination port (e.g., 8000 , 443 ). |
forward_scheme |
string |
The scheme: http or https . |
enabled |
boolean |
Whether the proxy is enabled (true or false ). |
ssl_forced |
boolean |
Redirect all HTTP requests to HTTPS. |
certificate_id |
integer |
The ID of the SSL certificate to use. |
meta.letsencrypt_agree |
boolean |
Agree to Let's Encrypt TOS (true or false ). |
meta.dns_challenge |
boolean |
Use DNS challenge for SSL cert (true or false ). |
allow_websocket_upgrade |
boolean |
Enable WebSocket support (true or false ). |
http2_support |
boolean |
Enable HTTP/2 (true or false ). |
caching_enabled |
boolean |
Enable caching (true or false ). |
block_exploits |
boolean |
Block known exploits (true or false ). |
advanced_config |
string |
Custom Nginx directives (multiline string). |
locations |
array |
Custom location blocks (advanced use). |
Some info of settings in the script with ./npm-api.sh --info
./npm-api.sh --info
π Checking system dependencies and directories...
β
All dependencies and directories are properly set up
βββ System tools: OK
βββ Directories : OK
βββ Permissions : OK
π Checking token validity...
β
Token is valid
π
Expires: 2026-03-14T10:24:56.267Z
Script Info: 3.0.0
Script Variables Information:
Config : /home/tools/Project/nginx_proxy/npm-api.conf
BASE URL : http://127.0.0.1:8099/api
NGINX IP : 127.0.0.1
USER NPM : user@mail.com
BACKUP DIR : /home/tools/Project/nginx_proxy/data/127_0_0_1_8099
π Backup Locations:
β’ Backup: /home/tools/Project/nginx_proxy/data/127_0_0_1_8099/backups
β’ Token: /home/tools/Project/nginx_proxy/data/127_0_0_1_8099/backups/token/
π NGINX - Proxy Manager - Dashboard π§
βββββββββββββββββββββββββββββββββββββββ
βββββββββββββββββββ¬ββββββββββ
β COMPONENT β STATUS β
βββββββββββββββββββΌββββββββββ€
β π Proxy Hosts β 11 β
β ββ Enabled β 9 β
β ββ Disabled β 2 β
βββββββββββββββββββΌββββββββββ€
β π Redirections β 1 β
β π Stream Hosts β 0 β
βββββββββββββββββββΌββββββββββ€
β π Certificates β 1 β
β ββ Valid β 1 β
β ββ Expired β 0 β
βββββββββββββββββββΌββββββββββ€
β π Access Lists β 1 β
β ββ Clients β 0 β
βββββββββββββββββββΌββββββββββ€
β π₯ Users β 3 β
βββββββββββββββββββΌββββββββββ€
β β±οΈ Uptime β 2 days β
β π¦ NPM Version β 2.12.3 β
βββββββββββββββββββ΄ββββββββββ
π‘ Use --help to see available commands
Check --examples for more help examples
By following these steps, you can enable SSL for your proxy host for the first time using Let's Encrypt.
List all Host in one command and show Β΄idΒ΄ , Β΄statusΒ΄ and Β΄SSLΒ΄ status:
./npm-api.sh --host-list
π List of proxy hosts (simple)
ID Domain Status SSL Certificate Domain
14 example.com enabled β
15 example.titi enabled β
1 domain.com disable 8 domain.com
11 titi.eu enabled β
12 toutou disable β
13 toutoux enabled β
Assuming the host ID is 1, you would enable SSL for the host as follows:
./npm-api.sh --host-ssl-enable 1
Host proxy info command --host-show id
./npm-api.sh --host-show 1
π Full details for proxy host ID: 59...
{
"id": 10,
"created_on": "2024-07-11 13:16:34",
"modified_on": "2024-07-13 09:42:40",
"owner_user_id": 1,
"domain_names": [
"test.domain.com"
],
"forward_host": "127.0.0.1",
"forward_port": 80,
"access_list_id": 0,
"certificate_id": 81,
"ssl_forced": 1,
"caching_enabled": 0,
"block_exploits": 1,
"advanced_config": "",
"meta": {
"letsencrypt_agree": true,
"letsencrypt_email": "",
"nginx_online": true,
"nginx_err": null
},
"allow_websocket_upgrade": 1,
"http2_support": 1,
"forward_scheme": "http",
"enabled": 1,
"locations": [],
"hsts_enabled": 1,
"hsts_subdomains": 0
}
We have performed a force push (git push --force
) on this repository to remove sensitive data from the history. As a result, the commit history has been rewritten, and your local copy may be out of sync.
π οΈ What You Need to Do? To avoid any issues, please follow these steps to update your local repository:
git fetch --all
git reset --hard origin/main # Replace 'main' with your branch name if different
If you have local changes that you don't want to lose, consider making a backup before running these commands.
β Why Was This Done? This action was necessary to remove sensitive data from the repository's history and ensure better security.
- add setting for ADVANCED configuration in npm
location / { ... }
- Add documentation on certain functions
- ADD: a configuration function for Custom Locations
- Backup all settings from NPM
- Add automatic confirmation with -y parameter
- Clean/minimize output when using -y parameter for better script integration
- Creation of ACCESS list through CLI
- Restore Function not working properly, need to find FIX
Special thanks to:
-
@ichbinder for implementing the
-y
parameter for automatic confirmations -
π Special thanks to zafar-2020 for his valuable help with testing and reporting issues during the development of version 3.0.0!
MIT License - see the LICENSE.md file for details