Invalid registration token
A remote storage node called /api/storage-node/register with a token that did not match the server’s registrationTokenHash (403). This is not a member signup error.
Why this happens
verifyRegistrationToken failed — wrong token pasted into the node package, truncated copy, token from a different storage server row, or already rotated. Expired tokens and “already connected” use different messages.
Diagnose and fix
1. Admin: open the storage server row; copy a fresh registration token / re-provision if needed.
2. On the node: paste the exact token; reconnect (Connect and enable the storage node).
3. Do not reuse a token after successful connect.
4. See Provision a remote storage server (token + package) for the full flow.