DocsCommon Issues
docs.backToHome

Documentation

Common issues

Troubleshooting installation, config sync, dashboard, and keys.

Installation & startup

Anti-Cheat not starting

Redeem your Tebex order on the Keys page, install EZAC from your Cfx.re portal, and add set ezac_license "YOUR-KEY" to server.cfg. Check the server console for Lua errors and ensure OneSync is enabled.

Configuration not applying

Redeem the Tebex order on Keys for that server, then start EZAC with ezac_license set in server.cfg. Config syncs automatically once the key is linked.

Resource fails to start (Lua errors)

Use the resource from your Cfx.re portal. The folder must be named so ensure EZAC works. Check the server console for the exact error. OneSync must be enabled.

Dashboard & keys

Key invalid or already used

Keys are one per server. Paste the Tebex order ID on Keys, then put that key in server.cfg. If that order was already used on another server, you need a new purchase.

Cannot see Configuration or Download

Create a server on Keys, paste the Tebex order ID, and generate. Until a key is linked, Configuration and Setup stay locked.

No servers in the list

Create a server on the Keys page, then paste the Tebex order ID and generate.

Whitelist & staff

Staff live on Dashboard → Admins (add by Discord ID). Full whitelist skips every detection; turn it off and use Skip detections to ignore only things like NoClip or Teleport. Non-staff players go on Dashboard → Whitelist by Discord ID or identifier — they skip detections but do not get an admin menu. You do not need to edit auth.lua.

Players list empty

The dashboard player list is filled by the EZAC resource (live sync every few seconds) and by txAdmin player data when present. EZAC automatically finds and loads txData/default/data/playersDB.json on start and every 60 seconds — no extra setup. If you see no players:

  • Ensure the server is running, EZAC came from your Cfx.re portal, and ezac_license is set in server.cfg.
  • With EZAC_AUTH.Debug = true in auth.lua, check the server console for "Players sync POST returned status …" — a non-200 code means the dashboard URL or key may be wrong.

If you use a custom txData path, ensure playersDB.json is at txData/<profile>/data/playersDB.json relative to your server root (where FXServer runs). EZAC derives the server root from the resource path.

Support

Join our Discord at discord.gg/ezac for help, key redemption, and setup — use Get Support in the docs sidebar or top bar. For false bans and tuning detections, see Common false bans.

Common false bans · Installation · Configuration