Skip to content

Troubleshooting

If your server is not reporting data, work through these checks in order.

  • Check the plugin is enabled: run /plugins and confirm ShardAnalytics is green.
  • Check scope: make sure the dashboard is showing the correct organization and server.
  • Check the connector: run /shardanalytics stats and confirm collection is running and the queue is not stuck at its cap.
  • Generate a new key from the server’s settings.

  • Set it on the server with:

    Terminal window
    /shardanalytics setapikey <new-api-key> confirm
  • Do not reuse one key across servers. Each server needs its own key so identity and attribution stay correct.

/shardanalytics stats reports states such as API_KEY_NOT_CONFIGURED, FAILED, and API_CONNECTIVITY_ISSUE:

  • API_KEY_NOT_CONFIGURED means no key is saved. Run setapikey.
  • FAILED after a 401 means the key was rejected. Generate a new key.
  • API_CONNECTIVITY_ISSUE means the plugin hit its retry ceiling. Check that the host allows outbound HTTPS (port 443) to the API, then let the plugin retry or force re-authentication with /shardanalytics stats auth.

No inbound ports are required; the connector only makes outbound connections.

  • Metrics lag slightly: collection and processing are asynchronous. A short delay is normal.
  • A stream is missing: check the connector configuration and the readiness panel before assuming the server is idle.
  • Retries are backing up: stats shows retry queue statistics. Use /shardanalytics stats retry to trigger a retry cycle.
  • Supported today: Paper servers.
  • Java: the connector requires Java 21.
  • Other server software is not verified. Check the connector release notes before installing on an unverified platform.

The dashboard shows the running connector version on the server Overview and Plugins pages. To update, replace the jar in plugins/ and restart. See Connector Updates.

Ask in the ShardAnalytics Discord with the output of /shardanalytics stats and the server platform you run.