Troubleshooting

Common issues and solutions for Arma Reforger servers

Arma Reforger Troubleshooting

Solutions to common issues with Arma Reforger servers.

Server Won’t Start

Check Console Output

Look for error messages in the Console tab. Common errors include:

• Missing files
• Invalid configuration
• Port conflicts

Invalid config.json

If you edited config.json and the server won’t start:

1. Check for JSON syntax errors (missing commas, brackets)
2. Validate your JSON at jsonlint.com
3. Restore from backup if needed
4. Reinstall the server to regenerate default config

Invalid Scenario ID

If the scenario ID is incorrect:

1. Check that the scenario ID is properly formatted
2. Use a default scenario ID to test:
   {ECC61978EDCC2B5A}Missions/23_Campaign.conf
   
3. View available scenarios in the console on startup

Port Already in Use

If you see port binding errors:

1. Contact support to verify port allocation
2. Check that another server isn’t using the same ports

Can’t Find Server in Browser

Server Not Visible

1. Ensure "visible": true in config.json or Startup tab
2. Wait 5-10 minutes after starting for browser registration
3. Verify the server is fully started (check for “Starting RPL server” in console)

Wrong Region

1. Check the REGION setting matches your actual region
2. Use the correct ISO country code (US, GB, DE, etc.)

Try Direct Connect

If the browser isn’t working:

1. Use Direct Connect with your server IP and port
2. Find your IP in the Game Panel Network tab

Players Can’t Connect

Connection Timeout

1. Verify the server is running (check Console)
2. Confirm players are using the correct IP and port
3. Check if server password is required

Version Mismatch

1. Ensure the server is updated (enable Auto Update)
2. Have players update their game client
3. Restart the server to apply updates

Mod Mismatch

1. Verify players have all required mods installed
2. Check mod versions match between server and client
3. Temporarily remove mods to test base connectivity

BattlEye Issues

If players get BattlEye errors:

1. Ensure players have BattlEye enabled in their client
2. Try disabling BattlEye temporarily to test (set BATTLEYE to false)
3. Have players verify game files in Steam

Performance Issues

Server Lag

1. Check RAM usage in the Game Panel
2. Reduce MAX_PLAYERS if needed
3. Lower serverMaxViewDistance and networkViewDistance in config
4. Consider upgrading to a higher RAM plan

Low Server FPS

1. Check the MAX_FPS setting (default 120)
2. Reduce player count
3. Remove performance-heavy mods
4. Upgrade server resources if needed

High CPU Usage

1. Reduce view distances in config
2. Lower max FPS limit
3. Reduce player count
4. Consider a higher-tier plan

Mod Issues

Mods Not Loading

1. Verify mod IDs are in hexadecimal format
2. Check mod entries in config.json for typos
3. Ensure dependency mods are listed first
4. Review console output for mod errors

Crash on Mod Load

1. Remove mods one by one to find the culprit
2. Check mod compatibility with current game version
3. Verify all dependencies are installed
4. Contact mod author for support

RCON Not Working

Can’t Connect to RCON

1. Verify RCON port is correct (default: 19999)
2. Check RCON password is set correctly
3. Ensure RCON is enabled in config
4. Use correct RCON permission level

Commands Not Executing

1. Verify your RCON permission level is admin
2. Check command syntax
3. Ensure you’re authenticated properly

Save/Progress Issues

Progress Not Saving

1. Shut down the server gracefully (don’t force stop)
2. Check the profile folder for save files
3. Verify disk space is available

World Reset

1. Check if a scenario change reset the world
2. Restore from backup if available
3. Verify save files exist in profile folder

File Validation

If you suspect corrupted server files:

1. Go to Startup tab
2. Set VALIDATE to true
3. Restart the server (this will take longer than normal)
4. Set VALIDATE back to empty after validation completes

File validation significantly increases startup time. Only enable it when troubleshooting file issues.

Getting More Help

If you’re still having issues:

1. Check Console Logs - Look for specific error messages
2. Review config.json - Ensure valid JSON and correct settings
3. Discord Support - Join our Discord
4. Support Ticket - Open a ticket

When contacting support, include:

• Console output showing the error
• Your config.json contents (remove passwords)
• Steps you’ve already tried