ArmA Reforger uses bindPort/publicPort for gameplay (BI wiki default 2001/UDP). Browser listing often needs A2S 17777/UDP. Optional RCON 19999 is admin-only.
Port table
| Service | Port | Protocol | Public? |
|---|---|---|---|
Game (bindPort / publicPort) | Primary allocation (wiki 2001) | UDP | Yes — players |
| A2S / browser query | Wiki 17777/UDP | UDP | Yes if using browser query — not in default egg config |
| RCON | Wiki 19999 (optional) | TCP | No — private |
Managed hosting (Chapter22)
- Open Pterodactyl → Reforger server.
- Copy primary IP:port — egg writes it into
config.jsonas bindPort/publicPort/publicAddress. - Join with that IP:port; do not assume 2001.
- If you add A2S/RCON manually, request matching extra allocations and keep RCON private.
VERIFY — panel remaps game port; A2S/RCON are not auto-wired by egg 18.
DIY / self-hosted readers
DIY: allow game UDP (and A2S if used). See Linux ports.
Egg verification (Chapter22)
Egg 18 (Arma Reforger): config.json bindPort/publicPort = primary SERVER_PORT (remap from wiki 2001). Default config has no a2sPort/RCON — A2S 17777 and RCON 19999 are optional manual additions + extra allocations.
config.json mapping
Egg find/replace sets bindPort/publicPort to {{server.build.default.port}} and publicAddress to the server IP.
Related guides
- How to Join
- Not Showing
- How to Open Ports on a Linux VPS (UFW, firewalld, iptables)
- VPS Port Forwarding Explained (Firewall vs Home Router)
- DDoS Protection Basics for Game Servers
Frequently Asked Questions
What does the egg bind?
Egg 18 maps bindPort and publicPort in config.json to the primary SERVER_PORT allocation (wiki default 2001 remapped).
Is A2S 17777 automatic?
Default install config.json has no a2sPort field. A2S 17777 is a BI wiki default — add it (plus an allocation) only if you need that query path.
RCON 19999?
Optional and not egg-managed — enable only with a strong password and keep it private.
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.