Common problems
Fixes for the problems server owners hit most: no link code, an unreachable ingest, a server that stays Waiting, empty charts and a resumed server that collects nothing.
Run /analytics status first (/analyticsv status on Velocity). Its State and Last send lines tell you which problem below you have. The lines are explained in Commands.
The console never prints a link code#
- The loader stopped at the licence and says so before the agent starts. A jar bought on BuiltByBit carries its licence, so there is no key to add: ask on the Exylia Discord.
- The server is already linked.
data/credentials.jsonexists, perhaps copied from another server./analytics statusshows the workspace; run/analytics unlinkthen/analytics linkif it is the wrong one. - The ingest cannot be reached. The console says "Could not request a link code (…); retrying". See the next problem.
- The code expired. A code lives ten minutes: run
/analytics linkfor a new one.
"Could not reach Exylia Analytics"#
The server cannot open an HTTPS connection to analytics-ingest.exylia.net. Usual causes are a host that blocks outgoing traffic, a firewall that allows only some ports, or a DNS failure. Nothing is lost meanwhile: events wait in data/spool/ (up to 50 MiB) and go out oldest first once the connection is back. Last send in the status shows the next retry.
The code is refused on the link page#
"That code is unknown, expired or already used." Codes work once and live ten minutes. If the workspace you want is not in the list, your role cannot link servers there. See Connect your server.
The status says Waiting: "Another running server holds this token"#
Two processes send with one token, almost always because a plugin folder was copied with data/credentials.json inside. The ingest accepts one and refuses the other, which keeps its events and retries every minute. On the copy, run /analytics unlink, then /analytics link and approve the new code. See Installation.
The status says "Disabled from the dashboard"#
The server is paused on the Servers page. A paused agent sends nothing, so it never hears that it was resumed: after you click Resume, run /analytics reload on it (or /analyticsv reload on the proxy), or restart it.
The server is linked but the charts are empty#
| Check | Where |
|---|---|
| The server reports | Servers: status Online with a recent heartbeat. |
| It is not paused | Servers: not Disabled. |
| The range has data | Pick a longer range. Most charts need at least a full day of sessions. |
| A network has its proxy | Without a linked Velocity proxy nobody reports sessions, so players, retention and acquisition stay empty. Backends alone only fill Performance, Economy and Placeholders. |
| The module is on | Settings → Agent. With Sessions off almost everything is empty. |
| You can see the page | Your role may not include it. |
Economy shows nothing#
The Economy module must be on and the server must be Paper or Spigot. /analytics status lists the sources it hooked on the Economy line. With only a Vault economy, check the Vault line: the wrapper may be off in config.yml, or the economy may hold the highest priority itself. Plugins that grabbed the economy before the first tick are not seen: see Economy.
"The installed loader is outdated"#
The loader jar is older than the economy or market API. Custom events still work. Replace Exylia-Analytics-Loader.jar with the current one; the agent itself updates with a plain restart.
"The workspace is suspended"#
The dashboard refused the server's events because the workspace is suspended. The console text also says "plan quota", but the dashboard has no quotas. Events are kept and retried every 15 minutes. Ask on the Exylia Discord.
Something missing on this page? Tell us on Discord