Arma Reforger Server Hosting

What is an Arma Reforger dedicated server and how does it differ from Arma 3?

The Arma Reforger dedicated server is the official server application Bohemia Interactive provides for Arma Reforger, built on its Enfusion engine. The main differences from Arma 3 are that all settings are collected in a single JSON file, mods are downloaded automatically by the server from Bohemia’s own Workshop, and players on platforms other than PC (Xbox and PlayStation) can join the same server.

Common scenarios on Reforger servers:

• Conflict: A large-scale PvP mode where two or more factions capture bases and build supply lines. Most busy community servers run this mode.
• Game Master: A mode where a game master places units, tasks and events in real time; popular with milsim units.
• Combat Ops: A mission-focused co-op scenario against AI for small groups.
• Modded scenarios: Maps, factions and game modes from the Workshop.

For admins with Arma 3 experience the concepts are familiar (AI load, server FPS, mod compatibility), but the file structure and mod management are completely different; rather than carrying over Arma 3 habits one to one, you need to learn Reforger’s own structure. If you are considering an Arma 3 server instead, see our Arma 3 server hosting page.

How many resources does an Arma Reforger server need?

A small Game Master or Combat Ops server can run with 4–6 GB of memory and 2–4 cores, while Conflict servers above 64 players need 12–16 GB and 6–8 dedicated cores. The values in the table are estimates; the scenario’s AI load and the mod list change the requirement noticeably.

The main factors that determine resource needs:

• Player count: A Reforger server can be configured for up to 128 players; as the count rises, network traffic and synchronisation load rise too.
• AI: AI patrols in Conflict and units placed by the Game Master load the CPU.
• View and network distance: The serverMaxViewDistance and networkViewDistance values decide how far away objects are streamed to players; high values increase load.
• Mods: Large map and vehicle mods increase memory and disk use.

Although the Enfusion engine is better suited to multi-threading than Arma 3, high single-core performance still matters for server FPS. A VDS with dedicated cores absorbs sudden load spikes in busy Conflict matches without interference from neighbouring servers. Plan resources for a full server at evening peak, not an empty one.

To see the server’s real load, the -logStats launch parameter writes server FPS and player count to the log at set intervals; watching these records for a few days shows clearly at what player count the server starts to struggle. If server FPS drops noticeably at busy hours, first try reducing view distances and AI density; if those settings are not enough, moving to a plan with more cores is the lasting fix.

Game package or VDS for Arma Reforger?

At LIONFIN you run an Arma Reforger server on a VDS; this page lists VDS plans for the game. You can install the server yourself or open a support ticket from the customer panel after ordering the VDS and ask for the setup.

Because Reforger officially supports Linux, you can set up an efficient installation with no licence cost. On a VDS you can also:

• Run separate server instances on different ports for different scenarios (for example one Conflict and one Game Master),
• Manage config.json files under version control and easily roll back changes,
• Define the server as a systemd service with automatic restart after crashes,
• Run the server inside a container with Docker; community Docker images are widely used.

VDS plans come with the public IPv4 address a Reforger server needs, which simplifies port forwarding and the publicAddress setting. A general comparison of a game package and a VDS is on the game server package vs VDS page; current plan values are shown in the plan table on this page.

How do you install an Arma Reforger server?

The Arma Reforger server is downloaded with SteamCMD from ID 1874900 using an anonymous login and started by pointing it at a config.json file. The process is the same on Linux and Windows; only the binary name changes.

1. Create a separate user for the server and download the files with SteamCMD:

   steamcmd +force_install_dir /home/reforger/server +login anonymous +app_update 1874900 validate +quit

2. Prepare a config.json file (see the example in the next section).
3. Start the server with the configuration and a profile folder:

   ./ArmaReforgerServer -config /home/reforger/config.json -profile /home/reforger/profile -maxFPS 60

   On Windows the same parameters are used with ArmaReforgerServer.exe.
4. Confirm in the log that the server downloaded its mods and loaded the scenario.
5. Define the process as a systemd service.

The -profile folder holds logs, downloaded Workshop mods and the server’s persistent data, so it is at the heart of your backups. The -maxFPS parameter caps the server frame rate so the CPU does not run at full capacity needlessly.

What do you configure in config.json?

All Arma Reforger server settings live in a single config.json file: network addresses and ports, server name and passwords, the scenario, player limit, game properties and mod list. Bohemia’s official wiki documents every field in the file.

{
  "bindAddress": "",
  "bindPort": 2001,
  "publicAddress": "",
  "publicPort": 2001,
  "a2s": { "address": "0.0.0.0", "port": 17777 },
  "game": {
    "name": "LIONFIN Conflict EU",
    "password": "",
    "passwordAdmin": "a-long-and-unique-password",
    "scenarioId": "SCENARIO_ID",
    "maxPlayers": 64,
    "visible": true,
    "crossPlatform": true,
    "gameProperties": {
      "serverMaxViewDistance": 2500,
      "networkViewDistance": 1500,
      "disableThirdPerson": false,
      "battlEye": true
    },
    "mods": []
  }
}

The file is strict JSON: keys are case-sensitive and even one extra comma stops the server starting. The scenarioId value is the ID of the scenario to play; the IDs of the official Conflict and Game Master scenarios can be found on the wiki and with the server’s scenario listing parameter. Copy the file before every change and check the syntax with a JSON validator.

