Forward the right router ports for Deployrr
A port forward tells your router to send traffic from the internet to your Docker host. In Hybrid mode, Traefik or Nginx Proxy Manager needs two of them. This page shows which ports to forward, how to set them, and how to test them.
Before you start
Section titled “Before you start”You only need port forwarding in Hybrid Setup Mode with a reverse proxy at home. Skip this page if:
- You use Local mode. Your apps are for your home network only. See Setup Mode: Local or Hybrid.
- You reach your apps with Tailscale. It needs no open ports. See Set up Tailscale.
- Deployrr runs on a VPS. It has a public IP and no home router. If a firewall blocks the ports, see Fix the UFW firewall on a VPS.
You also need:
- Hybrid mode with a reverse proxy picked. See Set up Traefik or Use Nginx Proxy Manager instead of Traefik.
- Access to your router’s admin page.
- To know your Traefik mode if you use Traefik. In Deployrr, open Proxy > Traefik and read the Traefik Mode line. It shows
NOT SETuntil you select Traefik Mode once. The first time, you get Simple mode.
What to forward
Section titled “What to forward”Forward these ports, as TCP, to the LAN IP address of your Docker host.
| Reverse proxy | Forward router port 80 to | Forward router port 443 to |
|---|---|---|
| Traefik, Simple mode | 80 | 443 |
| Traefik, Advanced mode | 81 | 444 |
| Nginx Proxy Manager | 80 | 443 |
The first number is the port on your router, the one the internet connects to. The second is the port on your Docker host. Some routers call them “external” and “internal” port.
Don’t forward the Nginx Proxy Manager admin port. Deployrr suggests 81 for it at install, and you can pick another. You open the admin panel from your home network, so only 80 and 443 need a forward.
Your Docker host’s LAN IP should not change. If your router hands out a new address later, the forwards point at the wrong machine. See Give your server a fixed IP address.
For what Simple and Advanced mode mean, see Simple vs Advanced Traefik mode.
Router menus differ by brand. The names below are common ones. Check your router’s manual if yours look different.
-
On the Docker host, find its LAN IP:
Terminal window ip -br addrLook for the line with your LAN address, for example
192.168.1.50/24. Skip thelo,docker0andbr-lines. -
Log in to your router’s admin page.
-
Write down the existing port forwarding rules.
-
Find the port forwarding page. It may be called Port Forwarding, Virtual Server, NAT or Applications.
-
Add a rule for port 80. Use TCP. Set the destination IP to your Docker host’s LAN IP. Set the destination port from the table above.
-
Add a rule for port 443 the same way.
-
Save the rules. Some routers need a restart to apply them.
To see a router port forward set up, watch Deployrr 5 walkthrough: Port forwarding at 38:18 (shows Deployrr v5; menus differ in v6, and it forwards 80 to 81 and 443 to 444 as in Advanced mode). For the same idea in a manual setup, watch Traefik 3 guide: forwarding ports 80 and 443 at 18:42 (manual Docker Compose setup). For a written guide, see UDMS part 18: Setting up port forwarding (manual setup).
Don’t use a DMZ or UPnP for this. A DMZ exposes your whole server to the internet. UPnP lets devices open ports on their own. Use fixed rules for 80 and 443 only.
Check it worked
Section titled “Check it worked”Check with Domain Checks
Section titled “Check with Domain Checks”Use this before you install Traefik.
-
In Deployrr, open Prerequisites.
-
Select Domain Checks.
-
Read the first lines. The port 80 line shows one of these:
Port 80 resolves to 80Port 80 resolves to 81The port 443 line shows one of these:
Port 443 resolves to 443Port 443 resolves to 444
What the lines tell you:
80and443mean your forwards match Simple mode or Nginx Proxy Manager.81and444mean your forwards match Advanced mode.
Each port is checked on its own, and Domain Checks doesn’t compare the result with your Traefik mode. A mixed result such as Port 80 resolves to 80 with Port 443 resolves to 444 also passes. Make sure both lines show the pair you want for your mode.
A green line here doesn’t always prove the forward reaches your server. When the test from the internet is refused, Domain Checks also shows Port 80 resolves to 80 (or Port 443 resolves to 443). Do the check from outside too once your reverse proxy is running.
If you see an error instead, see Domain Checks failed.
Check from outside
Section titled “Check from outside”Do this after Traefik or Nginx Proxy Manager is up and you have an app with an address.
- Turn off Wi-Fi on your phone, so it uses mobile data.
- Open
https://app.YOUR_DOMAINin the phone’s browser. Replaceappwith your app’s subdomain andYOUR_DOMAINwith your domain. - Check that the app’s page or login opens with a padlock.
If an app is set to Internal in Advanced mode, it should not open from mobile data. Test with an External or Both app.
Test from outside your home network. From inside, the result depends on your router (hairpinning) and your local DNS, so it can fail even when the forwards work, or pass when they don’t.
Test the ports with curl
Section titled “Test the ports with curl”When the page doesn’t open, test each port on its own. Run these from a device outside your home network: a VPS, a friend’s computer, or a terminal app on your phone with Wi-Fi off.
-
On the Docker host, find your public IP:
Terminal window curl -4 ifconfig.me -
From the outside device, test port 80. Replace
PUBLIC_IPwith the address from step 1:Terminal window curl -sSI http://PUBLIC_IP -
Test port 443:
Terminal window curl -sSkI https://PUBLIC_IP-kskips the certificate check, because your certificate is for your domain, not for the IP.-sShides the progress bar but still prints errors.
What the results mean:
| Result | What it means |
|---|---|
Any HTTP/... line, even 404 Not Found |
The port reaches Traefik or Nginx Proxy Manager. On port 80, Traefik answers with a permanent redirect to https://. On port 443, Traefik usually answers 404, because no app is set up for the bare IP. Nginx Proxy Manager shows its own default page. |
An SSL or TLS error on the port 443 test, such as curl: (35) |
Something on the other side answered, so the port is most likely forwarded. Traefik may refuse a secure connection that asks for a bare IP instead of a domain name, or answer it with a 404. Test your app by name (below) before you change the forward. |
Connection refused |
The request reached a device, but nothing listens on that port. Check the destination port in the forward (80 or 81, 443 or 444) and that Traefik or Nginx Proxy Manager is running with docker ps. |
| No answer, then a timeout | The forward is missing or points at the wrong IP, a firewall drops the traffic, or your ISP blocks the port. See If it doesn’t work. |
Then test your app by name:
curl -sSI https://app.YOUR_DOMAINA 200, or a redirect to your login page, means it works end to end. If the record is proxied by Cloudflare (orange cloud), this request goes to Cloudflare first. A 521 or 522 from Cloudflare means Cloudflare couldn’t reach your server: test the public IP as above. See Cloudflare for Deployrr.
Use an online port checker
Section titled “Use an online port checker”No device outside your network? Search for “open port checker”. Enter your public IP and port 80, then 443. These sites try a TCP connection from the internet:
- Open means something on your side accepts the connection.
- Closed means it doesn’t. Run the checker again with Traefik or Nginx Proxy Manager running, because with nothing listening the port shows as closed even when the forward is right.
A port checker tests the router ports, so check 80 and 443 in Advanced mode too, not 81 and 444. It doesn’t show that the right app answers. Use curl for that.
If it doesn’t work
Section titled “If it doesn’t work”- The forward points at the wrong IP. The Docker host may have a new LAN IP. Set the rules to the current address. Then give the host a fixed one. See Give your server a fixed IP address and Change the server IP.
- The ports don’t match your mode. Switching between Simple and Advanced later means changing the forwards too. See Simple vs Advanced Traefik mode. If you move between Traefik and Nginx Proxy Manager, see Switch between Traefik and Nginx Proxy Manager.
- Your ISP blocks port 80, or you are behind CG-NAT or double NAT. Forwards on your router then do nothing. See Behind CG-NAT. For the options in v6, watch Deployrr 6 overview: Options for CG-NAT at 4:37.
- A firewall on the server blocks the ports. See Fix the UFW firewall on a VPS.
- Internal apps don’t open from home in Advanced mode. When you switch to Advanced mode, Deployrr’s box notes: “If your router, gateway, or firewall is not capable of Hairpinning or you do not have a local DNS with rewrites (e.g. Pi-Hole, AdGuard Home, etc.), local traffic may be treated as external and you may not be able to access internal-only apps using FQDN.” See Set up local DNS rewrites.
- You use OPNsense. See Traefik staging fails with unable to obtain ACME certificate on OPNsense.

