Skip to main content

Send the NodeVault key to a node again

A node opens your NodeVault secrets only while it holds your organization's NodeVault key. A node you reinstalled or wiped has lost the key and its own identity key with it, and a delivery can fail on its way. Either way, tasks on that node can't open a NodeVault secret until the node has the key again. Jaah sends the key again from a node that still holds it; nobody has to upload the key by hand.

Who can do this: Org Owners and Org Admins, once NodeVault is set up.

  1. In the sidebar, select Settings, then Features, then NodeVault.
  2. Find the node in the Nodes list and read the chip at the end of its row:
    • Delivered: the node holds the key. Nothing to do.
    • Delivering, Failed — retrying or Waiting (offline): Jaah is still trying, or waits for the node to come back online. Wait, then read the list again.
    • Waiting for a node that holds the key: bring a node that shows Delivered online.
    • Failed: go to step 3.
    • Identity changed: go to step 4.
  3. For Failed, read the line under the row, such as Node didn’t answer in time, and select Retry. If the line says Node can’t run NodeVault encryption. Update Jaah on it., update Jaah on that node first.
  4. For Identity changed, the line reads Identity key changed — reset to re-enroll. Do this only if you reinstalled or wiped the node yourself. Select Reset identity.
  5. In Reset identity?, check the node's name and select Reset. Jaah forgets the node's old identity key and its key deliveries.
  6. Wait for the node to register its new identity key. Its row then shows a Fingerprint, and a node that holds the key sends the key to it.
  7. Before you trust the node, run jaah nodevault fingerprint on that machine and compare what it prints with the Fingerprint in its row. Hover the short fingerprint to read it in full. They must match.
  8. Check that the chip reads Delivered.

Reset only a node you know was reinstalled or wiped. If nobody did that and the node still shows Identity changed, find out why before you reset it, starting with Audit, beside Rotate key.

When no node holds the key​

When every node that held the key is gone, there is nothing to resend it from, and Rotate key can't help either: it also needs an online node that holds the current key. The Org Owner then sees Start over beside Rotate key. It retires the key, every secret sealed with it must be typed again, and NodeVault is set up afresh with a new key. Select it only when no node that held the key can be brought back online.