Put any app behind Traefik with Traefikify
Traefikify puts an app behind your Traefik. The app can run on the same server, on another machine, or on a device such as a NAS. You get an address like https://SUBDOMAIN.YOUR_DOMAIN and a login method of your choice. Un-Traefikify removes the app from Traefik again.
For a container you added in custom.yml, see Protect a custom.yml app with Traefik and a login. For a second copy of an app, see Run a second copy of an app. Some apps need one extra setting on their side, for example Home Assistant.
Before you start
Section titled “Before you start”- You have a Plus or Pro license. See Licenses.
- All Prerequisites steps are done, and the Socket Proxy app is running.
- Traefik Production is done and Traefik is running. See Set up Traefik.
- The app is running, and you can open it from your Deployrr server at
http://IP_ADDRESS:PORT. - If you want a login method, set it up first. See Choose a login method.
- Your DNS sends the subdomain you plan to use to your server.
If something is missing, Deployrr shows a Requirements Not Met box that lists it, and stops.
Put an app behind Traefik
Section titled “Put an app behind Traefik”- In Deployrr, go to Proxy > Traefik > Traefikify. When your server already has app rules files, the menu line shows how many, for example
2 App(s). - Read the Traefikify box and select Yes to proceed.
- At “Enter a name for the App”, type a lowercase name. Use
-or_instead of a space. - If a file for that name already exists, Deployrr shows File Provider Exists and asks if you want to overwrite it. Select Yes to replace it. Select No and Deployrr says “No changes made”.
- Answer the next prompts one at a time:
- Subdomain: the default is the name without hyphens. Use lowercase and no spaces.
- Host IP Address of the App: the IPv4 address of the machine that runs the app, for example
192.168.1.100. - WebUI protocol (http/https) of the App: type
httporhttps. Most apps usehttp. Pickhttpsonly if the app answers on HTTPS alone. - WebUI port number of the App: the port you use to open the app.
- At Pick an Authentication Method, select a method. See the list below.
- At Pick an Exposure Method, select where the app can be reached. See the list below.
- Wait for the connection test. See If you see “could not be verified”.
- Read the Traefikify - Success box. It shows the address of your app.
Traefik picks up the new file on its own. You don’t need to restart it.
To see these prompts filled in, watch Deployrr 5 walkthrough: Traefikify an app at 1:04:22 (shows Deployrr v5; menus differ in v6).
Deployrr creates a file named app-NAME.yml in appdata/traefik3/rules/HOSTNAME/ inside your Docker folder. NAME is the name you typed, in lowercase, and HOSTNAME is your server’s hostname.
To see what such a file does and how it is made by hand, watch Traefik guide: External apps (HTTP) behind Traefik at 9:03 (manual Docker Compose setup). For background, read UDMS part 18: Adding non-Docker or external apps behind Traefik (manual setup; paths and names differ from Deployrr).
If a prompt gets an empty answer, or the protocol is not http or https, Deployrr stops with a message such as “Port number missing” and creates no file. It then says “File provider addition aborted - you may start over if needed”. Run Traefikify again.
Login methods
Section titled “Login methods”The list shows the methods you can use:
- Authelia, Authentik, Google OAuth and TinyAuth show only when that app is running. They are marked Recommended.
- Basic HTTP Auth is marked Discouraged.
- No Authentication is marked Not Recommended. The app may still have its own login.
Some choices are refused for some app names. For example, Basic HTTP Auth is not offered for portainer, open-webui, kavita, flame, paperless-ngx or flowise. No Authentication is not offered for wg-easy. Deployrr shows a message and asks you to pick again.
Skip means no authentication. Deployrr says “Authentication selection skipped, using no authentication”.
Exposure choices
Section titled “Exposure choices”- In Simple Traefik mode, the only choice is Both. The app is reachable on your LAN and over the internet.
- In Advanced mode, you can also pick Internal (your LAN only) or External (over the internet only). Switch modes under Proxy > Traefik > Traefik Mode. See Simple vs Advanced Traefik mode before you switch.
If you cancel this box, Deployrr uses Both. To change the choice later, see Manage Exposure in the same menu. To limit an app to your LAN, see Allow only some IP addresses to reach an app.
Add the app to the Dashboard
Section titled “Add the app to the Dashboard”If the Deployrr Dashboard is running, Deployrr asks Add to Deployrr Dashboard? after the success box. The question says the app will appear in the Remote Apps section. On the Dashboard, that section is named Apps (Remote).
- Select Yes.
- At Dashboard - App Name, type the name to show. The default is your subdomain with a capital first letter.
- At Dashboard - Icon, type an icon name or leave the default. The default is
si-and your subdomain. Usesi-NAMEfor Simple Icons,mdi-NAMEfor Material Design Icons orsh-NAMEfor Selfh.st icons. - At Dashboard - Description, type a description. The default is the app’s address.
Deployrr then says “Added NAME to Deployrr Dashboard”. If it says “Could not add to Dashboard (Dashboard may not be running)”, start the Dashboard and add the app with Dashify. See Set up and maintain the Deployrr Dashboard.
Put an app that only uses HTTPS behind Traefik
Section titled “Put an app that only uses HTTPS behind Traefik”Some apps only answer on HTTPS with a self-signed certificate. Type https at the WebUI protocol prompt and use the app’s HTTPS port. Deployrr then creates the file so that Traefik does not check the app’s certificate. Your visitors still get your normal Traefik certificate. To understand why, watch Traefik guide: Proxmox web UI behind Traefik at 5:21 (manual Docker Compose setup).
You can tell an app is HTTPS-only when its address starts with https:// and your browser warns about the certificate. Common examples and their usual HTTPS ports:
| Device or app | Usual HTTPS port |
|---|---|
| Proxmox VE web UI | 8006 |
| Proxmox Backup Server | 8007 |
| Synology DSM | 5001 |
| UniFi Network Application (self-hosted) | 8443 |
These are the defaults. If you changed the port on the device, use yours.
Example: the Proxmox web UI
Section titled “Example: the Proxmox web UI”Say Proxmox runs at https://192.168.1.10:8006. Answer the Traefikify prompts like this:
- Name:
proxmox. - Subdomain: keep
proxmox. - Host IP Address:
192.168.1.10. - WebUI protocol:
https. - WebUI port:
8006. - Login method: pick one of yours. Proxmox still asks for its own login after it.
- Exposure: in Advanced mode, pick Internal to keep the Proxmox web UI off the internet.
Then open https://proxmox.YOUR_DOMAIN. You should see the Proxmox login with a valid certificate and no browser warning.
Deployrr’s connection test only checks that the port is open, so it passes even if you typed http for an app that only answers on HTTPS. The address then shows an error instead of the app. Run Traefikify again with the same name, overwrite the file, and type https.
Remove an app with Un-Traefikify
Section titled “Remove an app with Un-Traefikify”Un-Traefikify has the same requirements as Traefikify.
- Optional: make a backup from the Tools menu first. The delete warning recommends it.
- In Deployrr, go to Proxy > Traefik > Un-Traefikify.
- In the Traefik File Providers list, select the file to delete, for example
app-jellyfin.yml. The box shows how many files it found. - Select Delete.
- Read the warning and select Yes to delete the file. Select No to keep it. Deployrr then says the file “was not deleted”.
- Read the success box. It says “Traefik will automatically stop routing to this app.”
- If the Dashboard is running and has an entry for the app, Deployrr asks Remove from Dashboard?. Select Yes to remove it. A Dashboard Updated box confirms it.
- The list shows again, so you can delete more files. Select Back when you are done.
If you see “No file providers found”, there is nothing to remove.
Un-Traefikify deletes only the rules file and, if you agree, the Dashboard entry. The app itself keeps running, and your DNS records stay as they are.
If you see “could not be verified”
Section titled “If you see “could not be verified””After the prompts, Deployrr tests whether it can reach the app. If the test fails, you see this. Your address and port will differ:
Connection to http://192.168.1.100:8123 could not be verifiedSome apps may take time to start. Proceeding anyway...It means Deployrr got no answer from that IP address and port. Setup still goes on and the file is still created. If the app is just slow to start, you can ignore the warning.
If the app is up and the address still does not work, check these:
- The IP address is the one of the machine that runs the app, not your Deployrr server (unless they are the same).
- The port is the WebUI port of the app.
- The app is running. Open
http://IP_ADDRESS:PORT(orhttps://for an HTTPS-only app) in a browser on your network. - No firewall on the app’s machine blocks the port from your Deployrr server.
To fix a wrong value, run Traefikify again with the same name and overwrite the file. You can also edit appdata/traefik3/rules/HOSTNAME/app-NAME.yml and change the address on the url: line. Traefik picks up the change on its own. To change the subdomain the same way, see Change the subdomain of an app you already installed.
Use a hostname instead of an IP address
Section titled “Use a hostname instead of an IP address”The rules file holds the app’s address as you typed it. If the machine that runs the app gets a new IP address, the app stops loading through Traefik. The best fix is a fixed IP for that machine. See Give your server a fixed IP address.
If you can’t fix the IP, put a hostname on the url: line instead, for example http://nas.home.lan:5000. The Host IP Address prompt asks for an IPv4 address. It also accepts a hostname.
Deployrr tests the name from the server. Traefik looks it up from inside its own container, so the two can give different results. If Deployrr’s test fails, it only warns and still creates the file. Test the name from the Traefik container as shown below.
Traefik must be able to look up that name:
- A name from your local DNS server or router works when the server uses that DNS server.
- A name that exists only in the server’s
/etc/hostsfile, or a.localname, may work in Deployrr’s test but not in Traefik. Add the name to your local DNS server instead. See Set up local DNS rewrites.
To test the name from inside the Traefik container, run this. Replace the name and port with yours:
sudo docker exec traefik wget -q --spider http://nas.home.lan:5000/ && echo OKWhat you see tells you where the problem is:
OK: Traefik can reach the app by that name.bad address: Traefik can’t look up the name.Connection refusedor a timeout: the name works, but the app did not answer. Check the port and the firewall on the app’s machine.server returned errorwith an HTTP code, such as401: Traefik reached the app. The app answered with an error or a login request, which is fine.
If the server running Deployrr changes its IP, see Change the server IP. That page covers rules files that point at the server itself.
Check it worked
Section titled “Check it worked”- Open
https://SUBDOMAIN.YOUR_DOMAINin a browser. ReplaceSUBDOMAINandYOUR_DOMAINwith your own values. - You should see the app, or your login page if you picked a login method.
- Turn off Wi-Fi on your phone and open the same address. Skip this if you picked Internal.
- After Un-Traefikify, the same address should no longer open the app.
If the address does not load, read the Traefik logs. If it shows 404, 502 or Gateway Timeout, see One app behind Traefik shows 404, 502 or Gateway Timeout.

