Secure client portal

Ports & Server List

RUST Server Not Showing in Community/Modded List

Fix missing browser entries: distinct queryport, UDP reachability, Modded tab, Oxide filters.

Checklist

  1. Console shows Server startup complete.
  2. QUERY_PORT is set and allocated (egg default 28017) — distinct from game/RCON.
  3. Try Modded tab if Oxide/Carbon is enabled.
  4. client.connect still works? Then visibility is query/tags, not game bind.
  5. DIY: confirm query UDP open externally.

Managed customers: ports are allocated on the node — copy from Pterodactyl.



Frequently Asked Questions

Connect works, list fails?

Game port OK — fix query UDP / tags / Modded tab.

Oxide hidden?

Check Modded filter; ensure queryport differs and is allocated.

Wrong port favorited?

Favorites must track the query endpoint, not only game port.


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.