Advanced server settings

The saved vault is encrypted; do not edit qkvm.json or qkvm.bak as text. The settings in the web UI continue to work normally. For custom public DNS names and retention limits that previously required a hand edit, stop qKVM and create a small configuration file, for example server-settings.json:

{"allowed_hosts": ["kvm.example.com"], "history_days": 90, "history_mb": 200, "activity_mb": 100}

Apply it using the same OS account that runs the server and its original storage key:

qkvm --data-dir /path/to/data --vault-key-file /path/to/private/vault.key --configure-server server-settings.json

Then restart qKVM. Only the four fields shown above are accepted; omitted fields stay unchanged, and allowed_hosts replaces the complete additional-host list. Use host names without schemes, paths, ports or wildcards; an empty list removes the additions. This command cannot change accounts, credentials, MFA, or permissions. It holds the same instance lock as the server and refuses to run against an active instance. It validates both encrypted settings copies before applying the change. This is an OS-owner administration command, not an API for bypassing web permissions.