BeamMP problems fall into three groups. The console tells you which one you have.
1. Authentication key errors
If the console reports an invalid or missing key, the server is running but will never accept players.
- Stop the server.
- Open
ServerConfig.tomlin the Files tab. - Check
AuthKeyhas your key inside quotation marks with no stray spaces. - If you are not sure the key is still valid, generate a new one on the BeamMP keymaster site with your own account and paste that in.
- Save and start the server.
2. Version mismatch
- BeamNG.drive updates on Steam, and BeamMP releases a matching launcher and server version afterwards.
- If players are refused right after a game update, restart the server so it updates too.
- Players should also make sure the launcher itself is up to date, not just the game.
3. Mods do not reach players
- Client mods must be zip files placed directly in
Resources/Client. A folder or a subfolder is skipped. - Read the console during boot. Every loaded mod is listed with its size, so anything missing from that list was not loaded.
- A player who cancels the download at join gets an incomplete mod set and is dropped. Tell them to let it finish.
4. The server is not in the list
Privateset to true keeps the server out of the public list on purpose. Use direct connect withIP:Port.- A server that has not authenticated is never listed, so fix any key error first.
5. The map will not load
- Check the
Mapvalue inServerConfig.tomlagainst the level folder inside the map mod. - Set it back to a stock map such as
/levels/gridmap_v2/info.jsonto prove the rest of the server is fine.
If the console shows an error you cannot place, open a ticket from Support in the Client Area with the last 50 lines of output.





