Factory reset

Factory reset clears your Dopbase accounts and project data so you can start setup again. Only root can use it from the Admin UI or from the server host.

Full instance reset

Factory reset removes every project, environment, secret, user account, access token, audit record, and backup from the active instance. This includes the root account and signs everyone out. The Admin UI deletes this data. The host command saves the complete data directory as a ZIP before removing it.

This action cannot be undone from the console. Do not continue unless you understand what will be removed and no longer need the data.

Before you continue

• Check that you are connected to the correct instance.
• Tell other users and stop applications that depend on its secrets.
• Keep any data you need outside this instance. Backups left on the server will also be deleted.
• Make sure you have access to the server to complete setup afterward.

Confirm the reset

Admin UI

1. Sign in as root and open Instance.
2. In Danger Zone, choose Review factory reset.
3. Review the counts of accounts, projects, secrets, tokens, and backups that will be removed.
4. Acknowledge that the deletion is permanent.
5. Type FACTORY RESET exactly and enter your root password.
6. Choose Permanently reset instance only when you are ready.

If you are unsure, cancel before the final confirmation.

Server host

Stop the Dopbase server, then run:

dopbase admin factory-reset

The command reads the local server configuration and refuses to continue if the server still holds the database lock. It displays the exact data directory, then requires please-wipe-out-system and the Dopbase root password. The phrase is case-sensitive and does not allow extra spaces. There is no flag to bypass the prompts.

Use --data-dir or --config when the instance does not use the default path. The command writes the whole data directory to a timestamped ZIP beside the directory, then removes the active data. The ZIP includes every database, master-key, configuration, backup, log, and local CLI file stored inside the directory. Files configured outside the data directory are not included.

To reset without creating the ZIP, run:

dopbase admin factory-reset --no-backup

This mode permanently removes the data after the same confirmation phrase and root-password checks. Keep an external backup before using it.

After reset

Everyone must use new credentials after setup. Applications and agents will need new access tokens.

Factory reset does not uninstall the Dopbase binary. The Admin UI keeps the deployment settings and master key. The host command moves any settings and key stored inside the data directory, so the next setup uses defaults unless you provide configuration elsewhere. Neither method removes files saved on client devices or securely erases the underlying disk.

Stop any process still using the reset instance. After a completed reset, dopbase server start enters automatic setup using the same instance options. For backup restoration, omit DOPBASE_ROOT_EMAIL during startup or use dopbase server setup --web. If .factory-reset.pending remains after an interruption, startup stops without deleting more data. Run explicit setup using the same data directory and configuration options to complete recovery. See setup and sign in.