Arma Reforger server problems

Common Arma Reforger server problems. Settings are on your Startup page. See Arma Reforger settings.

Server does not show in the server browser

Why it happens: The server may be hidden, still starting, or the wrong scenario is set.

How to fix it:

1. On Startup, check Visible in Server Browser (VISIBLE) is true.
2. Wait a few minutes after the status says Online.
3. Check Server Region (REGION) and Server Name (SERVER_NAME) and search for the name in the game.
4. Try direct connect with the address and port from Network. See Network and ports.
5. If direct connect works but the browser does not, open a ticket.

Cannot connect by direct IP

Why it happens: Wrong address or port, or the server is not fully started.

How to fix it:

1. Check the Console shows the server is running and the status is Online.
2. Copy the primary address and port from Network.
3. Check the password: Server Password (SERVER_PASS) must be typed by players if set.
4. See Can’t connect to any game server.

Wrong or invalid Scenario ID

Why it happens: Scenario ID (SCENARIO_ID) is the path of a scenario .conf file (it looks like {ECC61978EDCC2B5A}Missions/23_Campaign.conf). If it is not valid, the server cannot load a mission.

How to fix it:

1. The Scenario ID setting says valid IDs can be viewed in the Console when the server starts. Start the server and read the Console.
2. Copy one exactly, including the curly braces and the .conf path after them, into Scenario ID.
3. Save and restart.

Mods are not loading

Why it happens: Arma Reforger mods are listed in the server’s config.json, not on the Startup page. There is no editable variable for mods here.

How to fix it:

1. Open Files and edit config.json. Look for the mods list inside the game section.
2. Each mod entry needs its mod ID (modId, a long hex ID shown on the mod’s Workshop page). name is only a label, and version is optional (without it the latest version is used).
3. Save, then restart. Mods are downloaded when the server starts.
4. If a mod updates, you may need to change its version to the new one.
5. Leave the address and port entries alone: the panel writes those itself on start.
6. If mods still fail, open a ticket with the Console error.

Players are kicked for a mod mismatch or missing mod

Why it happens: Players get the server’s mods when they join, and a mod that failed to download or has a different version can stop the join.

How to fix it:

1. Restart the server so mods check for updates (keep Automatic Updates AUTO_UPDATE at 1).
2. Ask players to restart the game and try again.
3. Remove recently added mods one at a time to find the bad one.

Kicked by BattlEye

Why it happens: Enable BattlEye (BATTLEYE) requires all clients to run it.

How to fix it:

1. Ask the player to restart the game and check BattlEye is not blocked by antivirus.
2. To test whether BattlEye is the cause, set BATTLEYE to false, save and restart. Only do this if you accept running without anti-cheat.

Client and server version mismatch after an update

Why it happens: The game updated and the server did not, or the opposite.

How to fix it:

1. Keep Automatic Updates at 1 and restart the server.
2. Set [Repair] Validate Server Files (VALIDATE) to true for one start if files look damaged, then clear it.
3. Ask players to update their game.

Server crashes or runs out of memory

Why it happens: Large scenarios, many mods and many players use a lot of memory.

How to fix it:

1. Watch memory on the Console.
2. Lower Max Players (MAX_PLAYERS) and remove unneeded mods.
3. See Out of memory and Upgrade.

Low server FPS or lag

Why it happens: The server is under load from players, AI or mods.

How to fix it:

1. Set Log FPS Interval (LOG_INTERVAL) to a number such as 60 to see server FPS in the Console. Set it back to 0 later.
2. Leave Max FPS (MAX_FPS) at a sensible value. It only caps the server.
3. Lower player count or heavy mods.

Cannot use admin commands

Why it happens: The admin password was not set or not typed correctly.

How to fix it:

1. Set Admin Password (ADMIN_PASS) on Startup and restart.
2. In game, log in with the admin login command using that password.

Server stuck on installing or updating

Why it happens: The first install and each update download a lot of data.

How to fix it:

1. Wait and watch the Console.
2. Check disk space. See Disk full.
3. If it does not finish, open a ticket.

My config.json changes keep reverting

Why it happens: The panel may write the port and address into config.json on start. Settings also set on Startup (name, password, scenario, max players) may be overwritten.

How to fix it: Change those on Startup. Edit only the other parts of config.json, such as the mod list.

Still stuck?

Open a ticket or ask on Discord. See Contact support.