BeamMP Server Troubleshooting
Fix common BeamMP server problems — auth key errors, connection issues, mod problems, and performance.
Auth Key Errors
| Console Message | Cause | Fix |
|---|---|---|
No AuthKey Specified | The AuthKey field is empty | Paste your key in Startup tab or ServerConfig.toml. See Auth Key guide. |
Backend system refused server! Check your AuthKey | Key is invalid, revoked, or running on another server | Check Keymaster — is the key still there? Generate a new one if needed. |
[WARN] Backend failed to respond to a heartbeat | BeamMP backend temporarily unreachable | Wait 5–10 minutes. Check BeamMP Discord for status. |
Server Not in Browser
Check in this order:
Verify Private is false
In Startup or ServerConfig.toml, ensure Private = false.
Check auth key
The key must be valid and not in use on another server. See Auth Key.
Check the Console
In the Console tab of the XGamingServer Panel, look for error messages. A successful start shows the server registering with the backend.
Wait 1–2 minutes
New/restarted servers take a moment to register with BeamMP's master server.
"Socket Error" / Stuck on Connecting
Usually caused by corrupted or incompatible mod files, especially after a BeamNG.drive update.
Server-Side Fix
Isolate the problem
In Files, rename Resources/Client/ to Resources/Client_backup/. Create an empty Resources/Client/ folder.
Test the connection
Restart the server and try connecting. If it works, a mod file is corrupted.
Find the bad mod
Move mods back from Client_backup/ one at a time, testing after each. The one that breaks it is corrupted — delete and re-download it.
Client-Side Fix
If the problem is on a specific player's end:
- Deactivate all mods in BeamNG's Mod Manager
- Re-enable only MultiplayerBeamMP
- Try connecting again
Can't Join Own Server via Browser
Most home routers don't support NAT loopback (connecting to your own public IP from inside the network).
Fix: Use Direct Connect with 127.0.0.1:30814 instead of the server browser.
Port Forwarding Not Working
- Verify both TCP and UDP are forwarded on port 30814
- Check for CGNAT — if your router's WAN IP differs from your public IP (check at whatsmyip.org), port forwarding won't work. This is why hosted servers like XGamingServer avoid this issue entirely.
- VPNs (Hamachi, RadminVPN) are not officially supported and cause UDP issues
Cars Not Moving
Check that the player's system date and time are correct. Incorrect time causes sync failures.
Server Overloaded / Rubber-banding
- Lower
MaxCars— see Vehicle Limits - Lower
MaxPlayers - Remove large/complex vehicle mods from
Resources/Client/ - Check Dashboard in the panel for CPU and RAM usage
Related Guides
How is this guide?
