Expanded operator checklist for Cfx list visibility (replaces the thin legacy page content).
Checklist
- Server online; FXServer healthy in Pterodactyl console.
- Valid license key in server.cfg.
sv_projectName/sv_projectDescset sanely.- 30120 TCP+UDP reachable (managed: panel allocation — see Ports Explained).
- Endpoint/listing not blocked by console errors.
- Client filters (locale, tags) not hiding you.
- Fallback:
connect IP:port(Direct Connect).
Managed vs DIY
Chapter22 FiveM hosting skips home-router NAT. DIY VPS readers still need firewall rules and must avoid CGNAT traps on residential IPs.
Related guides
- FiveM Ports Explained: 30120 TCP/UDP and txAdmin
- Ports Managed vs Self-Hosted
- Direct Connect
- VPS Port Forwarding Explained (Firewall vs Home Router)
- DDoS Protection Basics for Game Servers
Frequently Asked Questions
Direct connect works?
Then focus on listing/heartbeat/project info rather than raw ports.
Managed hosting?
Ports are allocated — check license key, sv_projectName, and console errors.
CGNAT?
Hurts DIY home hosts; Chapter22 game nodes are public allocations.
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.