What can overwrite or delete your changes
You edited a file or you have data you care about. Before you run a Deployrr action, check this page. It lists what each action overwrites or deletes, what it keeps, and how to protect your change.
Overview
Section titled “Overview”This page is the action view: you pick an action and see what it touches. For the file view, where you pick a file and see who writes it, see What you can edit and what Deployrr writes.
Before any of these
Section titled “Before any of these”-
For the whole Docker folder, go to Tools > Backups > Backup (Pro). A backup stops your running containers while it runs. See Back up and restore your Docker folder.
-
For one file, copy it to your home folder. Keep the copy outside the Docker folder and outside the Traefik rules folder, so Traefik does not read it. Replace
YOUR_DOCKER_FOLDER,HOSTNAMEandAPPwith your own values:Terminal window sudo cp YOUR_DOCKER_FOLDER/compose/HOSTNAME/APP.yml ~/APP.yml.bak
Apps and containers
Section titled “Apps and containers”| Action | Overwrites or deletes | Keeps | Protect your change | Details |
|---|---|---|---|---|
| Apps > Manage Apps > the app > Reinstall (shown only for a stopped app), or Install then Yes in Already Installed | The app’s compose file, the compose files of its database containers, and the config files listed under Config files a reinstall writes again. Secrets that Deployrr makes without asking you get new values. | appdata/APP data, an existing Traefik rules file, secrets you typed in (the prompt offers to keep them) |
Copy the files you changed and, for an app with a database, its files in secrets/. Put edits back, then Recreate. |
Config files a reinstall writes again, Reinstall an app |
| Apps > Manage Apps > the app > Remove | The container, the compose file and the app’s secret files, also when you keep app data | appdata/APP, if you answer No to removing app data |
Copy the app’s files in secrets/ first. |
Manage your apps |
| Tools > Stack Manager > Delete > Safe | The container, compose file, the app’s entries in .env, its Traefik rules file and Dashboard entry |
appdata/APP and secrets |
Copy the compose file and rules file first. | Stack Manager |
| Stack Manager > Delete > Full | All of the above, plus appdata/APP and the app’s secrets. It can also remove unused Docker volumes. You can’t undo it. |
Nothing of that app | Back up the Docker folder first. | Stack Manager |
| Docker > Cleanup | Stopped containers, unused networks, dangling images and build cache | Running containers, volumes, your Docker folder | Nothing to copy. See Stopped apps. | Free up disk space |
Aliases dprunevol, dprune, derase |
All three remove unused volumes. dprune also removes stopped containers, unused networks and unused images. derase stops and removes every container, then removes all images. |
Your Docker folder | Back up first. Docker asks you to confirm each prune. | Pick a cleanup alias |
| Docker Garbage Collection app (on its schedule, once you set the schedule) | Containers that exited over 7 days ago, unused images and unused volumes. A reinstall rewrites docker-gc.yml and the exclude file. |
Running containers, your Docker folder | List images to keep in appdata/docker-gc/docker-gc-exclude. Copy your edits to both files before a reinstall. |
Free up disk space |
Setup steps you run again
Section titled “Setup steps you run again”| Action | Overwrites or deletes | Keeps | Protect your change | Details |
|---|---|---|---|---|
| Prerequisites > Environment > Recreate | Everything in the Docker folder. It first copies the folder to docker_backup_DATE in your Backups Folder, but only if a Backups Folder is set. |
The copy, if one was made | Make your own backup first. The copy is a plain folder, so Tools > Backups > Restore does not list it. | Docker folder layout |
| Prerequisites > Environment > Reuse | The main compose file (written fresh, with no apps), every app compose file, logs, scripts and other folders it does not keep. It writes a fresh custom.yml and resets some .env values, such as hostname, server IP and timezone. |
appdata, .env and secrets |
Copy custom.yml first. Needs a Backups Folder. Choose Exit to change nothing. |
Docker folder layout |
| Proxy > Traefik > Preparation | After one Y/y confirmation: tls-opts.yml, middlewares-basic-auth.yml, middlewares-buffering.yml, middlewares-rate-limit.yml, middlewares-secure-headers.yml, chain-basic-auth.yml and chain-no-auth.yml. A CrowdSec line you added to those two chain files is lost. It also asks again for the Basic Auth login and Cloudflare token. |
app-APP.yml and the other rules files |
Copy those files first. While Traefik runs, Preparation stops with “Port N is occupied” before it rewrites the rules files. | Traefik rules files |
| Proxy > Traefik > Staging or Production | Your certificates (acme.json), unless you press Y at “Reuse existing … SSL certificate?”. Staging clears traefik.log. Production renames it to traefik_staging.log and starts a new one. Traefik is recreated. |
Your other edits in traefik.yml, rules files |
Press Y to keep your certificates. |
Set up Traefik |
| Security setups (Authelia, TinyAuth, Google OAuth, Authentik, CrowdSec) | Their middlewares-NAME.yml and chain-NAME.yml files and their config. See Login setups. Authentik also replaces authentik.yml, authentik-worker.yml and authentik-postgresql.yml. CrowdSec replaces crowdsec.yml. Authelia replaces authelia-redis.yml. |
The compose files of Authelia, TinyAuth and Google OAuth, with your label edits. See Edit labels in a compose file. Other rules files. | Copy the setup’s files and your user files first. | Change passwords and add users |
| Proxy > Traefik > Traefikify with a name you used before | app-NAME.yml, only if you answer Yes at File Provider Exists |
The file, if you answer No | Copy the file first. | Traefikify |
| Tools > ReDash | The Dashboard’s services.yaml. Your hand edits in it are lost. It restarts the Dashboard. |
The old file, saved as services.DATE_TIME.yaml. Dashify entries come back. |
Copy your lines from the saved file. | Dashboard |
| Prerequisites > Packages (Debian) | /etc/systemd/resolved.conf, set to Cloudflare and Google DNS on every run. A second run replaces the .bak copy with the changed file. |
Nothing of your DNS settings | Copy /etc/systemd/resolved.conf before the first run. |
Prerequisites |
| System > Mounts > SMB Mount | /etc/samba/credentials, early in each run, even if you cancel later. This changes the login of your earlier SMB mounts. |
Your other mount entries. It copies /etc/fstab first. |
Use the same NAS user every time. | SMB and NFS mounts |
Restore and reset
Section titled “Restore and reset”| Action | Overwrites or deletes | Keeps | Protect your change | Details |
|---|---|---|---|---|
| Tools > Backups > Restore (Pro) | Your whole Docker folder, replaced by the backup. Running containers stop. | The backup file | At “Do you want to create a current backup before restoring…”, any key but n makes one in your Backups Folder. |
Backups |
| Tools > Backups > MP Restore (Pro) | All Deployrr settings on this server, and Docker folder files that are also in the package | Docker folder files not in the package | Use it on a new server only. | Move to a new server |
| Settings > Reset | Stops and removes your app containers, then deletes unused images, volumes and networks. Clears Deployrr’s status, logs and downloaded data, and the cache. | Docker folder, app data, saved settings | Back up first. | Refresh, Reset or Remove |
| Settings > Remove | Deployrr’s configuration, saved settings, cache, scripts and logs | Your apps, images and Docker folder | Back up first. | Refresh, Reset or Remove |
Notes the tables can’t hold
Section titled “Notes the tables can’t hold”Config files a reinstall writes again
Section titled “Config files a reinstall writes again”During an install you see “Copying configuration files…”. For the apps below, this step, or a setup step right after it, writes the file again on every reinstall, even if it is already there. Your edits in it are lost, and no copy is kept. Paths are inside your Docker folder.
| App | File | What you lose |
|---|---|---|
| Deployrr Dashboard | appdata/deployrr-dashboard/config/ services.yaml, settings.yaml, widgets.yaml, bookmarks.yaml and docker.yaml |
Your layout, widgets and bookmarks. The app list keeps only the Dashboard, Socket Proxy and Traefik (if it runs). Run Tools > ReDash to add your apps back. You reinstall the Dashboard from Docker > Deployrr Dashboard, then Yes in Already Installed. See Dashboard. |
| Dashy | appdata/dashy/conf.yml |
Your whole Dashy layout. It goes back to the starter page. |
| DDNS Updater | appdata/ddns-updater/config.json |
Settings you added by hand. See After a reinstall. |
| Docker Garbage Collection | appdata/docker-gc/docker-gc-exclude |
The images you told it to keep. |
| Glances | appdata/glances/glances.conf |
Your Glances settings. |
| Mosquitto | appdata/mosquitto/config/mosquitto.conf and appdata/mosquitto/config/passwd |
Your listener changes and your MQTT users. The new passwd holds only the user you enter at the install prompts. Anonymous login stays off, so clients that use other users can’t connect until you add them again. |
| PrivateBin | appdata/privatebin/conf.php |
Your PrivateBin settings. |
| Prometheus | appdata/prometheus/config/prometheus.yml |
Your scrape jobs. |
| qBittorrent | appdata/qbittorrent/qBittorrent/qBittorrent.conf |
All qBittorrent settings and the web UI login. See Config files. |
| qBittorrent VPN | appdata/qbittorrent-vpn/qBittorrent/qBittorrent.conf is deleted |
All qBittorrent settings and the web UI login. See Config files. |
| SearXNG | appdata/searxng/settings/settings.yml and limiter.toml |
Your search settings. settings.yml also gets a new secret key. |
| Sshwifty | appdata/sshwifty/conf.json |
Your presets and settings. Deployrr fills in the web password from secrets/sshwifty_password again, and one preset for this server’s SSH port if it finds the port. |
| ViniPlay | appdata/viniplay/.env |
Nothing you set, but it gets a new session secret, so everyone has to log in again. |
Supabase’s config files and Cloudflare Tunnel’s hosts file are only written when they are missing, so a reinstall keeps your edits there. For the Traefik rules file and secrets, see the Apps and containers table.
To keep your edits:
-
Copy the file before you reinstall. For example, for Mosquitto:
Terminal window sudo cp -a YOUR_DOCKER_FOLDER/appdata/mosquitto/config ~/mosquitto-config.bak -
Reinstall the app.
-
Stop the app with Apps > Manage Apps > the app > Stop, so it can’t write the file while you copy.
-
Copy your file back over the new one, or copy only the lines you changed.
-
Use Tools > Stack Manager > Recreate for that app, so it starts and reads the file again.
Login setups
Section titled “Login setups”- TinyAuth: after a rerun,
users_fileholds only the user you typed, and that user sets up two-factor again. No copy is kept. Copyusers_filebefore the rerun. - Authelia: a rerun moves
users.ymlandconfiguration.ymlto copies with the date and time in their names. It writes new files with one user, makes new secrets and emptiesnotifications.txt. Your extra users are only in the dated copy. The run also removes all stopped containers, unused images and unused networks on the server. - Google OAuth: a rerun writes
secrets/oauth_secretsagain. Lines you added by hand are lost. Emails you entered in earlier runs come back. - CrowdSec: a rerun also rewrites
acquis.yamlandcustom-whitelists.yaml. Copy them if you edited them. It also moves CrowdSec to a new port and replaces its compose file, so run both bouncers again. See After you reinstall CrowdSec. - Traefik Bouncer: a login setup rerun and a Proxy > Traefik > Preparation rerun write chain files without the CrowdSec bouncer. See A chain file lost the bouncer.
To keep your own Traefik middleware safe from a Preparation rerun, put it in a file with your own name. See Edit Traefik rules files safely.
To avoid most of this, add users by hand. See Change passwords and add users.
Stopped apps after a cleanup
Section titled “Stopped apps after a cleanup”A cleanup, Docker Garbage Collection or an Authelia rerun can remove the container of an app you stopped. Its settings and data stay in the Docker folder. Start Container does not list removed containers. Tools > Stack Manager > Up creates them again. Up starts the whole stack, including apps you stopped on purpose, so stop those again afterwards.
To see the Docker cleanup option in use, watch Deployrr 5 walkthrough: Docker disk usage and cleanup at 27:35 (shows Deployrr v5; menus differ in v6). To understand what the prune commands behind the cleanup aliases remove, read UDMS part 13: Docker system cleanup commands (manual setup).
Check it worked
Section titled “Check it worked”-
Before the action, check your copy is there:
Terminal window ls -l ~/APP.yml.bak -
Run the action.
-
Open the file you protected and check whether your edit is still there.
-
If it is gone, copy your file back. Then use Tools > Stack Manager > Recreate for that app.
Next steps
Section titled “Next steps”- Learn which action applies a change: Restart, Recreate or Reinstall an app after a change.
- Add your own containers: Add your own containers with custom.yml.

