Player and dashboard connections

Players cannot connect

Confirm startup readiness and a running process. Check client 1.21.11, address, game port, and panel allocation. Localhost tests only the local route. External access also depends on firewalls, routers/providers, and proxy topology.

Do not publish private addresses or disable authentication as an arbitrary test. For a proxy, inspect forwarding and protected backend access using the integration guide. Invalid runtime authorization can also reject login.

Dashboard offline or stale

1. Run nusa status to confirm local responsiveness.
2. Run nusa link status privately and inspect the connection stage and heartbeat age.
3. Check outbound HTTPS, system time, customer entitlement, and saved credentials.
4. After recovery, allow another connection cycle. A saved file does not prove handshake success.
5. If access was replaced/revoked, use the new customer linking instructions.

Do not open the retired setup port or share tokens, private endpoints, or bridge files. See cloud connection for deliberate unlinking.

Apply fails or settings look unchanged

A console preview can expire, have unread pages, or use an outdated config revision. Create a new preview and read all pages. Check directory permissions and atomic replacement support.

For cloud changes, verify the server’s save result and backup, then review the file and restart. A UI acknowledgement alone does not prove startup settings are active. Use the verified console wizard when local validation guarantees are important.

Analysis is unavailable

An AI flag does not establish an active service after embedded UI removal. Do not try retired routes or enter provider keys in the browser. Use local advice and read advisor availability.