Troubleshooting

🎤 Microphone Issues

Problem: Microphone not working in-game

Solution:

1. Open radio → ST button → Navigate with arrow keys → Select different microphone device
2. Check FiveM permissions - ensure you clicked "Allow" for microphone access

🔌 Connection Issues

Problem: "Failed to connect to radio server"

Console Errors Indicate Blocked Port:

[Radio-Server] ERROR Health check failed after 4 attempt(s)
[Radio-Server] WARN HTTP endpoint test failed - connect ECONNREFUSED

Port Testing

1. Start the radio resource on your server
2. Go to https://portchecker.co/check-v0
3. Enter your server IP and port (e.g., 192.0.2.100:7777)
4. Check the result:
   • ✅ "Open" = Port is configured correctly
   • ❌ "Closed" = Port is blocked (see solutions below)

Web Panel Hosting Solutions

Problem: Port shows as "Closed" even after adding it in the panel

Steps:

1. Verify new port added in panel's Network/Ports/Allocations section
2. Confirm NOT using FiveM (30120) or txAdmin (40120) ports
3. Set port in config.lua: serverPort = 50978 and connectionAddr = "http://192.0.2.100:50978/"
4. Restart entire server from panel
5. Test with portchecker.co
6. If still closed, open support ticket: "Need port [YOUR_PORT] opened for voice server. Port added in panel but shows closed on port checker."

Common Provider-Specific Issues

VPS/Dedicated Server Solutions

If you have direct server access, open the port manually:

Ubuntu/Debian:

sudo ufw allow 7777
sudo ufw reload
sudo ufw status  # Verify it's open

CentOS/RHEL:

sudo firewall-cmd --permanent --add-port=7777/tcp
sudo firewall-cmd --reload

Windows Server:

netsh advfirewall firewall add rule name="Radio Voice Server" dir=in action=allow protocol=TCP localport=7777

Checklist

• fx_version 'bodacious' in fxmanifest.lua
• Port not in use (not 30120 or 40120)
• serverPort and connectionAddr match and use same port
• Resource starts without errors
• Tested with portchecker.co while resource running

Error Messages

Success Indicators

When everything is configured correctly, you should see:

[Radio-Server] ℹ Started Radio Server - Running Checks...
[Radio-Server] ℹ HTTP endpoint test passed (attempt 1/4)
[Radio-Server] ℹ Socket.IO connection test passed (attempt 1/4)

 ╭────────────────────────────────────────────────────╮
 │                                                    │
 │  ✅  Tommy's Radio - System Ready                   │
 │                                                    │
 │  Version: v3.1                                     │
 │  Status:  Started - All Systems Operational        │
 │  Panel:   http://192.0.2.100:7777/                 │
 │  NAC ID:  141                                      │
 │  FX Ver:  bodacious                                │
 │  Config:  3 zones, 12 channels                     │
 │                                                    │
 ╰────────────────────────────────────────────────────╯

Key indicators of success:

• ✅ No "Health check failed" warnings
• ✅ No "ECONNREFUSED" errors
• ✅ Status shows "All Systems Operational"
• ✅ Port checker shows your port as "Open"
• ✅ Panel URL is accessible in browser

📞 Dispatch Panel Problems

Problem: NAC Code Doesn't Work in Desktop App

Cause: Desktop app defaults to demo server.

Solution:

1. Open app, login with 141
2. Click settings cog (⚙️) at top-right
3. Change Endpoint URL to: http://192.0.2.100:7777/ (your IP and port)
4. Save - app refreshes
5. Login with YOUR dispatchNacId

Problem: "Where Do I Get the NAC Code?"

You CREATE it in config.lua - it's YOUR dispatch panel password.

Config = { dispatchNacId = "DISPATCH2024" }  -- This is your login code

Login at http://yourip:port/ using whatever you set as dispatchNacId.

Problem: Can't Talk on Dispatch Panel

Browsers block microphone on HTTP.

Solution: Use desktop app (recommended) or setup HTTPS for production.

🚨 Emergency Features

📡 GPS & Tracking

GPS not showing?

• Check NAC permissions in channel config
• Enable GPS in radio settings (ST menu)
• Verify channel has GPS configured: gps = { color = 54, visibleToNacs = { "100" } }

🔊 Audio Problems

⚙️ Configuration Issues

🐛 Debug Logging

Set Config.logLevel in config.lua:

• 0: Errors only | 1: Warnings | 2: Minimal | 3: Normal | 4: Detailed | 5: Verbose

Warning: Debug mode (4-5) creates extensive console output. Use only for troubleshooting.

📋 Support

Before asking for help:

1. Check server console for errors
2. Test on demo server
3. Verify port is open with portchecker.co

Forum: FiveM Community Post

When reporting issues include:

• Console error messages
• Relevant config.lua sections
• Server framework (QBCore, ESX, etc.)