Arma Reforger Server Not Showing in Browser? Fixes That Work

When an Arma Reforger server does not show in the browser, check that it has finished starting (mods can take minutes to download), that game.visible is true in config.json, that publicAddress and publicPort point to an address players can reach on UDP 2001, and that the server runs the same game version as the players. If it shows but players cannot join, look at mods, crossplay platforms, the password and BattlEye. Try Direct Join with the IP and port to tell a listing problem from a connection problem.

First: listing problem or connection problem?

In the Multiplayer menu, use Direct Join with your server's IP and port.

• Direct Join works: the server is reachable, it is just not listed or is hidden by filters. Read fixes 1 to 4.
• Direct Join fails too: players cannot reach the server or are being refused. Read fixes 5 to 9.

Fix 1: Wait for the server to finish starting

A Reforger server does not register until it has loaded the scenario, and on a modded server it first downloads or updates every mod. With a long mod list, that can take several minutes after a restart or a mod update. Watch the console. When the scenario has loaded and the server reports it is registered with the backend, try the browser again.

Fix 2: Check visible in config.json

"game": {
  "name": "Everon Night Ops",
  "visible": true
}

With visible: false the server runs but is hidden from the browser, and only Direct Join works. That is handy for private groups and easy to leave on by accident.

Fix 3: Check the browser filters

The Reforger browser filters a lot by default. Before blaming the server:

• Search by exact name.
• Clear filters for modded servers, password protected servers and full servers.
• Check the version filter. A server on a different version may be hidden or greyed out.

A unique name helps. Searching "Everon" returns hundreds of servers.

Fix 4: Mods that block listing for some players

Console players only see servers they could actually join. If one mod on your list does not support Xbox or PlayStation, console players will not get your server even with crossplay on. Check every mod's Workshop page for platform support. PC players see the server either way.

Fix 5: publicAddress and publicPort

"bindAddress": "0.0.0.0",
"bindPort": 2001,
"publicAddress": "203.0.113.70",
"publicPort": 2001

publicAddress is what the server tells the backend players should connect to. At home behind a router, it must be your public IP, not the PC's local 192.168.x.x address. publicPort must match the port you forwarded. If either is wrong, the server may appear in the list and still refuse every join attempt.

Fix 6: Open the ports

On a home server, forward UDP 2001 at least, and allow the server through the firewall. Our port forwarding guide covers the router side. If you are behind CGNAT, forwarding cannot work; see how to tell if you are behind CGNAT.

Fix 7: Match the version

Reforger updates regularly, and clients cannot join a server on a different version. After a game update:

1. Update the server (SteamCMD app 1874900) and restart.
2. Make sure everyone is on the same branch. A server on the experimental branch only takes experimental clients, and the other way round.

Mods update separately. When a mod author pushes an update, a server that has not restarted serves the old version, and players who already have the new one are refused or stuck downloading. Restart the server after mod updates.

Fix 8: Crossplay settings

For Xbox and PlayStation players, config.json needs crossplay turned on:

"game": {
  "crossPlatform": true
}

Every mod must also support consoles (fix 4). Without both, console players cannot see or join the server. The full crossplay setup is in our Arma Reforger hosting guide.

Fix 9: Password, slots and BattlEye

• Password: game.password is for joining, game.passwordAdmin is for #login. Players need the first.
• Full server: check maxPlayers against how many are on.
• BattlEye: with battlEye: true, players need BattlEye running. Someone launching the game with it disabled cannot join.

Fix 10: The config did not load

If the server starts with a default name, or settings seem ignored, config.json likely has a syntax error and the server fell back, or failed to start. JSON is strict: no trailing commas, and true and false without quotes. Validate the file in any JSON checker before restarting. Back it up first so you can undo.

The short checklist

Hosted, without the router

A GamezServers Arma Reforger server fills in bindAddress, publicAddress and the ports for you on every start, so the address players get is always right. The control panel has the server name, max players, passwords, BattlEye, third person and a Visible in Server Browser switch, and Automatic Updates checks the server and its mods each time it boots. Crossplay and mods are in config.json in the file manager. For admin tools once players are in, see Arma Reforger admin commands.

FAQ

Why is my Arma Reforger server not in the server browser?

It is still starting or downloading mods, visible is false, browser filters hide it, or the server is on a different version than you.

How do I join an Arma Reforger server by IP?

Open Multiplayer, click Direct Join and enter the IP and port.

Why can Xbox players not see my Reforger server?

Crossplay is off in config.json, or one of your mods does not support consoles.

What port does an Arma Reforger server use?

UDP 2001 by default for game traffic.