Update BeamMP Server Without Breaking Mods

Safe update order

1. Backup ServerConfig.toml + Resources/ (backup guide).
2. Announce downtime.
3. Apply the BeamMP server update via panel/egg update flow.
4. Confirm config preserved; re-paste AuthKey if needed.
5. Start → console clean → Direct Connect → list check if public.

Related guides

• Backups
• AuthKey
• List Visibility

Frequently Asked Questions

Will updates wipe AuthKey?

They should not if ServerConfig.toml is preserved — verify after update.

Resources disappear?

Restore from backup; never update without a snapshot.

List broken after update?

Re-check AuthKey, Private flag, and ports; Direct Connect still works.

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.