Use Nginx Proxy Manager instead of Traefik
Nginx Proxy Manager (NPM) is a reverse proxy with a web page where you add each app by hand. Deployrr v6 lets you pick it instead of Traefik. This page shows how to pick it, install it, add an app, and switch back to Traefik.
For a short look at NPM in v6, watch Deployrr 6 overview: NGINX Proxy Manager at 3:43.
Before you start
Section titled “Before you start”- You have a Deployrr Plus or Pro license, the same as for Traefik. On Free or Basic, the install stops at a “License Required” box. See Licenses.
- Finish the steps in the Quick start, including Prerequisites with all steps done.
- Set Setup Mode to Hybrid (in Prerequisites). NPM needs it. Setup Mode is a toggle: each time you select it, it switches between Local and Hybrid. Check the box says “Hybrid mode ENABLED”.
- Own a domain and point its DNS records at your public IP. For one address per app, you’d usually add an A record for the domain and a wildcard record (
*.YOUR_DOMAIN). This is general advice; Deployrr doesn’t check DNS for NPM. - Ports 80 and 443 are free on your server. NPM always uses them. Traefik and NPM can’t run together.
- If Traefik is running, Deployrr stops it for you in the first section. It does not remove it.
What you give up compared to Traefik
Section titled “What you give up compared to Traefik”With NPM, you do this work in NPM’s own web page. Deployrr does not do it for you.
- No automatic addresses. While Traefik is stopped, Deployrr does not ask for a subdomain when you install an app and does not create a route. You add each app in NPM yourself.
- No Traefik menu tools. Entries such as Traefik Mode, Manage Exposure, Traefikify, Un-Traefikify, Domain Passthrough and Auth Bypass need Traefik.
- No Security menu login apps. Authelia, Authentik, Google OAuth, TinyAuth and Manage Auth need Traefik Production done and Traefik running (and a Pro license). With NPM you see a “Requirements Not Met” box that lists Traefik among other items. See Choose a login method for what they do.
- CrowdSec is untested with NPM. Traefik Bouncer needs Traefik, so it is blocked. CrowdSec and Firewall Bouncer are not blocked, but the NPM intro box says: “Middleware integration (Authelia, Authentik, CrowdSec) is NOT fully tested. Manual configuration may be required.” See Block bad visitors with CrowdSec.
If you want any of these, use Traefik instead. To understand how the two proxies differ, read UDMS part 18: Traefik vs Nginx Proxy Manager (manual setup, background only).
Pick NPM as your proxy type
Section titled “Pick NPM as your proxy type”- In Deployrr, open Proxy > Proxy Type (“Pick a Reverse Proxy”).
- Select NPM (“Simple Web UI based Nginx Proxy Manager”).
- Read the intro box. It ends with “Do you want to set NPM as your Proxy Type?”. Confirm.
- If you see a “Traefik Container Running” box, agree to stop it. The box says Traefik will be stopped but not removed.
- Read the output. If those entries are in your compose file, you see “Enabling npm.yml in compose file…” and “Disabling traefik.yml in compose file…”.
- If Deployrr stopped Traefik or changed the compose file, it ends with “Proxy Type set to: NPM”. Otherwise it goes straight back to the Proxy menu.
The Proxy Type line in the Proxy menu now ends with “- NPM”.
Install NPM
Section titled “Install NPM”- Open Proxy > NPM > Install (“Install Nginx Proxy Manager”).
- If you see a “License Required” box, you need a Plus or Pro license. If you see a “Requirements Not Met” box, fix what it lists, then start again. It lists missing Prerequisites or a Setup Mode that isn’t Hybrid.
- If you see “Proxy Type Required”, go back and do Pick NPM as your proxy type.
- If you see “Port Conflict - Cannot Install”, Traefik is still running. Stop or uninstall Traefik first.
- In the Port Configuration box, read “Enter the port for Nginx Proxy Manager (Admin web interface port):”. Deployrr suggests the first free port from 81. Press Enter to accept it, or type another port from 1 to 65535. If the port is invalid or in use, Deployrr says so and uses the suggested port. See Port already in use.
- Wait while the image downloads. Deployrr warns it “may take a few minutes”.
- Wait for “Nginx Proxy Manager installed successfully!”.
- Note the line “Access NPM Admin Panel: http://SERVER_IP:81”. It shows your server’s IP and the port you chose.
NPM also shows up on the Deployrr Dashboard, in the “Apps (Others)” section, if the Deployrr Dashboard is running.
If you run Install again later, an “Already Installed” box says reinstalling stops the container, recreates it with the latest image, and keeps your data. Proxy > NPM has only Install. It has no stop, start or uninstall entry.
Create your NPM admin account
Section titled “Create your NPM admin account”Do this right after the install. Until an admin account exists, NPM shows a setup screen to whoever opens the admin page first. Anyone who reaches that page before you can create the account and take over NPM.
- Open
http://SERVER_IP:81in your browser. ReplaceSERVER_IPwith your server’s local IP address. If you chose another port, use that port. - Create your admin account when NPM asks. Deployrr’s message says “On first access, you will be prompted to create your admin account.” Deployrr does not give you a default login. Use a strong password.
- Log in.
Keep the admin page off the internet
Section titled “Keep the admin page off the internet”The admin page controls every address and certificate NPM serves. Only you should be able to open it.
- At home: Don’t forward the admin port on your router. Only forward ports 80 and 443 to your server.
- On a VPS: The admin port is open on the server’s public IP. Docker publishes it past UFW, so a UFW rule doesn’t block it. Block the admin port in your provider’s firewall panel and allow only your SSH port, 80 and 443 from the internet. See Set the provider firewall. To open the admin page, use an SSH tunnel, for example
ssh -L 8181:localhost:81 YOUR_USER@SERVER_IP, then browse tohttp://localhost:8181. Use your admin port in place of81if you chose another one. - Don’t add a proxy host for the admin page itself unless you protect it with an access list in NPM.
Forward your router ports
Section titled “Forward your router ports”This is general router setup, not a Deployrr step.
- On your router, forward port 80 to port 80 on your Docker host.
- Forward port 443 to port 443 on your Docker host.
For VPS firewall problems, see Fix the UFW firewall on a VPS.
Add a proxy host for an app
Section titled “Add a proxy host for an app”These steps happen on NPM’s own screens. They come from NPM, not Deployrr, and NPM may change its labels in a new version.
- In NPM, open Hosts > Proxy Hosts.
- Select Add Proxy Host.
- In Domain Names, type the address you want, for example
sonarr.YOUR_DOMAIN. ReplaceYOUR_DOMAINwith your domain. - Set Scheme to
http. - In Forward Hostname / IP, type the app’s container name, for example
sonarr. - In Forward Port, type the app’s internal port, for example
8989. - Save the host.
Use the container name and internal port, joined as container-name:internal-port. This works because NPM is on the same default Docker network as most apps. Don’t type localhost or 127.0.0.1, because inside the NPM container they point to NPM itself. For the name and port of each app, and for apps on host networking, see Connect your apps to each other. Nextcloud needs extra settings behind NPM; see Nextcloud behind Nginx Proxy Manager.
Get a certificate
Section titled “Get a certificate”These steps also happen in NPM.
- Open the proxy host you made and select Edit.
- Open the SSL tab.
- Under SSL Certificate, pick Request a new Certificate.
- Turn on Force SSL.
- Save. If NPM asks you to agree to the Let’s Encrypt terms, agree.
NPM asks Let’s Encrypt for the certificate. This works only if the domain points to your public IP and ports 80 and 443 reach your server.
Get one wildcard certificate with Cloudflare
Section titled “Get one wildcard certificate with Cloudflare”Instead of one certificate per app, you can get one certificate for *.YOUR_DOMAIN and use it on every proxy host. Let’s Encrypt gives wildcard certificates only through a DNS challenge: NPM uses a Cloudflare API token to add a temporary DNS record that proves you own the domain. Deployrr does not give NPM a Cloudflare token, so you add it in NPM yourself.
These steps use the labels in recent NPM versions. Deployrr installs the latest NPM image, so labels can change.
- In Cloudflare, create an API token with Zone / Zone / Read and Zone / DNS / Edit for your domain, as in Create the API token. A separate token for NPM lets you revoke it without touching Traefik’s token.
- In NPM, open Certificates and add a certificate. Choose Let’s Encrypt via DNS.
- In the domain names field, add
YOUR_DOMAINand*.YOUR_DOMAIN. ReplaceYOUR_DOMAINwith your domain. - In DNS Provider, select Cloudflare.
- In Credentials File Content, replace the sample token with yours, so the line reads
dns_cloudflare_api_token=YOUR_TOKEN. - Leave Propagation Seconds empty to use the default. If the request fails because the record wasn’t found, try again with a higher value, such as
60. - Save and wait for the certificate to show in the list.
- For each proxy host, open Edit > SSL, pick the wildcard certificate under SSL Certificate, turn on Force SSL and save.
NPM warns that it stores the credentials as plain text. That is one more reason to keep the admin page off the internet. The wildcard covers one level only: sonarr.YOUR_DOMAIN works, a.b.YOUR_DOMAIN does not. Your DNS records still need to point to your public IP, and ports 80 and 443 still need to reach your server for visitors. See Cloudflare for Deployrr for records and the orange or gray cloud.
Check it worked
Section titled “Check it worked”-
Open the Proxy menu in Deployrr. The NPM line should end with “- Running”. The NPM line only shows a status while Proxy Type is NPM. If NPM is stopped, it shows “- Not Installed”. Run
sudo docker ps -ato see whether thenpmcontainer exists. -
Open
https://sonarr.YOUR_DOMAINin your browser, using the address you added. -
Check that the browser shows a padlock and the app’s login page.
-
Run this to check the container:
Terminal window dpsIf you didn’t install the bash aliases, run:
Terminal window sudo docker ps -aYou should see
npmwith a status that starts with “Up”.
Switch back to Traefik
Section titled “Switch back to Traefik”- Open Proxy > Proxy Type.
- Select Traefik and confirm the intro box.
- When the “NPM Container Running” box appears, agree. NPM is stopped, not removed.
- If Deployrr stopped NPM or changed the compose file, you see “Proxy Type set to: Traefik”.
- If you never set up Traefik before, follow Set up Traefik from Preparation. If you did set it up before, skip this step. Running Preparation again warns “previous setup may be overwritten”.
If you set up Traefik before and its line in the Proxy menu shows “Not Running”, the Traefik menu has no start option. Open Tools > Stack Manager > Up (needs a Basic, Plus or Pro license). It starts every enabled app, including Traefik.
As a fallback, start the container yourself with Docker. This works only if the container still exists. A Stack Manager Up or Update Stack run while Traefik’s line is disabled may have removed it.
sudo docker start traefikYour proxy hosts in NPM do not move to Traefik. Traefik needs its own routes for your apps. For router forwards and moving your apps, see Switch between Traefik and Nginx Proxy Manager.

