Change the subdomain of an app you already installed
Deployrr asks for an app’s subdomain once, when you install it. After that, no menu changes it. This page shows how to change it by editing the app’s Traefik file, or the compose file for the Traefik dashboard and the login apps. It also tells you which menu changes the app’s login method and exposure.
What the install asks
Section titled “What the install asks”When Traefik is running and the app supports Traefik, the install asks up to three questions. It asks them even if you have not installed the Deployrr Dashboard. Authelia, Authentik, OAuth and TinyAuth get none of them.
| Question | What it does | Change it later |
|---|---|---|
| Traefik Subdomain | Sets the address: https://SUBDOMAIN.YOUR_DOMAIN. The default is the app’s name without hyphens. Cancel or an empty box uses the default. Deployrr turns capitals into lowercase and removes spaces. |
Edit the app’s file |
| Pick an Authentication Method | Sets who must log in before they see the app. Skip gives the app No Authentication. | Manage Auth |
| Pick an Exposure Method | Sets whether the app opens from home, from the internet or both. Deployrr asks this only in Advanced mode, where the Cancel button reads Default (Internal). In Simple mode the app is set to Both without a question. | Manage Exposure |
If your .env file in the Docker folder already has a line such as PAPERLESSNGX_SUBDOMAIN=docs, Deployrr uses that value and skips the Traefik Subdomain box. The line starts with the app’s name in capitals, with no hyphens or underscores, followed by _SUBDOMAIN.
Deployrr saves your answers in one file for the app, named app-NAME.yml. It sits in appdata/traefik3/rules/HOSTNAME/ inside your Docker folder. NAME is the app’s name and HOSTNAME is your server’s hostname.
Before you start
Section titled “Before you start”- The app is installed and opens at its current
https://address. - You can open a terminal on the server.
- You know the new subdomain. Use lowercase letters, with no spaces.
- Your DNS has a wildcard record (
*.YOUR_DOMAIN), as Set up Traefik asks. If you made a separate DNS record for each app instead, add one for the new name first. ReplaceYOUR_DOMAINwith your domain.
Your Traefik certificate covers your domain and every subdomain of it, so a new name needs no new certificate.
You can’t change the subdomain by reinstalling the app. If the app already has its file, a reinstall asks the three questions again but keeps the old file. The Dashboard entry can then show the new name while Traefik still uses the old one. If that happened, change the Dashboard entry to match the file, as in Update the Deployrr Dashboard. See Reinstall an app and keep its data.
-
Go to your Docker folder.
Terminal window cddWithout the aliases, use
cd YOUR_DOCKER_FOLDER. ReplaceYOUR_DOCKER_FOLDERwith the path to your Docker folder. -
List the app files and find the one for your app.
Terminal window sudo ls appdata/traefik3/rules/$HOSTNAME/ -
Copy the file to your home folder. Keep the copy outside the rules folder. Replace
NAMEwith the app’s name.Terminal window sudo cp appdata/traefik3/rules/$HOSTNAME/app-NAME.yml ~/app-NAME.yml.bak -
Open the file.
Terminal window sudo nano appdata/traefik3/rules/$HOSTNAME/app-NAME.yml -
Find the
rule:line.rule: "Host(`OLD_SUBDOMAIN.{{env "DOMAINNAME_1"}}`)" -
Replace only the old subdomain with the new one. Leave
{{env "DOMAINNAME_1"}}and the quotes as they are.rule: "Host(`NEW_SUBDOMAIN.{{env "DOMAINNAME_1"}}`)"If your file has a second
rule:line (for example one you made by hand or under v5), change it too. -
Save the file and close nano. Press
Ctrl+O,Enter, thenCtrl+X.
Traefik picks up the saved file on its own. You don’t need to restart it. To see a file like this edited by hand, watch Reverse proxy guide: editing an app file at 11:33 (manual Docker Compose setup).
To understand why the address lives in this file and not in Docker labels, read UDMS part 18: Docker labels vs the file provider (manual setup).
Do the same for an app you added with Traefikify. Its file has the same rule: line.
Update the Deployrr Dashboard
Section titled “Update the Deployrr Dashboard”The Deployrr Dashboard keeps its own copy of the address. Changing the file does not change it. A remote entry usually shows the address on two lines: the link and the description. At install, and after Manage Exposure, an Internal app gets a local link only.
If you use Advanced mode and installed the app from the Apps menu, the quick way is this:
- Open Proxy > Traefik > Manage Exposure.
- Select the app and select Change.
- Pick the exposure the app already has, then select Apply.
Manage Exposure rewrites the app’s Dashboard entries from the subdomain in the file. It does not update an app you added only with Traefikify.
Otherwise, edit the entry by hand:
-
Open
services.yamland find the old address.Terminal window sudo grep -n "OLD_SUBDOMAIN" appdata/deployrr-dashboard/config/services.yaml -
Open the file, change the old subdomain to the new one on those lines, and save. Change both lines of a remote entry.
Terminal window sudo nano appdata/deployrr-dashboard/config/services.yaml -
Refresh the Dashboard in your browser.
Leave the comment lines in the file alone. See Edit the dashboard files. To see an entry added by hand, watch Deployrr 5 walkthrough: Manually adding apps to the Dashboard at 1:06:41 (shows Deployrr v5; menus differ in v6, but the services.yaml file works the same way).
Tools > ReDash also reads the new subdomain from the file for apps you installed from the Apps menu. But it rebuilds the whole app list and drops hand edits to services.yaml. It also adds a local and a remote entry for every app while Traefik runs, whatever the app’s exposure. For an entry you added through the Traefikify or Dashify Dashboard dialogs, it puts back the old address. ReDash first saves the old file as services.DATE_TIME.yaml in the same folder.
Traefik dashboard and login apps
Section titled “Traefik dashboard and login apps”These apps get their address from a Docker label in their own file in compose/HOSTNAME/, not from a rules file. See Apps that use Docker labels. A login app also keeps its own address in a second place. Change every place in the table, or logins send people to the old address.
| App | File in compose/HOSTNAME/ |
Also change |
|---|---|---|
| Traefik dashboard | traefik.yml |
Nothing else. |
| Authelia | authelia.yml |
rd=https://authelia. in appdata/traefik3/rules/HOSTNAME/middlewares-authelia.yml, and authelia_url: in appdata/authelia/configuration.yml. |
| Authentik | authentik.yml |
Any address you typed into Authentik’s admin pages that starts with https://authentik.. |
| Google OAuth | oauth.yml |
The AUTH_HOST= line in the same file, and the redirect URI in your Google Cloud project. |
| TinyAuth | tinyauth.yml |
The TINYAUTH_APPURL= line in the same file, and the callback URL at Google or GitHub if you set up that login. |
-
Go to your Docker folder and back up the file. Replace
NAMEwith the file name from the table, without.yml.Terminal window cddsudo cp compose/$HOSTNAME/NAME.yml ~/NAME.yml.bakFor Authelia, also back up
middlewares-authelia.ymlandconfiguration.ymlthe same way. -
Open the file.
Terminal window sudo nano compose/$HOSTNAME/NAME.yml -
Find the
rule=Host(...)label and change only the old subdomain. Leave.$DOMAINNAME_1as it is. For example, to change Authelia fromautheliatologin:- "traefik.http.routers.authelia-rtr.rule=Host(`authelia.$DOMAINNAME_1`)"becomes:
- "traefik.http.routers.authelia-rtr.rule=Host(`login.$DOMAINNAME_1`)"Authentik has a second rule, on the
authentik-output-rtrline. It matches every subdomain, for Authentik’s outpost path only. Leave it alone. -
For Google OAuth or TinyAuth, change the subdomain in the
AUTH_HOST=orTINYAUTH_APPURL=line in the same file. Save the file and close nano. -
For Authelia, change the subdomain in the
rd=https://authelia.part (or the name you set before) of theaddress:line inmiddlewares-authelia.yml. Then change theauthelia_url:line inconfiguration.yml. Leave thedomain:lines as they are. They hold only your domain, so the subdomain doesn’t matter to them.Terminal window sudo nano appdata/traefik3/rules/$HOSTNAME/middlewares-authelia.ymlsudo nano appdata/authelia/configuration.yml -
Recreate the app. Traefik doesn’t see a label change until you do.
Terminal window dcrec NAMEWithout the aliases, see the full command in Apps that use Docker labels.
-
Update the address outside your server:
- Google OAuth: in your Google Cloud project, change the authorized redirect URI to
https://NEW_SUBDOMAIN.YOUR_DOMAIN/_oauth. - TinyAuth: change the callback URL in the Google or GitHub app you made for TinyAuth to use the new address.
- Authentik: Deployrr stores no other Authentik address. If you typed one into Authentik’s admin pages yourself, open them at the new address and update any that still starts with
https://authentik..
- Google OAuth: in your Google Cloud project, change the authorized redirect URI to
-
Change the app’s Dashboard entry by hand, as in Update the Deployrr Dashboard. Tools > ReDash reads these apps’ default address, not your label, so it puts the old address back. After a ReDash, edit the entry again.
To check it, open https://NEW_SUBDOMAIN.YOUR_DOMAIN in a private browser window. For a login app, also open an app that uses it. You should land on the login page at the new address. If you get a 404, see Apps that use Docker labels. To undo, copy the .bak files back and recreate the app.
Change the login method
Section titled “Change the login method”Use Security > Manage Auth (Pro license), or edit the chain name in the same file. Manage Auth also lists the apps that use Docker labels. Both ways are in Choose a login method for your apps. The file route is under By editing the rules file.
Change the exposure
Section titled “Change the exposure”Use Proxy > Traefik > Manage Exposure. It works in Advanced mode and needs a Plus or Pro license. See Change it later with Manage Exposure.
Check it worked
Section titled “Check it worked”- Open
https://NEW_SUBDOMAIN.YOUR_DOMAINin a private browser window. Replace both values with your own. - You see the app or its login page.
- Open the old address in the same window. It no longer opens the app. It usually shows
404 page not found.
If the new address shows an error, see One app behind Traefik shows 404, 502 or Gateway Timeout. A typo in the rule: line is the usual cause.
Update what used the old address
Section titled “Update what used the old address”The old address stops working. Update these:
- Bookmarks in your browsers.
- Mobile and TV apps that you pointed at the old address.
- Other apps that call this app by its address.
- Any login app that lists the old address as a redirect URL, if you set one up that way. If you changed the login app’s own address, see Traefik dashboard and login apps.
- Nextcloud only answers on addresses it trusts. Add the new one as in Nextcloud says Access through untrusted domain. If you turned on
OVERWRITEHOST, also changeNEXTCLOUD_SUBDOMAINin.envand recreate Nextcloud.
Undo the change
Section titled “Undo the change”-
Copy the backup file over the changed file.
Terminal window sudo cp ~/app-NAME.yml.bak appdata/traefik3/rules/$HOSTNAME/app-NAME.yml -
Change the Dashboard entry back, if you changed it. If you ran ReDash, copy back the
services.DATE_TIME.yamlfile it saved inappdata/deployrr-dashboard/config/overservices.yaml.
Traefik picks up the old file on its own. Delete the .bak copy when you no longer need it.
To remove an app’s file instead, use Un-Traefikify. See Put any app behind Traefik with Traefikify.

