
Why does Rust+ say your paired server is offline?
If players can join the game but two paired players see Offline in Rust+, check the server's companion connection. A successful pair can leave an entry in the app even when that connection fails.
Compare two phones before changing the server
Pick the same paired server on both phones and use a second network for one of the checks. If one phone shows the current game time or player count, you have a working companion connection from at least that network. Check the affected phone's network and account first.
| What you see | Where to look next |
|---|---|
| The same phone works on Wi-Fi but fails on mobile data | Check that the phone lets Rust+ use mobile data, and try another phone on a separate network. Continue with the server checks if the problem affects both players. |
| Neither paired player can open it and the game still works | Read app.info and check the startup log for a companion registration or connectivity error. |
| One player has an old server entry after a move | Confirm they are opening the active server. Use the current pairing for that server and keep the existing identity files while investigating. |
Follow the companion port to the process
For example, a second game server was set up with its own game ports, but the router still sends the companion port to the first host. Compare the public address and port shown by app.info with the router or host panel. If the port is correct and the log reports failed registration, also check if the Rust host can reach companion-rust.facepunch.com.
If the startup log says Rust+ was disabled after a failed connectivity check, warn players and restart after fixing access so the game can check again. A listen-port change also needs a restart. Open the same paired entry over mobile data and verify it shows live server information.