Secure client portal

Config & Visibility

BeamMP Server Not Showing in the List

Fix visibility: AuthKey, Private flag, heartbeats, ports, and filters—plus Direct Connect fallback.

Checklist

  1. Valid AuthKey in ServerConfig.toml (console shows no auth errors).
  2. Private = false for public listing.
  3. TCP + UDP on the configured port (managed: already allocated).
  4. Server process running in Pterodactyl.
  5. Client filters not excluding your server.
  6. Fallback: Direct Connect IP:port.

DIY readers: verify firewall with Linux ports and port forwarding explained.



Frequently Asked Questions

Still hidden after AuthKey?

Confirm Private=false, TCP+UDP on the port, and wait a minute for heartbeats.

Can players still join?

Yes — Direct Connect with IP:port usually works even when the list fails.

Filters?

Client filters (modded, empty, etc.) can hide healthy servers.


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.

Chapter22 BeamMP hosting

Deploy a managed BeamMP server.

Chapter22 BeamMP hosting is a single US plan with Pterodactyl—AuthKey, ports, and friends online fast.