Troubleshooting
Fixes for the most common oxide-radio problems — configuration, the radio item, voice, channel access, encryption, and the overlay.
Fixes for the most common problems, grouped by area. For most issues the first step is the same: watch the server console — oxide-radio prints its warnings and notable events there (lines tagged [oxide-radio]).
Configuration Issues
Opening the Radio
Voice and Audio
Channels and Access
Encryption
The Overlay
Admin and Commands
General Debugging
Watch the server console
oxide-radio prints its warnings and notable events to the server console with lines tagged [oxide-radio] — boot status, missing pma-voice, channel registration conflicts, rejected settings, and security events all show up there. That console output is your main diagnostic tool.
There is also a Debug logging toggle (/radio settings → Advanced, or Config.Debug before the first start). It adds a few extra settings-loading lines on top — turn it on while diagnosing a configuration problem, and leave it off on a live server.
For a permanent audit trail (channel joins, encryption changes, settings edits, security rejections), install the optional oxide-logger resource — oxide-radio logs structured events through it automatically when it's present.
Getting Help
If none of the above resolves your issue:
- Turn on debug mode and reproduce the problem.
- Check your server console (and press F8 in game) for error messages.
- Note which framework you run (QBCore / QBX / ESX), whether
pma-voiceis installed, and the exact steps that trigger the problem. - Contact Oxide Studios support with your debug output and those details.
Next Steps
- Installation — setup steps
- Configuration — every setting explained
- Features — how the radio works in game