Testing the deployment

Verify registration, policy decisions, signing, persistence, and recovery before production use

Test a Virtual Signer on a disposable vault with no real assets before you give it production signing weight. Use the approval policy and deployment topology you intend to run in production.

Check health and identity

For the ports in Deploy self-hosted:

curl --fail-with-body 'http://127.0.0.1:2114/core/v1/health?strict=true'
curl --fail-with-body 'http://127.0.0.1:8182/broker/v1/health?strict=true'

Both return 200 and JSON with status: "ok" when healthy. The Broker check probes its connection to MPC Core and its MQTT credentials. The Core check tests MQTT connectivity. If a strict check returns 503, inspect the probe details in the response.

Confirm the signer ID and organisation in the Dashboard or the API. Record the ID, so you can confirm it's unchanged after a restart.

Exercise the full workflow

TestExpected result
Create a vault with a policy-approved key-generation requestThe vault completes key generation and has a public key.
Submit an allowed signing requestPolicy returns approve; an eligible signer set completes signing; the signature verifies against the payload and vault public key.
Submit a disallowed requestThis signer doesn't approve. The request can still complete if other signers meet the threshold.
Policy returns abstain, malformed JSON, or HTTP 4xxNo approval from this signer.
Policy is unavailable, times out, or returns HTTP 5xxThe signer retries a limited number of times, then rejects, as described in Custom policy server.
Disconnect a required signerThe request isn't reported as signed only because approvals exist.
Reshare the test vaultThe vault shows the new membership, keeps its public key, and the new signing set can sign.
Restart containers and reboot the hostThe same signer ID and shares remain usable; repeat signing successfully.
Restore a backup in an isolated recovery exerciseYour restore procedure works without two copies of the same signer identity running.

Export a new recovery bundle after key generation and after resharing, and verify it as described in Virtual Signer disaster recovery. Store it off the signer host.

Development smoke tests

On a disposable development signer, Always approve can help isolate connectivity problems. You don't need it to deploy, and you must never use it with production vaults.

The Virtual Signer seals its approval mode when it registers. You can't register a signer with always-approve and later switch it to api-approval. Create the production signer with its reviewed policy configuration from the start.

Record the result

Keep the tested image versions, signer ID, vault ID, request IDs, policy decisions, and final outcomes in your deployment record. Repeat the relevant checks after changing an image, policy, network, certificate, or storage configuration.


Did this page help you?