Secure client portal

Ports & Browser

ArmA Reforger Server Not Showing in Browser

Fix missing listings: A2S 17777/UDP, `visible`, publicAddress/publicPort, and BattlEye filters.

Checklist

  1. game.visible true (Startup VISIBLE).
  2. publicAddress/publicPort match panel allocation (egg-managed).
  3. Direct Connect with IP:port succeeds.
  4. If you depend on A2S listing, add a2sPort + allocation (not default on egg 18).
  5. Align mods/version with clients.


Frequently Asked Questions

Direct works, browser fails?

Check visible=true, publicAddress/publicPort, and A2S if required.

Egg A2S?

Default egg config omits a2sPort — Direct Connect still works with game port.

Filters?

BattlEye / version / mod filters can hide servers.


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 ArmA Reforger hosting

Deploy a managed ArmA Reforger server.

Chapter22 ArmA Reforger hosting on Pterodactyl—Squad, Platoon, and Company tiers in Ogden, UT.