Switch between Traefik and Nginx Proxy Manager
You can use Traefik or Nginx Proxy Manager (NPM) as your reverse proxy, but not both at once. Both need ports 80 and 443. This page covers what to stop, what to start, what to change on your router, and what to redo for your apps.
For a short look at why NPM is an option in v6, watch Deployrr 6 overview: NGINX Proxy Manager at 3:43. To understand how the two proxies differ, read UDMS part 18: Traefik vs Nginx Proxy Manager (manual setup, background only).
Before you start
Section titled “Before you start”- Setup Mode is Hybrid. In Local mode you see the “Proxy Type - Local Mode Warning” box. Picking a Proxy Type there still saves your choice, stops the other proxy and changes the proxy lines in your compose file, so switch to Hybrid first. Switching Setup Mode to Local also clears your Proxy Type (the Proxy menu shows “NOT SELECTED”). See Setup Mode.
- Your proxy hosts in NPM do not move to Traefik. Your Traefik routes do not move to NPM. You recreate them.
Switch from Traefik to NPM
Section titled “Switch from Traefik to NPM”- Open Proxy > Proxy Type and select NPM. Follow Pick NPM as your proxy type.
- When the “Traefik Container Running” box appears, answer yes. Traefik stops. It is not removed. If you answer No, the switch is cancelled and Proxy Type stays as it was.
- Deployrr prints “Enabling npm.yml in compose file…” and “Disabling traefik.yml in compose file…”. This decides which proxy a later Stack Manager Up starts.
- Change your router forwards.
- Start NPM. If you never installed it, open Proxy > NPM > Install. If you used it before, see Start a proxy you used before.
- In NPM, add a proxy host for each app. Use the container name and internal port. See Add a proxy host for an app and Connect your apps to each other. App reference lists app ports.
“Port Conflict - Cannot Install” at NPM > Install means Traefik was started again after the switch, for example with sudo docker start traefik. Run sudo docker stop traefik, then try again.
Apps behind a Traefik login chain have no login in NPM, and the login apps, Manage Exposure and Traefikify need Traefik. See What you give up compared to Traefik.
Switch from NPM to Traefik
Section titled “Switch from NPM to Traefik”- List your NPM proxy hosts first. Write down the domain, forward host and forward port of each one. You need them later.
- Open Proxy > Proxy Type and select Traefik.
- When the “NPM Container Running” box appears, answer yes. NPM stops. It is not removed. If you answer No, the switch is cancelled and Proxy Type stays as it was.
- Deployrr prints “Enabling traefik.yml in compose file…” and “Disabling npm.yml in compose file…”. This decides which proxy a later Stack Manager Up starts.
- Start Traefik. If you never set it up, follow Set up Traefik: Preparation, Staging, then Production. If you set it up before, see Start a proxy you used before.
- Change your router forwards.
- Bring your apps across (see the next section).
“Proxy Type Required” at Traefik > Traefik Mode means your Proxy Type is still NPM.
Bring your apps across
Section titled “Bring your apps across”Apps you installed before the switch keep their Traefik rules. They work again once Traefik runs.
Apps you installed while NPM was in use have no Traefik address. While Traefik is not running, Deployrr does not ask for a subdomain when you install an app. Fix each one in one of two ways:
- Use Traefik > Traefikify to add the app. See Traefikify.
- Reinstall the app while Traefik is running. Deployrr asks for the subdomain and creates the rules file if the app has none. See Reinstall an app.
For something Deployrr did not install, such as an app on another machine, use Traefikify with the IP address and port from your list of NPM proxy hosts.
The Dashboard adds remote entries only while Traefik runs.
Start a proxy you used before
Section titled “Start a proxy you used before”Choosing a Proxy Type does not start the proxy. Open Tools > Stack Manager > Up (needs a Basic, Plus or Pro license). It starts every enabled app, including the proxy whose line is now enabled. Tools > Stack Manager > Start Container also works if the container still exists.
As a fallback, run sudo docker start npm or sudo docker start traefik. This works only if the container still exists: a Stack Manager Up or Update Stack run while a proxy’s line is disabled removes its stopped container (see What happens to a disabled app’s container). Its appdata stays, and the next Up after you switch back creates it again.
Change your router forwards
Section titled “Change your router forwards”| Proxy | Forward 80 to | Forward 443 to |
|---|---|---|
| NPM | 80 | 443 |
| Traefik, Simple mode | 80 | 443 |
| Traefik, Advanced mode | 81 | 444 |
Only a move to or from Traefik Advanced mode needs a change. To see the Simple and Advanced forwards set on a router, watch Deployrr 5 walkthrough: Port Forwarding at 37:43 (shows Deployrr v5; menus differ in v6, the ports are the same). See Port forwarding and Simple vs Advanced Traefik mode.
Check it worked
Section titled “Check it worked”-
List your containers:
Terminal window sudo docker ps -aOnly one of
traefikandnpmshould have a status that starts with “Up”. The other should show “Exited”. It is not listed if a Stack Manager Up ran since the switch. -
Open Proxy. The Proxy Type line should end with the name you chose.
-
Open an app address in your browser.

