Your server runs, but BeamMP will not list it because it did not accept the key. Create a new key at keymaster.beammp.com, paste it on your server's Overview page, and restart. A key belongs to one server at a time.
What you see
- The Console repeats, every 30 seconds:
Backend REFUSED the auth key. Reason:and BeamMP's reason, for exampleYour key is invalid. - The BeamMP server list card on Overview says Key refused, with
BeamMP said:and the reason. - Step 1 of the Go live card says
BeamMP refused this key. - Above the Console, the card What BeamMP said about your server says
BeamMP refused the auth key.
The server keeps running, but BeamMP will not list it, so nobody finds it in the list.
Why it happens
- The key already runs another server, for example your old host.
- The key was deleted in keymaster.
- The key was copied wrong.
Fix it
- Sign in at keymaster.beammp.com, open Keys and create a new key for this server. Copy it.
- On Overview, paste it in the box on the BeamMP server list card and click Save key. Or paste it in step 1 of the Go live card, which shows a box for a new key while the old one is refused.
- Restart the server. The BeamMP server list card has Restart now for this.
- Within 1 to 3 minutes the card should say Listed.
See How to get a BeamMP auth key for your server.
The key looks wrong
If the Console says AuthKey specified is the wrong length and likely isn't valid., or the panel says The saved key does not have the shape of a BeamMP key (36 characters)., copy the key again from keymaster without spaces or extra text.
Good to know
- A private server is never listed, so it does not need BeamMP to accept the listing. It still needs a key to start: How to make your BeamMP server private.
- If the Console says
Backend failed to respond to a heartbeatinstead, BeamMP's own servers did not answer. That is not your key and it clears by itself: Your BeamMP server does not show in the server list.





