Remove or uninstall

Choose the action that matches what you want:

The one exception is a migration source, which Deplo does uninstall itself from, because that role exists precisely to be temporary.

Remove a server from DeploCopy Anchor Link

The machine running the control plane cannot remove itself.

Any pending teardowns for that server are dropped with it, so Deplo stops retrying instructions nobody can carry out.

Uninstall the agent from a hostCopy Anchor Link

uninstall.sh does both host-side jobs. The dashboard's command uses --agent-only. On the control-plane host, that also removes Traefik, so the panel stops answering until you re-run install.sh.

The script is a dry run by default. Running it with no flags prints exactly what it would do and changes nothing.

# See what would happen
curl -fsSL https://deplo.example.com/uninstall.sh | sudo bash -s -- --agent-only

# Do it
curl -fsSL https://deplo.example.com/uninstall.sh | sudo bash -s -- --yes --agent-only

# Do it, and delete the data too
curl -fsSL https://deplo.example.com/uninstall.sh | sudo bash -s -- --yes --agent-only --purge-data

It never touches Docker Engine itself or a container Deplo did not label. Full flag reference: uninstall.sh. If the panel is unreachable, download the script from https://deplo.build/uninstall.sh.

On the machine running the control plane that directory's traefik entry is a symlink into /opt/deplo, so removing it takes the link rather than the certificates behind it. There the certificates live with the rest of /opt/deplo.

Uninstall Deplo itselfCopy Anchor Link

Run the same script without --agent-only. It also removes /opt/deplo, the panel, its Postgres, its Traefik, and Deplo-managed containers on that host.

# See what would happen
curl -fsSL https://deplo.example.com/uninstall.sh | sudo bash

# Do it, keeping every volume and /opt/deplo
curl -fsSL https://deplo.example.com/uninstall.sh | sudo bash -s -- --yes

# Do it, and delete the data with it
curl -fsSL https://deplo.example.com/uninstall.sh | sudo bash -s -- --yes --purge-data

# And the backups stored on this machine
curl -fsSL https://deplo.example.com/uninstall.sh | sudo bash -s -- --yes --purge-data --purge-backups

Order matters, and the script handles it: the panel and its Postgres stop before Traefik and the deplo network go away under them.

--purge-backups is separate for the same reason: everything else on the machine can be rebuilt from a backup, and those are the backups.

Moving the instance rather than ending it? Take disaster recovery first and uninstall second.

Decommission a machine properlyCopy Anchor Link

For the machine running the panel, steps 4 and 5 are one command: uninstall without --agent-only.

Before you remove the hostCopy Anchor Link

• Removing a server does not stop its containers. They keep running, unmanaged, until somebody stops them. That is why the uninstall step exists.
• Apps still assigned to a removed server cannot deploy. Move them first.
• Reinstalling an agent re-bootstraps from scratch. The installer deletes the existing certificate files, so it genuinely re-enrolls against the new pin rather than half-trusting the old one.
• A migration source is removed with Remove from Deplo, and Deplo uninstalls its own agent from that machine as part of it.
• The panel cannot uninstall itself. Nothing in the dashboard removes the control plane, it is the thing doing the removing. That is what the host-side script is for.
• Docker Engine and /etc/docker/daemon.json stay. The installer widened Docker's address pools and kept your original as daemon.json.deplo-bak. Putting it back needs a Docker restart, which stops every container on the machine, so the uninstaller only tells you it is there.

TroubleshootingCopy Anchor Link

The uninstall script does nothing (it is a dry run, add --yes), containers survive an uninstall, or a removed server reappears: see Servers and agents troubleshooting.

Next stepsCopy Anchor Link