BeamMP Server Not Showing in Server List

Your server is running, but it's nowhere to be found in the server list. This is one of the most common issues, and it's almost always one of these things:

1. Missing or Invalid Auth Key

This is the #1 cause. Your server needs a valid authentication key to appear on the public list.

Fix:

1. Go to BeamMP Keymaster and log in with Discord
2. Create a new key (or copy your existing one)
3. Open the Config Editor tab in your panel
4. Paste the key into the AuthKey field
5. Save and restart

Full walkthrough: Auth key setup guide

Common key mistakes:

• Copying extra spaces before or after the key
• Using a key that's been deleted from the Keymaster
• Using someone else's key (keys are tied to your Discord account)

2. Server Set to Private

Check your ServerConfig.toml:

Private = false

If this is set to true, your server won't appear in the list. That's intentional — it's for private servers. Change it to false if you want to be listed.

3. Server Isn't Actually Running

Sounds obvious, but double-check. Open your panel and look at the server status. If it says stopped or crashed, start it up. Check the Console for error messages if it keeps crashing.

4. Server Name Issues

Some server names can cause problems:

• Extremely long names
• Certain special characters
• Empty name field

Try a simple name like "Test Server" and see if it shows up. If it does, your original name had something the list didn't like.

5. Give It a Minute

The server list isn't instant. After starting your server (or changing your auth key), it can take 1-3 minutes to appear. Don't restart repeatedly — that resets the timer each time.

6. BeamMP Backend Issues

Rarely, the BeamMP backend servers have issues. Check the BeamMP Discord to see if others are reporting the same problem.

Still Not Working?

If none of the above fixed it:

1. Check your console for any error messages mentioning "auth" or "backend"
2. Try generating a brand new auth key
3. Make sure your server is on the latest BeamMP version
4. Contact our support and we'll take a look