Skip to main content
Start with a short radio check with another user on the same channel. Note whether you cannot hear, cannot transmit, or both. Avoid repeatedly keying an operational channel while investigating.

I cannot hear or transmit in game

  1. Check that at least one available radio unit is powered on. Opening the radio face does not turn it on.
  2. Select a permitted zone and channel. Fresh power-on starts disconnected; a blank channel or NO TG is not an active channel.
  3. Wait for registration and affiliation to finish. Check for OUT OF RANGE, BUSY, or INHIBITED.
  4. Check radio volume and the intended microphone in /radiosettings → Audio. Confirm your OS input and output devices work.
  5. Close chat, settings, and pause menus, then hold your mapped PTT. Wait for the permit tone before speaking.
  6. Ask staff to check your character’s radio access, duty requirements, codeplug, or restrictions if the channel is missing or denied.
If proximity chat works but radio does not, that does not prove the radio microphone or connection is ready. They can use different audio paths.

It happens in a vehicle

Handheld and mobile radios have separate power. A powered, available handheld should still work with the mobile off, even if the displayed mobile face looks off. Use /radiodisplay or the display-switch binding to inspect the handheld. In /radiosettings → Radio, check the separate Handheld and Mobile power controls. Switching the face does not itself power a unit on or off. If the issue persists, report whether the handheld was carried/powered, whether the vehicle mobile was powered, the selected channel, and whether entering or leaving the vehicle changed the result.

A key triggers old radio controls or the retired /radio message

Open FiveM Settings → Key Bindings → FiveM and look for LSR Radio and any old radio resource bindings. Remove or remap the conflicting old entry, then assign the intended LSR control. The supported open command is /lsrradio, not the retired /radio. Removing an old radio resource does not always remove your saved keybind. Do not delete your entire FiveM key configuration or unbind every control just to fix one conflicting key. Use /radio_debug keys if staff asks for radio keybinding diagnostics.

Channel or zone selection seems stuck

Release PTT before retuning. Try both the on-screen Zone / Chan menus and your mapped channel/zone keys. Check that the channel is permitted and that you have not left a text field or another menu focused. If keys work but the on-screen selector does not, report the radio model, the menu involved, and the exact selection that fails. A screenshot or short clip helps staff distinguish a display issue from denied tuning.

Discord sign-in fails

  • Use the console address supplied by staff and the Discord account they authorized. There is no self-registration.
  • Allow the sign-in window to open. Complete authorization, then return to the original console or desktop app.
  • In desktop, sign-in opens in your normal browser; keep the app running until it finishes.
  • If the window closes, the request expires, or an error appears, start a fresh sign-in attempt and record the exact error if it repeats.
  • If you are unauthorized or staff just changed your account, ask them to verify your Discord ID and assigned access.
A secure-configuration or service error needs staff attention. Do not paste OAuth secrets, tokens, cookies, or passwords into support chat, and do not disable security protections as a workaround.

Dispatch receives audio but cannot transmit

Check microphone permission for the console and OS. Ensure the intended channel is in the TX group, or set a primary/selected fallback when the group is empty. Read the status bar for PTT failed or a denied/busy result. For Channel PTT, confirm the assigned channel still exists and that the key is not already used by another action. While the shortcuts dialog or another modal is open, PTT is intentionally blocked.

PTT fails when another application is focused

A browser console supports keys only while focused. Use the desktop app, leave it running, and install a current version. Background Channel PTT requires desktop 1.3.9 or newer, along with the current console page. On a compatible macOS desktop build, verify the app’s Accessibility permission. Function keys can also be intercepted by OS/media-key settings or require Fn. If a native mapping is unavailable, choose another supported key and check the shortcut status for synchronization errors.

The desktop console address is wrong or offline

On a load error, choose Change URL, Retry, or Quit. If the console opens, use Help → Desktop App settings… → Reset console URL…. The native application menu also offers Help → Reset radio console URL…. Check connectivity and ask staff to confirm the exact HTTPS console address. If several users lose the website at once, staff should check the service; repeatedly reinstalling the app is unlikely to fix a server outage. Desktop updates can still be checked while the website is offline.

Recordings or Stream Deck are not working

  • Recordings: check enabled modes, available storage, and the recording status. Automatic clips need accepted voice traffic; enabling sessions still requires selecting Start. See Local recordings.
  • Stream Deck: keep its application running, fully restart it after plugin upgrades, generate a fresh code, and read errors in the in-game tab. See Stream Deck.

What to send staff

Provide the time and timezone, whether you were in game/web/desktop, your app/plugin version where applicable, exact error text, zone/channel, and the shortest steps that reproduce the issue. For vehicle problems, include both unit power states. If staff requests it, run /radio_debug or /radio_debug keys and send the relevant output privately. For a FiveM connection error such as CURL error 56, include the complete error and the stage at which it occurred; the error number alone does not identify the cause. Redact private messages, personal details, and sensitive information from screenshots or logs. Never share pairing codes, credential files, Discord tokens, session tokens, passwords, or private recordings in a public bug report.