Skip to main content
If something’s not working, check the F8 console (client) and your server console, filtered for [nexdev_djsystem]. Most issues print a clear reason there. Setting Config.Debug = true and restarting draws every sound point’s radius as a ring on the ground. For anything audio-related, do that first.

​
There is no audio

Work down this list in order.
  1. Is the panel showing a track as playing? If not, this is a playback problem, not an audio problem — see the next section.
  2. Streamer mode. It mutes the audio locally by design. Run /djstreamer to check.
  3. Volume. Three faders stack: the DJ’s master volume, your own my volume slider on the settings tab, and the booth’s maxVolume ceiling. Any of them at zero is silence.
  4. Distance. You have to be inside a sound point’s radius. Turn on Config.Debug and look for the ring.
  5. The audible-range slider. It scales every radius proportionally. If a DJ dragged it to the minimum, the whole rig shrank.
  6. A sealed vehicle applies vehicleMuffle — as low as 0.2 on some shipped booths. Get out and check.
  7. Windows audio. FiveM must not be muted in the volume mixer, and the game window generally has to have had focus at least once.
  8. Which engine is running? Turn on Config.Debug and run /djaudiodebug. The output starts with the backend name. If it says xsound and you expected the built-in engine, or the reverse, see Audio backend.

​
The xsound backend

Only relevant when Config.AudioBackend resolves to xsound.

​
YouTube is not loading

​
The panel will not open

  1. Are you in range? With Config.RequirePresence = true, the keybind and /dj only open the nearest booth you’re actually standing at. “There is no DJ booth nearby” means exactly that.
  2. Do you have permission? “You are not allowed to do that here” is the server refusing the session. Check the booth’s mode, and check your ACE — temporarily granting yourself nexdev_djsystem.admin is the fastest test.
  3. The keybind. Config.OpenKey defaults to F7 but is rebindable, and may already have been rebound. /dj always works.
  4. Give it a moment after a server start. The panel retries its initial fetch with a backoff of up to 30 seconds. Config.Debug = true prints the attempt count.
  5. Stuck with a mouse cursor? Three separate mechanisms release focus — the close button, an ESC watch, and a ten-second watchdog. If all three somehow failed, restart nexdev_djsystem always drops focus.
If the interface files are missing or damaged, the resource cannot start at all. Re-download the resource from your purchase rather than trying to repair it.

​
The target option does not show

​
Booths

​
Other things worth checking

  • “The database is unavailable.” oxmysql isn’t connected. Playback still works; playlists, saved booths and audit rows don’t. Check your mysql_connection_string and that oxmysql starts first.
  • The soundboard does nothing. The shipped URLs are placeholders. See Soundboard.
  • Buttons are greyed out or clicks do nothing. Usually a job or group change while the panel was open. The panel refreshes on a 30-second loop; reopening it resyncs immediately.
  • permission:refused, proximity:refused, rate_limit:refused or session:stale in the console. These are traces, not punishments — the request was dropped and the player was charged nothing. One line per player per ten seconds. A steady stream of permission:refused from one player usually means their job changed while their panel was open; a steady stream of proximity:refused means they’re standing right on a booth’s radius edge.
  • Someone was kicked for “security”. The console and the audit table record which flag and why. Only one thing raises a strike — a malformed payload that the shipped interface cannot produce. An ordinary player collecting strikes is a bug worth reporting, not a threshold to raise.
Read the flag reasons before touching Config.Security.strikes. Raising the thresholds hides the symptom of a real problem.

​
Before opening a support ticket

Please include:
  1. Your Config.Framework value, and what it actually detected on boot.
  2. Your FiveM artifact build number.
  3. Whether it’s a fresh install or after a config change.
  4. Server console output filtered for [nexdev_djsystem] from when the issue happens.
  5. F8 console output filtered for [nexdev_djsystem].
  6. Whether the booth came from config/locations.lua or the booth manager.
  7. For audio issues: a screenshot with Config.Debug = true showing the radius rings.
See Support & contact for how to reach us.