Skip to main content

Common Errors

Console Commands

The resource registers two server console commands for testing:

Enable Debug Mode

Debug mode prints detailed information about every API poll and command execution to the server console. Enable it by setting Config.Debug = true in config.lua:
Then restart the resource:
Check the server console for lines prefixed with [RMZ]. These will show:
  • Each poll request and response
  • Commands being executed and their results
  • Confirmation callbacks to the RMZ API
Disable debug mode in production (Config.Debug = false) to keep your console clean. Only enable it when actively troubleshooting an issue.

Connection Status

On the FiveM Servers page in your RMZ dashboard, each server shows a connection indicator:

Resource Not Starting

If the resource does not start or you see no [RMZ] output in the console:
  1. Confirm the resource folder is named rmz-fivem and is inside your resources/ directory
  2. Confirm ensure rmz-fivem is in your server.cfg
  3. Check that config.lua has a valid secret key set
  4. Verify your server can reach https://fivem.rmz.gg (check firewall rules)

Commands Not Executing

If orders are completing but commands are not running on the server:
1

Enable debug mode

Set Config.Debug = true and restart the resource.
2

Check the console

Look for [RMZ] messages. Are polls succeeding? Are commands being received?
3

Verify the benefit is attached

In the RMZ dashboard, confirm the FiveM benefit is attached to the product.
4

Check online-required setting

If “Execute only when player is online” is enabled, commands wait until the player joins. Test with this setting disabled first.
5

Test the command manually

Copy the exact command from the debug output and run it in your server console. If it fails there, the issue is with the command itself, not the RMZ integration.

Security Tips

  • Regenerate your secret key immediately if it is ever exposed publicly
  • Use IP whitelisting in the dashboard to restrict which server IPs can poll
  • Do not commit config.lua with your real secret key to any public repository