Common Issues

Server Saying ‘Done’

This issue is generally caused by incompatible or corrupted mods. This can be resolved through checking every mod and ensuring they are not corrupted, check every mod is structured properly, and have BeamNG folders in the root.

Sometimes mod files get corrupted while downloading and reuploading them to your service. Try download the mod again and re-upload it to your service.

Backend failed to respond to a heartbeat

This issue is normally caused by an invalid authkey, broken connection or BeamMP backend issue and will constantly send the message Backend failed to respond to a heartbeat. Your server may temporarily disappear form the serverlist. This is not an error, and will likely resolve itself soon. Direct connect will still work. into the server console.

This means that the BeamMP server failed to heartbeat to the BeamMP backend/API. The heartbeat process is what the backend relies on to show your server on the serverlist. If this warning is happening repeatedly, it could be caused by a few things, which should be checked/fixed in the following order:

• Invalid Authkey → Check AuthKey is valid (in the startup section) as shown on BeamMP Keymaster
• Broken Connection → Restart server
• BeamMP Backend Issues → Contact Vyper Hosting support or BeamMP support.

If the warning shows up once or intermittently, then you do not need to worry. The server heartbeats every 30 seconds, so it should be back on the serverlist as soon as possible.

Error Codes

Here are some common error codes found on a BeamMP server.

Code	Description	Possible solution
10022	There is an issue with binding to the port	Check if the port for the server is already in use by another service, if it is use another one.
10048	Address already in use	Another BeamMP server or program is running on that port, use another one.
10051	Network unreachable	Bad port forwarding or similar issues, verify that it is all set up correctly.
10052	Network reset	Happens if the network drops connection while a connection is being established. Retry the connection.
10053	Connection aborted	Caused by timeout or network error, retry the connection.
10054	Connection reset by peer	A client has disconnected from your server.
10064	Host down	Unlikely error, but it means that the host is down because either it’s shutdown or ports were closed.

Note

For any other code not in this list, you can refer to https://learn.microsoft.com/en-us/windows/win32/winsock/windows-sockets-error-codes-2 if you know a bit how networks / sockets work.