This page is for people who are still on Deployrr v4.6.1 or older. It is kept for reference.
Deployrr v5.0 changed a lot of the code. Because of that, v4 setups do not carry over on their own. The steps below move a v4.6.1 install (or older) to v5.0.
What changed in v5
Section titled “What changed in v5”- A new Deployrr logo and icon.
- Local mode. You can install apps for local access without a reverse proxy. This also lets you run setups with more than one server, because Traefik is no longer required.
- New ways to expose apps through Traefik:
- Simple mode: every app behind Traefik is reachable from inside and outside your network.
- Advanced mode: you choose per app whether it is internal, external or both.
- Traefik now uses file providers by default to expose your apps. A few apps, such as Traefik itself, OAuth and Authelia, still use Docker labels.
Migrate from v4 to v5
Section titled “Migrate from v4 to v5”- Stop all running containers, or bring down the whole stack.
- Keep the stack down until the migration is done.
- Open the Deployrr Tools menu and run a cold backup.
- If you can, make a second backup, for example a Proxmox VM or LXC backup.
- Exit Deployrr v4.6.1.
- On your v4.6.1 install, open the
/opt/deployrr/statusfolder. - Delete every status file whose name starts with
03_,04_,05_or06_. - Open your Docker folder.
- Delete the compose folder.
- Delete the main Docker compose file.
- Start Deployrr again.
- Go through all the setup steps in order. Deployrr finds your existing appdata.
- When Deployrr asks if you want to reinstall Traefik, choose to overwrite.
Get help
Section titled “Get help”If you then run Deployarr v5.7 or older, see Migrate from Deployarr to Deployrr for the rename.
If you run into problems, see Get help on Discord.

