Arma 3 server errors and how to fix them

Most Arma 3 server problems come from three things: versions that don’t match, mods that don’t match, and typos in server.cfg. Find the message or symptom below.

“Bad version, server rejected connection”

The player’s game and the server are on different versions.

1. Players update Arma 3 in Steam. Anyone on a beta branch, like profiling, switches back to the main one.
2. Stop the server and start it again so it updates from the same release.

If you run Arma 3 with Creator DLC, the server is on the Creator DLC branch, which still matches the normal game.

“Files not signed by a key accepted by this server”

A player loaded a mod the server doesn’t have a key for, or a different version of one.

1. Check that each mod’s .bikey is in the server’s keys folder.
2. Check that players run the same versions as the server. After a Workshop update, upload the new mod folder and key, then restart.
3. Ask players to load only the server’s mods. A preset from the mods guide helps.

Stuck on “Waiting for host”

The server is up but no mission is running.

• Log in with #login and your admin password, then pick a mission with #missions.
• Check server.cfg: the template name in the Missions class must match a file in mpmissions, without .pbo.
• Check the mission’s map is loaded. A mission on a mod map needs that mod in the Mods setting.

“You cannot play/edit this mission; it is dependent on downloadable content that has been deleted”

The mission needs mods or DLC the player or server hasn’t loaded. The message lists the missing addons. Load those mods on the server and in the player’s Launcher, or pick a mission that doesn’t need them.

A mod won’t load

• Uppercase names. The Linux server looks files up in lowercase. Rename the mod folder, and if needed its files, to lowercase.
• Wrong path in the Mods setting. Each entry is mods/@name, separated by semicolons, with no spaces.
• Missing required mod. ACE needs CBA, for one. Add the required mod first in the list.

The console names the missing addon when a mission can’t start.

Kicked by BattlEye

• “BattlEye: Client not responding” usually means BattlEye on the player’s PC isn’t installed or is blocked. Players verify Arma 3’s files in Steam, which reinstalls BattlEye.
• Kicked right after joining: the player started the game without BattlEye. Start from the Launcher with BattlEye on.

You can turn BattlEye anti-cheat off in Settings for a private group, but keep it on for public servers.

“Session lost”

The connection dropped. Often it’s the player’s network. If everyone drops at once, the server stalled: check memory on Overview and see performance.

The server isn’t in the browser

1. Check it’s running in Console.
2. Give it a minute after a restart.
3. In the browser, clear filters for version, mods and ping, then search for the exact name.
4. Join with Direct Connect and the address and port from your address card. See how to connect.

The server won’t start after a change

A missing semicolon or quote in server.cfg stops the server from reading the rest. Read the last lines in Console, then restore yesterday’s file from Files if you can’t find the typo.

Still stuck?

Write to us at support@wilderack.com. Real people answer. Tell us your server name, what you changed last and the exact message. The help form in the panel can attach your server’s last log lines for you.