ArmA Reforger Won’t Start / Config JSON Errors

Console checklist

1. Read JSON parse / scenario errors.
2. Revert config.json from backup if needed.
3. Confirm SCENARIO_ID and mod hex IDs.
4. Watch for OOM on small tiers with big mod stacks.
5. Ticket with console excerpts via the client area.

Related guides

• Edit config.json
• Backups
• DDoS Protection Basics for Game Servers

Frequently Asked Questions

JSON error?

Trailing commas / bad quotes break boot — restore backup and re-edit carefully.

Bad scenarioId?

Use a known-good SCENARIO_ID from Startup or BI docs.

OOM?

Heavy mods on Squad (8 GB) may need Platoon/Company or Extra RAM.

Need help?

If you are stuck after following this guide, open a ticket from the Chapter22 client area with the exact error, the port or DNS change you made, and whether the service listens locally (ss / Resource Monitor) but fails externally.

Build the server. Grow the community. Start your next chapter.