Self-host Nginx Proxy Manager with Levelrail
A web UI for managing Nginx reverse-proxy hosts, redirects, and Let's Encrypt certificates.
- AuthorNginxProxyManager
- LicenceMIT
- Memory256 MiB
- Archarm64
- Services1
How to self-host Nginx Proxy Manager
-
Pull the images
One image is pulled on your server.
Show images
jc21/nginx-proxy-manager:2.12.3
-
Create the app
One service starts in a single Compose app, with 2 named volume mounts for your data, on port 81.
-
Fill in the secrets
1 setting is preset, you do not have to fill in anything.
-
Open it
Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.
Nginx Proxy Manager requirements
- Memory
- About 256 MiB
- Architectures
- amd64 image published, arm64 image published
- Ports
- 81
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- MIT, permissive license
- Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.
- Host ports. It publishes port 81 on the host, so open them in the VPS firewall only if you want that.
Install Levelrail first
On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then Nginx Proxy Manager. New to Levelrail? Install it on a fresh VPS first.
docker pull ghcr.io/glincker/levelrail:latest Then levelrail-cli login --device. See Getting started and the Nginx Proxy Manager docs page.
Deploy Nginx Proxy Manager your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy Nginx Proxy Manager from the CLI
levelrail-cli templates deploy nginx-proxy-manager --name my-nginx-proxy-manager Deploy Nginx Proxy Manager with the API
curl -X POST -H "Authorization: Bearer $TOKEN" \
https://levelrail.example.com/api/v1/service-templates/nginx-proxy-manager/deploy Nginx Proxy Manager configuration
Nginx Proxy Manager services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| npm | jc21/nginx-proxy-manager:2.12.3 | 81 | npm_data -> /datanpm_letsencrypt -> /etc/letsencrypt |
Nginx Proxy Manager environment variables
| Variable | Service | Value |
|---|---|---|
| DB_SQLITE_FILE | npm | Preset by the template |
Ports and volumes
- Ports
- 81
- Volumes
- 2 named mounts: npm_data -> /data, npm_letsencrypt -> /etc/letsencrypt
Nginx Proxy Manager FAQ
How much memory does Nginx Proxy Manager need?
The catalog lists about 256 MiB of memory for Nginx Proxy Manager.
Does Nginx Proxy Manager run on arm64?
For Nginx Proxy Manager, an arm64 image is published; amd64 is image published.
What licence is Nginx Proxy Manager under?
Nginx Proxy Manager is licensed under MIT, which is permissive, with few conditions on reuse.
Does Nginx Proxy Manager need configuration before it starts?
No. The template fills in its own defaults.
Which ports does Nginx Proxy Manager use?
Nginx Proxy Manager listens on port 81 inside the stack.
Where does Nginx Proxy Manager keep its data?
In named volumes: npm_data mounted at /data and npm_letsencrypt mounted at /etc/letsencrypt.
Can I deploy Nginx Proxy Manager on Dokploy or Dokku?
The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list we compared does not have an entry with the same id for Nginx Proxy Manager, so on Dokploy you would use a Docker Compose application with the file from this page. Dokku deploys container images with its own commands, so the pinned image jc21/nginx-proxy-manager:2.12.3 is what you deploy there.