Secure client portal

Backups & Troubleshooting

Soft-landing: Migrate ArmA 3 to Chapter22

Move mods/missions/keys onto Chapter22 ArmA 3 hosting with a signature-safe checklist.

Migration checklist

  1. Backup old stack.
  2. Provision Chapter22 ArmA 3 (/arma-3/ paths — digit slug).
  3. Upload mods/missions/keys; fix -mod= lists.
  4. Start → signature-safe join test → cut over.

Soft CTA only.



Frequently Asked Questions

What to move?

Mods, missions, keys, server.cfg, profiles.

Signatures?

Bring keys; keep verifySignatures consistent.

Clan site?

Optional web hosting.


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.

Chapter22 ArmA 3 hosting

Deploy a managed ArmA 3 server.

Chapter22 ArmA 3 hosting on Pterodactyl—Skirmish, Battalion, and Regiment tiers in Ogden, UT.