How to Set Your BeamMP AuthKey

A BeamMP AuthKey ties your dedicated server to BeamMP’s backend for listing and authentication.

Steps

1. Generate an AuthKey from BeamMP’s official key page (see current BeamMP docs / check.beammp.com).
2. Stop the server in Pterodactyl.
3. Edit ServerConfig.toml:

AuthKey = "YOUR_KEY_HERE"

1. Start the server and watch the console for AuthKey acceptance errors.
2. Set Private = false if you want the public list (see Public vs Private).

Security

• Never commit AuthKeys to public Git repos or screenshot them in tickets without redaction.
• If a key leaks, revoke/regenerate and update ServerConfig.toml.

Managed tip

On Chapter22 BeamMP hosting, edit the file in the panel File Manager — no SSH required.

---

Related guides

• Ports Explained
• ServerConfig.toml Explained
• Not Showing in the List

---

Frequently Asked Questions

Is AuthKey required?

Required for public list visibility. Private Direct Connect sessions still benefit from a valid key.

Where do I get one?

From BeamMP’s official AuthKey / key generation flow (check.beammp.com / BeamMP docs).

Can I paste the key in Discord?

No. Treat it like a password — rotate if leaked.

---

Need help?

If you are stuck after following this guide, open a ticket from the Chapter22 client area with the exact error, the port or DNS change you made, and whether the service listens locally (ss / Resource Monitor) but fails externally.

Build the server. Grow the community. Start your next chapter.