Why use Nginx Proxy Manager on a VPS?
Nginx Proxy Manager provides a browser interface for proxy hosts, certificates, access lists and related Nginx configuration. It is useful when you run several applications and want to manage their public hostnames from one place. Explore the official project.
Route a hostname
Point each application domain at the reverse proxy and select the service that should receive its requests.
Manage HTTPS
Request a certificate, check its status and choose the HTTPS settings for each proxy host.
Review access
Keep administration private and configure application authentication and access policies around the service you publish.
Version 2.17.1 was released on 19 November 2026. It updates the OpenResty base with backported nginx2root fixes and corrects SSL toggles being reset while requesting a certificate during host creation. This walkthrough pins that release. Read the release notes.
Choose a VPS and check the ports
Our starting recommendation for a few modest applications is about 2 vCPU and 2 GB RAM. This is HYEHOST sizing guidance. Allow additional resources for the applications themselves, and monitor memory, connections, logs and transfer as use grows.
Use a current Ubuntu LTS VPS with Docker Engine, the Compose plugin and SSH access. Your administrator needs permission to run Docker commands and use sudo. This example uses SQLite and a sample Nginx container on the same Docker host.
Prepare a subdomain such as app.example.com. Ports 80 and 443 must be available for Nginx Proxy Manager. Check existing listeners before starting the stack, especially if this server already runs another web server.
docker version
docker compose version
sudo ss -ltnp
1. Prepare the deployment directory
Create a dedicated directory for a fresh installation. Restrictive directory permissions help protect its database, account information and certificate keys.
umask 077
mkdir -p ~/nginx-proxy-manager/data
mkdir -p ~/nginx-proxy-manager/letsencrypt
cd ~/nginx-proxy-manager
The two persistent directories retain the application database and certificate material when you replace the container. Keep them together in your recovery plan. Review the official deployment layout.
2. Start the proxy and a sample application
Save this as compose.yaml. Public traffic enters ports 80 and 443. Administration binds to the VPS loopback address. The demo service is reached through the Compose network.
services:
app:
image: jc21/nginx-proxy-manager:2.17.1
restart: unless-stopped
ports:
- "80:80"
- "443:443"
- "127.0.0.1:81:81"
environment:
TZ: Etc/UTC
volumes:
- ./data:/data
- ./letsencrypt:/etc/letsencrypt
healthcheck:
test: ["CMD", "/usr/bin/check-health"]
interval: 10s
timeout: 3s
retries: 6
start_period: 60s
demo:
image: nginx:stable-alpine
restart: unless-stopped
The health command is supplied by Nginx Proxy Manager. Services in the same Docker network can use their service names as hostnames, which makes demo the upstream address for this exercise. Review health checks and Docker networking.
docker compose config --quiet
docker compose pull
docker compose up -d
docker compose ps
docker compose logs --tail=100 app
Allow time for the initial database setup and key generation. Check the application becomes healthy. Use a current Docker Engine and retain the explicit loopback binding for port 81. Review Docker port publishing.
3. Open administration through SSH
On your computer, open the following tunnel using your VPS connection details. Keep the terminal open and visit http://localhost:8181.
ssh -N -L 8181:127.0.0.1:81 admin@YOUR_VPS_IP
Complete the first-run setup with your name, an email address you control and a unique password, then choose Save. Verify that you can sign out and sign back in, and store the credentials in your password manager. Review the current setup screen.
The SSH connection provides access to the local administration port. Continue managing the proxy through this route and review any additional administrator accounts you create.
4. Point DNS at your VPS
Create an A record for app.example.com with the VPS IPv4 address. Add an AAAA record when you have verified IPv6 connectivity to this stack. Replace the example hostname throughout these instructions.
Allow inbound TCP 80 and 443 through the applicable firewalls, and restrict SSH to your administrators. Check the hostname resolves to the intended server from an external connection. If you use a CDN, establish a clear direct path for the initial hostname and certificate checks before adding its proxy configuration.
5. Add your first proxy host
In Nginx Proxy Manager, open Hosts, then Proxy Hosts, then Add Proxy Host. In the Details tab, set the following values and save. Review the current proxy-host fields.
Domain Names
app.example.com
Scheme and hostname
Choose http and enter demo as Forward Hostname / IP.
Forward Port
Enter 80, the sample application's container port.
Open the HTTP hostname from an external browser. The sample Nginx welcome page confirms that the domain reaches the proxy and that the proxy can reach its upstream. This tests the public route through both the proxy and upstream.
For your own application, replace the sample upstream with its service name and internal port. Configure features such as WebSocket support and access policies according to that application's requirements. For applications on separate HYEHOST VMs, use the intended regional private LAN and verify reachability and firewall rules between those VMs. Explore private networking between VPS instances.
6. Issue and verify an HTTPS certificate
Edit the proxy host and open its SSL tab. Choose Request a new Certificate, supply the requested contact details, accept the Let's Encrypt terms and save. For this single-hostname example, use the normal HTTP validation path with public port 80 reachable. Review certificate validation.
After issuance, reopen the SSL tab, select the issued certificate and enable Force SSL. Save again and confirm the setting persists. Visit the HTTPS hostname and inspect the certificate name and browser connection status.
curl -I http://app.example.com
curl -I https://app.example.com
The HTTP request should redirect to HTTPS and the HTTPS request should reach the sample application. Check certificate status and renewal behaviour as part of ongoing operation. Nginx Proxy Manager uses Certbot for Let's Encrypt issuance and renewal. Review the certificate tooling.
Back up the proxy database and certificates
A recovery copy needs the Compose file, data and letsencrypt directories. For this SQLite deployment, stop the proxy while copying them. This interrupts every application using it, so choose a maintenance window.
Save the following as backup-proxy.sh in the deployment directory and run bash backup-proxy.sh. The archive contains private keys and account state, so retain encrypted copies off-server and test an isolated restore.
#!/usr/bin/env bash
set -e
cd "$HOME/nginx-proxy-manager"
umask 077
backup_dir="$HOME/proxy-backups"
mkdir -p "$backup_dir"
archive_path=$(mktemp "$backup_dir/proxy-XXXXXXXX")
sudo -v
resume_proxy() {
backup_status=$?
trap - EXIT
if ! docker compose start app; then
printf '%s\n' 'Proxy restart failed. Review its logs.' >&2
if [ "$backup_status" -eq 0 ]; then
backup_status=1
fi
fi
exit "$backup_status"
}
trap resume_proxy EXIT
docker compose stop app
sudo tar -czf - compose.yaml data letsencrypt > "$archive_path"
printf 'Backup archive created at %s\n' "$archive_path"
The exit handler attempts to restart the proxy after success or failure and preserves a failed backup's exit status. Check both script completion and service health before ending maintenance.
Apply updates and check certificate integrations
Before updating an existing deployment, record the running image tag, read the target release notes and create a verified backup. Update the pinned image in Compose, then pull and recreate the proxy. This can briefly interrupt proxied traffic.
docker compose config --quiet
docker compose pull app
docker compose up -d app
docker compose ps
docker compose logs --tail=100 app
Nginx Proxy Manager performs database updates during its upgrade process. If recovery requires the previous version, use a compatible pre-upgrade backup. Check representative applications, administrator login, redirects and certificates afterward. Review the upgrade workflow.
The current release updates Certbot. DNS challenge plugins have their own dependencies, and combinations of providers can produce Python package conflicts. Existing DNS-challenge users should review their provider plugin and logs and verify issuance and renewal with a suitable test certificate before depending on the updated integration. Review DNS plugin compatibility.
Common proxy setup problems
The proxy cannot start
Check whether another service owns port 80 or 443. Review Compose status, application logs and permissions on the persistent directories.
The proxy returns a 502
Check the upstream service name, scheme, port and Docker network. Confirm the sample container is running and reachable from the proxy.
Certificate validation fails
Check public DNS, both address families, port 80 and any CDN or firewall in the request path. Inspect the certificate request error before retrying.
Use a specific hostname and timestamp when reading the logs. Change one setting at a time and check the result through the same route your users take. Follow the 502 troubleshooting guide.
Nginx Proxy Manager VPS FAQ
Which ports does Nginx Proxy Manager use?
This setup publishes ports 80 and 443 for web traffic. Admin port 81 is bound to the VPS loopback address and reached through an SSH tunnel on local port 8181.
What do I enter as the Forward Hostname in Docker?
Use the upstream service name when the application and Nginx Proxy Manager share a Docker network. In this guide, the demo service is reached as demo on port 80.
Why does my proxy host return 502 Bad Gateway?
Check that the upstream is running and reachable from the proxy container. Confirm its service name, port, scheme and shared Docker network, then inspect the proxy and application logs.
What should I back up before updating Nginx Proxy Manager?
For this SQLite deployment, stop the proxy briefly and archive the Compose file, data directory and letsencrypt directory together. Protect the certificate private keys in those copies and test recovery in an isolated environment.
Why use Nginx Proxy Manager 2.17.1 in this guide?
Version 2.17.1 was released on 19 November 2026 with an updated OpenResty base containing backported security fixes. Existing deployments should review its release notes and check any Certbot DNS plugins during the update.
Can I use Nginx Proxy Manager for several applications on one VPS?
Yes. Create a proxy host for each domain or subdomain and route it to the intended application. Size the VPS for the combined workloads and keep each application's authentication and recovery plan in place.