How do you add Workshop mods to the server?

In Arma Reforger, mods are added by writing their IDs into the mods array in config.json; the server downloads them itself from Bohemia’s Arma Reforger Workshop at start-up. Unlike Arma 3, there is no need to copy mod folders or manage key files.

"mods": [
  { "modId": "MOD_ID_1", "name": "Mod name" },
  { "modId": "MOD_ID_2", "name": "Another mod", "version": "1.2.3" }
]

Things to watch:

• Version pinning: If you leave the version field empty, the server downloads the latest version. For stability you can pin the version and update on your own schedule.
• Dependencies: Some mods need other mods; add the dependencies listed on the Workshop page.
• Player side: Players download the required mods in-game when connecting.
• Console compatibility: On a server that accepts console players, the mods you use must also be available on consoles, otherwise console players cannot connect.

If you use a modded scenario, the scenarioId value must point to that mod’s scenario. Backing up the profile folder before changing the mod list lets you roll back quickly if anything is incompatible.

As the number of mods grows, so do the server’s start-up time and the download time players face on first connection. Choosing mods that genuinely add value for your community, trying each new mod on a test server first and removing unused mods from the list protects both server performance and player experience. A test server opened as a second instance on the same VDS is ideal for these trials.

Can console players join the server (crossplay)?

Yes, Arma Reforger servers can accept Xbox and PlayStation players as well as PC players; this is controlled by the crossPlatform setting in config.json (or by the supportedPlatforms field, which lists supported platforms explicitly).

Things to consider when planning a crossplay server:

• Player pool: Servers open to console players reach a wider audience, which matters especially for filling the server.
• Mod restrictions: Console players can only use mods published on their platform. On a modded server this limits console participation.
• Performance: Consoles can respond differently from PCs to the object density the server sends; keeping network view distance reasonable gives a smoother experience on every platform.
• Community management: Set up rules and communication channels that players from every platform can access.

For a heavily modded milsim server aimed only at a PC community, disabling crossplay may make more sense. The decision depends on your community’s make-up and your mod list.

Because console players are part of Reforger’s player base, a Conflict server with crossplay enabled and either no mods or console-compatible mods is one way to reach a wider audience. A server hosted in Türkiye suits both PC and console players in Türkiye and the surrounding region.

Which ports need to be open?

By default an Arma Reforger server needs game port 2001/UDP and A2S query port 17777/UDP open; if you enable RCON, its port (default 19999) must also be opened.

sudo ufw allow 2001/udp
sudo ufw allow 17777/udp

According to the official wiki, if the server has a public IP address the publicPort value must match bindPort; if port forwarding is used, enter the externally exposed port. Since your VDS has a public IPv4 address, keeping both values the same is enough. Rather than opening the RCON port to everyone, allow only admin IPs.

How do you configure admins and RCON?

Arma Reforger is administered through the passwordAdmin password in config.json, the admins field listing admin IDs, and an optional RCON connection. A player who logs in with the admin password in-game gets access to commands such as kicking, banning and scenario management.

RCON lets you send commands to the server without joining the game and is defined in its own block in config.json:

"rcon": {
  "address": "0.0.0.0",
  "port": 19999,
  "password": "strong-password-without-spaces",
  "permission": "admin"
}

According to community sources, the RCON password cannot contain spaces and must meet a minimum length. Keep the admin password and RCON password different so that a leak of one does not compromise the other.

In Game Master scenarios the game master role matters too: whoever holds it can place units and objects in the world. Give this right only to people you trust and tell your community clearly who is game master in each session.

As the admin team grows, adding admins to the admins list by ID is more controlled than sharing one password with everyone: to revoke access for someone who leaves, you simply remove them from the list, with no need to change everyone’s password. Logging ban and kick decisions in your community channel provides transparency.

How do you back up server data?

The two core items to back up on an Arma Reforger server are the config.json file and the profile folder set with the -profile parameter. The profile folder holds logs, downloaded mods and persistent scenario data.

• Configuration: Copy config.json with a date before every change; keep it under version control if possible.
• Profile folder: Archive the parts containing persistent scenario data and server settings daily. Downloaded Workshop mods can be fetched again, so they can be left out of the backup, which shrinks the archive considerably.
• Off-site copy: Move the archives to another server or storage.

When migrating from another provider, copy the same config.json and profile folder to the new server and start it with the same parameters; mods are downloaded again on first launch.

How is an Arma Reforger server protected against DDoS and cheating?

Arma Reforger server security relies on BattlEye anti-cheat, opening only the required ports, strong passwords and network-level DDoS filtering applied together. On LIONFIN infrastructure the RouteFence firewall filters at the network level and traffic is monitored 24/7 by our NOC and SOC teams; see our data center for details.

• BattlEye: Keep the battlEye setting in gameProperties enabled on public servers.
• Passwords: Choose admin and RCON passwords that are different, long and hard to guess.
• Ports: Open only the game and query ports to everyone; protect RCON with IP restrictions.
• SSH: Connect to the server with key-based login.

On busy Conflict servers, admins regularly reviewing in-game logs makes it easier to respond quickly to cheating reports.

What are the most common Arma Reforger server errors?

Most Arma Reforger server problems come from JSON syntax errors, a wrong scenario ID or mod incompatibility.

The first place to look when the server has problems is the logs in the profile folder. If you cannot solve it, open a support ticket from the customer panel.