Connect the cloud dashboard
Link once, check the heartbeat, and distinguish saved settings from runtime changes.
Customer access
The web wizard and dashboard are cloud services. Access links and activation instructions are provided to licensed buyers. Follow customer instructions for product verification and adding a server. Public docs do not include portal addresses or account screenshots.
The old embedded setup HTTP UI has been removed. /nusa setup web only points to customer cloud access; legacy management-web settings cannot start it again. Console setup and status remain available.
Link your server
Copy the server-specific linking command and run it in your private console. Its basic form is:
nusa link <SERVER_TOKEN_FROM_CUSTOMER_ACCESS>
nusa link statusThe placeholder is not a usable token. Never place a real token in player chat, public tickets, screenshots, or examples. If customer instructions include an additional address argument, use that supplied command unchanged rather than guessing an endpoint.
Credentials are saved in nusa-cloud-bridge.properties for reconnects after restart. Keep this file private and preserve it only in protected migration backups.
nusa link status shows the connection stage and heartbeat age. Saved credentials do not prove an online connection. The dashboard may show stale data when heartbeats stop. nusa link off, or alias nusa link unlink, disconnects and removes saved credentials.
Review and restart
The cloud guide follows Server, Players, Hardware, and Review. Check estimates against the actual hosting allocation and inspect the diff/preset effects. The bridge can save configuration with a backup on main; a successful save does not activate startup settings. Review the saved file, restart fully, and verify the result.
Do not assume every cloud release has the same all-page and revision validation guarantees as the console transaction. For important changes, use the locally verified console workflow or inspect the saved file before restarting. Keep independent backups.
Understand the data scope
The bridge sends hardware/version information, plugin names and versions, current configuration during linking, and operational telemetry. Treat a linked service as administrative access. This is broader than the restricted AI-advisor context. Avoid unnecessary secrets in configuration and review the customer instructions before linking.
For offline/stale data, compare local status and follow connection troubleshooting.