Accessing the Web Panel
After launching Nexus Core, open your browser and navigate to:Connection Parameters
Security Key
TheNEXUS_SIGNING_KEY environment variable controls HMAC-SHA256 message authentication. Since v1.5.1, signing is fully symmetric: Nexus Core verifies signatures on inbound packets and also signs all outbound responses (including DataAddon publish operations and heartbeat messages).
Set the key before launching the process:
If
NEXUS_SIGNING_KEY is not set, both inbound verification and outbound signing are disabled. A one-time warning is logged at startup. This is acceptable only in local development environments.What Gets Signed (v1.5.1)
Production Checklist
- Set
NEXUS_SIGNING_KEYon every node (Nexus Core and all Spigot servers) before deployment. - Keep all server clocks synchronized with NTP. Timestamp validation uses a 5-minute window; drift beyond that causes valid packets to be rejected.
- Use a MongoDB URI with authentication in production (e.g.
mongodb://user:pass@host:27017/nexus_core_db). - Bind Redis to a private network interface and enable password authentication. Do not expose it to the public internet.
Related Topics
- Installation — building and running Nexus Core from source
- Security — how HMAC signing, timestamp validation, and nonce protection work together
- Quickstart — registering your first DataAddon