Troubleshooting
Dashboard stays disconnected
Check that the resource is running in the server console. Confirm the folder contains fxmanifest.lua and voidac.key, then run refresh and ensure VoidAC. Check outbound HTTPS connectivity from the FiveM host to api.voidac.eu.
Read the [VoidAC] or [VoidAC License] error before changing settings. The dashboard cannot receive live telemetry from a stopped resource.
Unable to validate voidac.key
The key file must be in the resource root and contain exactly 32 letters/numbers, without an extra label, JSON or copied dashboard license key.
If you downloaded a new package, the old resource key was replaced. Install the complete new package, including its key, and restart VoidAC. Check that the license is active and has not expired.
IP mismatch
Each license binds to the first validated public server IP. Request an IP reset and wait for approval. A fresh download does not remove the binding. The resource stops after a rejected validation; repeatedly restarting it will not fix a mismatched IP.
Player cannot join
Check the rejection message and corresponding server-console entry. An existing ban, Antispoof mismatch and temporary API-validation error are different problems.
For a device change, follow Antispoof approval. Do not clear bans or device bindings to troubleshoot a network failure. For an unexpected detection, inspect its reason and evidence and test the specific conflicting method.
FILE CHANGED / LICENSE_VALIDATION
Keep the resource folder named VoidAC and do not rename any of its original scripts. The upcoming protected build also rejects a changed resource name. Reinstall the complete package if this check fails. Read integrity and request limits for the reason and recovery steps.
If the console says File changed: fxmanifest.lua, file verification failed before license or ban validation. Compare the file with the manifest from your downloaded package. From 1.8.32, standalone external script references may be added at top level, but the original content must remain unchanged. Statements inside code blocks, modified original lines, traversal paths and duplicate added references are rejected. Older releases may still require the previous strict format. See Manifest integrations. Never edit the signed integrity inventory.
Add add_ace resource.VoidAC command.stop allow before ensure VoidAC. This lets a failed resource close existing connection checks and stop itself. Without that permission, it remains disabled and tells the administrator to run stop VoidAC manually.
A separate ESX no identifier found error comes from the gameplay framework, not a confirmed VoidAC ban. Likewise, a second anticheat can run its own connection checks. Preserve the actual rejection Reference and console logs when investigating; do not remove a valid ban just to make the connection succeed.
Update button does not complete
- The FiveM server must be connected, and you need Settings → Edit.
- Versions 1.8.10 or older need a one-time manual installation of the latest package.
- The FiveM process must be able to write inside the resource folder.
- Add
add_ace resource.VoidAC command.restart allowbeforeensure VoidAC. - Check the progress dialog and
[VoidAC Update]console output for the actual failure.
For a full server restart, also check txAdmin supervision, voidac_dashboard_restart and the separate command.quit permission. See installation guide.
Discord returns HTTP 429
Discord has rate-limited the webhook. Current releases queue and retry using Discord's delay. Leave the queue to drain and check whether several resources or servers are posting to the same webhook. Do not create more events to test it while it is throttled.
For persistent failures, verify the saved webhook URL and check whether it was deleted in Discord. Replace a compromised webhook rather than sharing its address in a ticket.
No screenshot or recording
Check the client/NUI capture errors and server upload logs at the incident time. A client that has just joined may not yet have a complete recording buffer; a disconnected client may not finish its upload. Manual bans may have no automatic capture.
See Bans & evidence. Missing media does not mean the ban was not saved.
Map or monitoring is delayed
Check that the resource is connected and the selected players are still online. Close streams you do not need and check the player's connection and capture errors. Loading the 3D map for the first time is separate from receiving live player positions.
Ask for support
Create a ticket in the VoidAC Discord with the resource version, server ID, time of the problem, exact error and what changed before it happened.
Remove license keys, voidac.key, webhook URLs, passwords and private player information from screenshots and logs. Do not post your full configuration publicly.
