Secure client portal

Backups & Troubleshooting

Friends Can’t Join RUST (Works for You Checklist)

Local OK, public fail: UDP 28015, CGNAT DIY notes, wrong connect port vs query port.

Checklist

  1. Friends use public panel game IP:port (not 127.0.0.1).
  2. You didn’t accidentally share query/RCON ports for client.connect.
  3. Server shows startup complete.
  4. DIY home host: check CGNAT and UDP firewall.
  5. Test from a phone network with client.connect.

Soft CTA: RUST hosting.



Frequently Asked Questions

You can join, friends can’t?

Often wrong IP:port shared, or DIY CGNAT/firewall.

Managed hosting?

Use panel game allocation; no home router forward needed.

CGNAT?

Common on residential DIY — see General CGNAT backlog; managed nodes avoid your home CGNAT.


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 RUST hosting

Deploy a managed RUST server.

Chapter22 RUST hosting is Oxide-capable on Pterodactyl—Scrap, Raid, and Wipe tiers in Ogden, UT.