Operate, upgrade and recover Canvus MCP
Keep state/ (including SQLite journal/WAL, approvals, nonces, tombstones,
operation receipts and uploads) together with its original state.key and
configuration. Retain every installed manual snapshot, not only CURRENT.
Backup
Stop new requests and let Compose stop the service gracefully before a filesystem backup. Back up the complete installation with file ownership and permissions preserved, using your existing encrypted backup system. Restart the same image after backup. Do not copy just the SQLite main file while it is running.
Upgrade
Read the new release's state compatibility declaration first. Verify/import the
new archive, stop the service, back up the current installation, and replace
only release-owned files: image ID in .env, Compose/proxy templates when needed,
notices and public CA roots. Merge new manual snapshots without deleting retained
ones; update CURRENT only after verifying the new snapshot. Preserve customer CA
additions and configuration. Start with the new image and check readiness and
client authentication. Never rerun bootstrap or replace state.key.
Rollback and uncertain operations
No downgrade or cross-version rollback is qualified by this first customer release, 26.11.0. Same-artifact restart with durable authority and receipts was verified. Use a forward fix unless a release explicitly proves its older executable can use the current durable state. Ordinary software rollback must not restore an old database: doing so can revive revoked authority, consumed approvals or already dispatched writes. Keep the current journal, key and uploads, even when reverting compatible executables.
After a timeout, retrieve the existing operation receipt/status. An uncertain mutation is not permission to retry create/copy/delete. Reconcile using reads; never automatically replay it. The server-side atomic receipt journal must also remain intact after resources are deleted.
Disaster recovery from backup is not ordinary rollback. If newer state has been lost, isolate the endpoint and contact MultiTaction support before allowing writes; the backup may predate revocations or committed operations. A lost key cannot be replaced against the old encrypted database.
Uninstall
cd /opt/canvus-mcp
sudo docker compose down
This stops the service while retaining bind-mounted state, key, configuration, uploads and manual. Remove proxy routing separately. Do not delete data as an uninstall default. Retention/deletion is the customer's explicit decision.
Troubleshooting
Check docker compose ps and the static healthcheck first. Inspect service logs
locally; do not share tokens, authorization URLs, credentials, state databases or
keys with support. Supply the release version, image ID, manifest checksum, Canvus
version, exact error and timestamps. 421 means the proxy Host differs from the
canonical origin; 403 from a browser may mean its exact Origin is not allowed.
TLS errors require the correct CA chain, never insecure TLS. A missing manual or
unwritable UID65532 state must be repaired before claiming installation success.