Arma Reforger server_config.json Explained: Every Setting

Starting the server with your config file

The dedicated server executable is ArmaReforgerServer.exe on Windows and ArmaReforgerServer on Linux. Install or update it with SteamCMD using anonymous login: app_update 1874900 validate for the stable branch, or 1890870 for experimental. Match the branch to the one your players run.

# Windows
ArmaReforgerServer.exe -config ".\Configs\my_server.json" -maxFPS 60

# Linux
./ArmaReforgerServer -config /home/USER/.config/ArmaReforgerServer/config.json -profile /home/USER/.config/ArmaReforgerServer -maxFPS 60

On a hosted server the host normally launches the server for you, so you edit the same config file (over SFTP or your host's editor) instead of building the command yourself. It must be strictly valid JSON, so no comments and no trailing commas. A server that refuses to start after an edit often has a stray comma or quote.

-maxFPS is not in the config file but belongs in your launch line. Bohemia says it is heavily recommended, with a value between 60 and 120, because otherwise the server can try to use all available resources.

Ports and addresses: bindPort, publicAddress and a2s

Open 2001 UDP for players and 17777 UDP if you want the server to answer Steam Query. If you leave RCON out, there is nothing else to expose. If you enable it, use a strong password with no spaces, keep permission at monitor (read-only commands) unless you truly need admin, and do not expose the RCON port to the public internet.

The game block: name, passwords, admins, players

About crossplay: the wiki page lists only the PC and Xbox values. Hosting guides, including our own knowledgebase article on crossplay, also use PLATFORM_PSN for PlayStation 5 players, so check the current wiki and patch notes for your version before you rely on it. Console players and mods are a separate problem; see the mods guide.

A note on the name key inside mods entries: it has no function and is only a comment to remind you which mod an ID is.

gameProperties: view distance, BattlEye, voice and perspective

Servers running a milsim ruleset usually set disableThirdPerson and the two VONDisable options to true, as in Bohemia's own example. Leave battlEye on for a public server.

The operating block

Version 1.0.0 also added a navmesh streaming option under operating; read the wiki for its current key name and behavior, because it changed in 1.2.0.

A complete example server_config.json

Replace the example IP with your server's public address. The scenario is Conflict on Everon. Remove the mods entries if you are not using mods.

{
  "bindAddress": "0.0.0.0",
  "bindPort": 2001,
  "publicAddress": "203.0.113.10",
  "publicPort": 2001,
  "a2s": {
    "address": "203.0.113.10",
    "port": 17777
  },
  "game": {
    "name": "My Community | Conflict Everon",
    "password": "",
    "passwordAdmin": "change_this_admin_password",
    "admins": [],
    "scenarioId": "{ECC61978EDCC2B5A}Missions/23_Campaign.conf",
    "maxPlayers": 32,
    "visible": true,
    "supportedPlatforms": ["PLATFORM_PC"],
    "gameProperties": {
      "serverMaxViewDistance": 2500,
      "serverMinGrassDistance": 50,
      "networkViewDistance": 1000,
      "disableThirdPerson": false,
      "fastValidation": true,
      "battlEye": true
    },
    "mods": []
  },
  "operating": {
    "lobbyPlayerSynchronise": true
  }
}

The view-distance values come from the example on the Bohemia wiki. They are a sensible starting point, not a rule. a2s.address is the local address the query socket binds to, so on a machine behind NAT use its local IP there rather than the public one.

Old key names that break older tutorials

The wiki marks these renames as happening before 0.9.8.73. If you copy a config from an old video or forum post and settings seem ignored, look here first.

Hosting with ChicagoServers? The ArmA Reforger server hosting page lists what is included, such as free server backups and SFTP file access.

Server not showing up or players cannot join

• Not in the browser: check visible, that the server finished starting without errors, and that publicAddress is correct if the machine sits behind NAT or has several network interfaces.
• Can see it, cannot connect: confirm UDP 2001 (or your bindPort) is reachable from outside. If publicPort differs from bindPort, the forwarded port must match publicPort.
• BattlEye problems: BattlEye is on by default (battlEye true), so players need it working too. Check the server and client logs before deciding to turn it off.
• Admin login fails: the password must match game.passwordAdmin. Type #login PASSWORD in chat with no quotes.
• Config ignored: confirm the path passed to -config. The parameter is ignored when you launch with -server, which is the local-world mode.

Frequently asked questions