Back Up companion.id Before Moving a Rust Server

Before migrating or restoring a Rust server, preserve its Rust+ identity files. Facepunch documents companion.id as the server’s Rust+ identity and says it should remain with the server and its backups.

For related administration guides, follow sourced Rust coverage on TOP OF GAMES.

Files to preserve

The two Rust+ files serve different purposes:

• companion.id is the server’s unique Rust+ identifier.
• player.tokens stores unique tokens for players paired through Rust+. Removing it forces those players to pair again.

Preserve both files when a move must retain the server’s Rust+ identity and existing player pairings.

Protect companion.id

Facepunch instructs operators not to share companion.id, use another server’s file, reuse one file across multiple servers, delete it arbitrarily, or change the app.id convar. Violating these rules can cause incorrect Rust+ behavior, disable players’ notification permissions, and probably require players to pair again.

Deleting companion.id generates a new server identity. Facepunch says the previous identity cannot be recovered after deletion.

Check Rust+ after the move

Run app.info to see the companion port and current connection settings. The companion TCP port must be accessible over the internet and use port number 10000 or higher.

If registration or push notifications fail, verify that the server can reach companion-rust.facepunch.com. Facepunch documents app.listenip for selecting the listening network interface and app.publicip for correcting the IP address advertised to the app.

When the automatic connectivity test fails, the server logs Rust+ companion server connectivity test failed! Disabling Rust+ features. and disables Rust+ features. Connectivity checks are limited to 10 attempts per public IP within five minutes. After reaching that limit, operators must wait five minutes before registering additional Rust+ instances.