Secure client portal

Ports & Auth

BeamMP Ports Explained (30814 TCP + UDP)

BeamMP needs TCP and UDP on 30814 (or your custom Port)—managed hosting vs DIY firewall rules.

BeamMP’s default listen port is 30814 and needs TCP and UDP.

Port table

ServicePortProtocolPublic?
BeamMP game30814 (or Port in ServerConfig.toml)TCP + UDPYes — players

Managed hosting (Chapter22)

  1. Open the BeamMP server in Pterodactyl.
  2. Copy the primary allocation IP:port.
  3. Ensure ServerConfig.toml Port matches that allocation when you customize it.
  4. Share IP:port for Direct Connect.

DIY / self-hosted readers

On a DIY VPS, allow 30814/tcp and 30814/udp (or your custom port) in the OS firewall and provider security group. See Linux ports.

ServerConfig.toml

Port = 30814

Restart after changes. Verify with a Direct Connect from a second machine.



Frequently Asked Questions

TCP and UDP both?

Yes. BeamMP expects both protocols on the configured Port (default 30814).

Can I change the port?

Yes via ServerConfig.toml Port — then use the matching Pterodactyl allocation.

Managed customers forward at home?

No. Use the panel IP:port; Chapter22 already publishes the allocation.


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.