Skip to content

Uninstall

Gibran Khan edited this page Nov 16, 2026 · 1 revision

Uninstall an instance

Normal removal deletes the selected instance's jails/VM registration, private networking and owned startup configuration. Application datasets, their snapshots and office VM disks stay on the host. Other instances and shared infrastructure remain.

Use the original installer as root. Save and close editors, disconnect clients and end calls. Keep console access and a second independent SSH connection. Removal is attended and has no --yes flag. Preserve any jail-local TLS keys or service settings you need before removal; these are not all kept with the application data.

1. Select the instance

sh install.sh list
sh install.sh status INSTANCE
sh install.sh remove INSTANCE

Replace INSTANCE with your name, or choose Uninstall instance in the menu.

2. Choose an optional SQL/configuration capture

Removal asks whether to capture Nextcloud SQL and configuration. Alternatively, choose one command:

sh install.sh remove INSTANCE --backup
# Or explicitly skip capture:
sh install.sh remove INSTANCE --no-backup

With --backup, optional --backup-output DIRECTORY selects a new absolute private directory outside the instance's data, jail roots and saved state. Its parent directory must already exist. Capture needs a ready instance and does not start stopped services.

Optional database and configuration capture

The capture includes database records such as accounts, contacts and calendars, not user files or data-directory encryption keys. It is manual-recovery material, not accepted by ordinary Restore, and may be older than the retained files/database. It is not a full synchronized backup. Keep your own tested backups.

A requested capture failure stops removal before runtime deletion. Read the error and check affected services. Skipping afterward requires exact SKIP-BACKUP INSTANCE and a fresh removal confirmation.

3. Confirm removal and management access

Review the instance, URL, services and retained-storage summary, then type exact:

REMOVE INSTANCE

For cloud, type REMOVE cloud. This also confirms that editors are saved/closed and clients disconnected. Unsaved work may be lost.

Instance removal confirmation

If ownership, mount or shutdown checks fail, follow the message; do not force deletion or clear safety checks. When asked for KEEP, open a new independent host SSH connection, confirm access and type KEEP before the deadline. Your existing session is not enough; missing confirmation causes network rollback.

4. Check retained storage

Normal removal retains:

  • Application datasets and their snapshots: files, Nextcloud configuration, physical databases, data-directory encryption keys and office storage/VM disks.
  • Existing backups, host credentials and private audit records.
  • The removed-instance record and reserved name.

Copy retained storage privately, preserving ownership and permissions. Shared packages and Bastille infrastructure remain.

Retained data is not automatic reinstallation or full disaster recovery. If database shutdown is reported unverified, do not treat the database as a clean offline copy. Check the final message and sh install.sh status INSTANCE; follow recovery instructions with the original installer if removal stops.

Permanently delete application data

sh install.sh remove INSTANCE --purge-data

This also destroys owned application datasets and snapshots, including VM disks. It requires exact PURGE INSTANCE instead of REMOVE INSTANCE. Purge is irreversible and is not the default. An optional SQL capture does not replace a full backup. Existing backups, host credentials, audit records and the reserved name remain even after purge.

Installation guide · Recipe installation

Clone this wiki locally