Troubleshoot the FiveM resource

In short. Always start in two places: the game server console (the [agora] lines) and Server → Players in Agora (the last signal received). Then turn on Verbose log (debug) in Administration → Configuration → Agora resource: it applies live.

No signal received #

Server → Players says no signal was received: the agora resource is not deployed yet or cannot reach Agora. Check in this order:

1. The resource is started: ensure agora in server.cfg, after the framework, then refresh and ensure agora.
2. The game server reaches the site: from the game server machine, open SITE-ADDRESS/api/health.
3. The embedded address is right: Administration → Configuration → Agora resource shows the address bundled in the resource. If it is wrong, fix it in Administration → Configuration → Site identity and redeploy. When the deployed resource's address differs from the site's, a banner says so too: "The resource points to … Redeploy it so it follows", with a Redeploy button.

Secret refused #

Console: [agora] presence: Agora responded 401 (check the URL or the secret). Or the tablet opens on the sign-in screen.

Cause: the secret in config.server.lua no longer matches the site's (secret regenerated since deployment). Fix: download or redeploy the resource again.

If the line says instead Agora responded 0 (or 502…) "site unreachable or restarting — retrying automatically", neither the address nor the secret is at fault: the site is restarting or down (update, outage). The resource retries by itself; check SITE-ADDRESS/api/health if it lasts.

"Agora responded 301" (or 302): a redirect #

Console: [agora] presence: Agora responded 301 (check the URL or the secret). Since resource 0.3.2, the resource no longer follows any redirect: if Agora's address answers with a 301 or 302, the answer is treated as an ordinary error. Otherwise the shared secret would have been re-sent as is to the new address, possibly another host, possibly plain http. Agora itself never redirects its /api/ingame routes: the problem comes from the address or from a reverse proxy in front of it.

Fix: put the final address (the one that answers without a redirect, over https) in Administration → Configuration → Site identity, then download or redeploy the resource again. See also Behind a proxy. The option is supported by recent FXServer builds; a very old build simply ignores it.

"REFUSED: … is neither https nor on your local network" #

The resource refuses to send the secret in clear over the Internet. Put the site on https, or give the site's private address if the game server is on the same network. See config.lua and the secret.

OneSync missing #

Console, in yellow: "live map: OneSync disabled — fallback: CLIENTS send their position…". Everything works, but clients do work for the map. Turn OneSync on (onesync on, on by default on recent artifacts).

The tablet opens on a blank page #

Messages players see #

Command already taken #

Console, in yellow: "the /911 command is already used by resource “…”: Agora will not override it". Another dispatch script took the command. Change the Call command name in Administration → Configuration → Agora resource (takes effect at the next resource restart), or keep the other script.

Framework not found #

On the site side, Server → Database says under the Framework dropdown what Agora detected, or why nothing is: see Supported frameworks.

Lua errors #

The resource's errors (since 1.9.9, so also in the current 0.3.3) also reach Administration → Errors, source FiveM resource. After an Agora update, redeploy the resource: an outdated resource does not send everything.

Before opening a ticket #

Note the version (Server → Players), turn on the verbose log, and copy the [agora] lines from the console. Never send config.server.lua.