docs
Uninstall and clean up
Removing the app from your computer deliberately does not touch your server. Here is how to clean the server too, when you actually want that.
Uninstalling the desktop app
Removing MihraOps deletes its local records — your server list and the stored fingerprints. Your servers keep running exactly as they are, which is almost always what you want: your applications should not stop because you uninstalled a management tool.
What is on the server
Depending on which features you used: ~/.mihraops/ holds Compose projects, application definitions and encrypted secrets; ~/.config/mihraops/keys/master.key is the key that encrypts those secrets; /opt/mihraops/caddy is the reverse proxy configuration; /opt/mihraops/sites holds static site content; /opt/mihraops/agent holds webhook, monitoring, incident and delivery Agent data.
Two containers may be running: mihraops-caddy and mihraops-agent.
Remove the managed pieces
Do this over SSH, on a server you no longer want MihraOps to manage. Removing the proxy takes down HTTPS for every domain it was serving, so make sure something else is ready to serve them first.
Stop and remove the MihraOps components
docker rm -f mihraops-agent mihraops-caddy sudo rm -rf /opt/mihraops rm -rf ~/.mihraops ~/.config/mihraops
Your own applications stay
The containers you deployed are ordinary Docker containers and the commands above do not touch them. Remove them with docker rm -f <name>, or bring a Compose stack down with docker compose down from its project directory, before you delete ~/.mihraops if you want the compose files as a reference.