Use one domain across several servers
You can run Deployrr on several machines and still reach all their apps on one domain, for example jellyfin.example.com and sonarr.example.com. One server runs Traefik. The others run apps. This guide is for you if you have, say, a storage server and a second server for other apps.
Overview
Section titled “Overview”You end up with this layout:
| Server | Setup Mode | What it does |
|---|---|---|
| Main server | Hybrid | Runs Traefik, your domain, and your login protection. Your router sends ports 80 and 443 here. |
| Other servers | Local | Run apps. Their apps are open only on your home network. |
The main server’s Traefik sends each subdomain to the right machine. You tell it where each app lives with Traefikify. The other servers need no domain, no Traefik and no port forwarding.
Your DNS stays as it is. The * CNAME record pointing to @ that Hybrid mode asks for already covers every new subdomain.
To see the two modes explained, watch Deployrr 5 walkthrough: Local vs Hybrid mode at 7:01 (shows Deployrr v5; menus differ in v6).
Before you start
Section titled “Before you start”- The main server is set up with a domain, Cloudflare and Traefik Production, and Traefik is running. Follow the Quick start if it is not.
- You have a Plus or Pro license on the main server. Traefikify and Hybrid mode need it. Local mode works with a Basic, Plus or Pro license.
- On the main server, all Prerequisites steps are done and the Socket Proxy app is running. Traefikify needs both. If something is missing, Deployrr shows a Requirements Not Met box that lists it.
- The servers can reach each other on your network. A VPN between sites also works.
- If you want login protection on an app, that auth app (for example Authelia) is already running on the main server.
Set up the main server
Section titled “Set up the main server”- In Deployrr, open Prerequisites. The current mode shows next to Setup Mode.
- If it shows Local, select Setup Mode. The setting switches each time you select it. The Server Setup Mode box should say
Hybrid mode ENABLED. - Meet the Hybrid requirements listed in the box and in the Quick start: a domain, Cloudflare DNS with an A record and a
*CNAME record, Cloudflare SSL mode set to FULL, and ports 80 and 443 forwarded to this server. - Go to Proxy > Proxy Type and pick Traefik. Switching a server to Local mode clears this choice, so check it if the server was in Local mode before.
- Set up Traefik with Proxy > Traefik > Production and make sure Traefik is running.
Set up each other server
Section titled “Set up each other server”- Install Deployrr on the server.
- Open Prerequisites and check the mode next to Setup Mode. If it shows Hybrid, select Setup Mode once. The box should say
Local mode ENABLED. In Local mode, apps are open on the internal network only. No reverse proxy, domain name or port forwarding is needed. - Install your apps as usual.
- Open each app in a browser on your network, at
http://SERVER_IP:PORT. Write down the IP address and the port. You need both next.
Add each app to the main server’s Traefik
Section titled “Add each app to the main server’s Traefik”Do this on the main server, once for each app on another server. Put any app behind Traefik with Traefikify explains every prompt in more detail.
- In Deployrr, go to Proxy > Traefik > Traefikify.
- Read the Traefikify box and confirm that you want to proceed.
- Answer the prompts:
Enter a name for the App.: a lowercase name, for examplejellyfinEnter a subdomain for the App.: the default is the name without hyphensHost IP Address of the App.: the IP address of the other server, not the main serverWebUI protocol (http/https) of the App::httpfor most apps. Type exactlyhttporhttps.WebUI port number of the App:: the port you wrote down
- At Pick an Authentication Method, pick the method you want. Authelia, Authentik, Google OAuth and TinyAuth only show up if they are running on the main server. Basic HTTP Auth and No Authentication are always there. Skip means no authentication. Choose a login method helps you pick.
- At Pick an Exposure Method, pick how you reach the app. In Simple Traefik mode, the only choice is Both (internal and external). Advanced mode, under Proxy > Traefik > Traefik Mode, adds Internal and External. Advanced mode also needs your router to forward ports 80 and 443 to ports 81 and 444 on the main server.
- If the Deployrr Dashboard is running, Deployrr asks if you want to add the app to it. Say yes to see the app in the Dashboard’s Apps (Remote) section. See Set up and maintain the Deployrr Dashboard.
Deployrr creates a file named app-NAME.yml in appdata/traefik3/rules/HOSTNAME/ inside your Docker folder. NAME is the app name and HOSTNAME is the main server’s hostname. Traefik picks up the new file on its own, so you don’t need to restart it. To see how such a file works when you write it by hand, watch Traefik guide: External apps (HTTP) behind Traefik at 9:03 (manual Docker Compose setup).
If you see Connection to http://192.168.1.20:8096 could not be verified, setup still continues. Your IP address and port will differ. Check the IP address and the port, and see the limits below.
If you made a mistake, run Traefikify again with the same name. Deployrr asks if you want to overwrite the file. You can also remove the app with Un-Traefikify in the same menu.
Example: Jellyfin on a second server
Section titled “Example: Jellyfin on a second server”Your main server runs Traefik for example.com. A second server at 192.168.1.20 is in Local mode and runs Jellyfin.
- On the second server, open
http://192.168.1.20:8096. Jellyfin loads. Use the port that your Jellyfin uses if it differs from 8096. - On the main server, go to Proxy > Traefik > Traefikify and confirm.
- Enter these values:
- Name:
jellyfin - Subdomain:
jellyfin - Host IP address:
192.168.1.20 - Protocol:
http - Port:
8096
- Name:
- Pick an authentication method and an exposure method.
- Open
https://jellyfin.example.com.
Replace example.com and 192.168.1.20 with your own domain and IP address.
If the Jellyfin app on an LG TV or Xbox then shows error -27, see Jellyfin app on LG webOS TV or Xbox shows error -27.
Check it worked
Section titled “Check it worked”- Open
https://SUBDOMAIN.YOUR_DOMAINin a browser. Replace the placeholders with your subdomain and domain. - You should see the app, or your login page if you picked an auth method.
- Turn off Wi-Fi on your phone and open the same address. This tests access from outside your network. Skip this step if you chose Internal.
If the page does not load, read the Traefik logs on the main server.
Limits
Section titled “Limits”- The main server is a single point of failure. If it is down, no app is reachable by its domain name. Apps on other servers still work at their local
IP:PORTaddress. - The main server must reach each other server. A VPN, a different network or a different site all work if the main server can open the app’s IP address and port.
- The app’s port must be open to the main server. If a firewall runs on the other server, allow the app’s port from the main server’s IP address.
- Give each other server a fixed IP address, or a DHCP reservation on your router. The IP address is saved in the app’s file. If the address changes, the app stops loading until you fix it.
If the other server runs its own Traefik
Section titled “If the other server runs its own Traefik”Your router can usually send ports 80 and 443 to one machine only. If another server runs its own Traefik for a different domain, use Domain Passthrough on the main server instead of Traefikify. The main server then hands every request for that domain to the other server.
It needs the same things as Traefikify: Prerequisites done, Socket Proxy running, Traefik Production done and Traefik running, and a Plus or Pro license.
Prepare the other server
Section titled “Prepare the other server”- Set the server up with its own domain, Cloudflare and Traefik Production. Follow the Quick start.
- In Cloudflare, point that domain’s
Arecord and*CNAME record to the same public IP address as your main server. Your router sends ports 80 and 443 to the main server, so traffic for both domains arrives there. - Do not forward any ports to the other server. It gets its certificates through Cloudflare, so it needs none for that.
Prerequisites > Domain Checks on the other server tests ports 80 and 443 on your public IP address, and your router sends those to the main server. The first run, before the other server’s Traefik is running, passes. If you run it again later, it stops with Port 80 is reachable but something is already listening on it. Then turn on Expert mode in Settings and answer Y when Deployrr asks to override.
Add the passthrough
Section titled “Add the passthrough”Do this on the main server.
- Go to Proxy > Traefik > Domain Passthrough and confirm the box.
- Enter a name for the host, for example
synology. Deployrr makes it lowercase. - Enter the other server’s IP address on your network, for example
192.168.1.100. - Enter the domain to pass through, for example
example.net.
All three answers are required. Deployrr saves domain-DOMAIN.yml in appdata/traefik3/rules/HOSTNAME/ in your Docker folder. HOSTNAME is the main server’s hostname. Traefik picks it up on its own, with no restart. If the file exists, Deployrr asks if you want to overwrite it.
To remove a passthrough, move that file out of the rules folder. Traefik drops the rule. Keep the file as a backup. There is no menu item for this.
Check it worked
Section titled “Check it worked”- Turn off Wi-Fi on your phone.
- Open an app on the other domain, for example
https://APP.example.net. Replace the placeholders with your own app and domain. - You should see the app, served with the other server’s certificate.
If it fails, read the Traefik logs on both servers.
Things to know
Section titled “Things to know”- The passthrough does not forward the visitor’s address. This is how a plain TCP passthrough works. The other server’s Traefik sees connections from the main server, so IP allowlists and CrowdSec there see the main server’s address.
- Port 80 is not passed through. The main server redirects
httprequests tohttps, and the browser then connects again on 443, which is passed through.
To see it in use, watch Deployrr 5 walkthrough: Domain Passthrough at 1:10:42 (shows Deployrr v5; menus differ in v6). To understand how the passthrough works underneath, read UDMS part 27: the Traefik TCP passthrough solution (manual setup, background only; follow the steps above in Deployrr v6).
Next steps
Section titled “Next steps”- Put a Home Assistant that runs elsewhere behind Traefik: Home Assistant behind Traefik.
- Add more apps and link them: Connect your apps to each other.

