Can’t Connect / Stuck Connecting on BeamMP

Operator checklist

1. Server running in Pterodactyl; console clean.
2. Direct Connect uses the panel IP:port.
3. AuthKey valid.
4. TCP+UDP on the port (managed = allocated).
5. Disable suspicious recent client resources; retry.
6. Update BeamMP client; retry from a second network (phone hotspot) to rule out local filters.

Still stuck? Open a ticket from the client area with console logs (redact AuthKey).

Related guides

• Ports
• AuthKey
• Resources
• DDoS Protection Basics for Game Servers

Frequently Asked Questions

Is CGNAT the problem on Chapter22?

No for the server side — managed nodes have public allocations. CGNAT can still affect DIY home hosts.

Stuck on downloading resources?

Remove or fix client resource zips; try a clean BeamMP client cache.

Auth errors in console?

Regenerate AuthKey and update ServerConfig.toml.

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.