# What can you still do when your Rust dashboard is unavailable?

[Rust server guides](https://rustsc.com/learn/index.html.md) / [Server management](https://rustsc.com/learn/management/index.html.md)

Practice using a route that works without your usual dashboard. For a server at home, sign in directly to your host. For a rental, try your provider’s panel. Check the game from a player’s side first so you know whether the outage affects Rust or only the way you manage it.

## Test with the dashboard closed

Keep the normal dashboard closed for the rehearsal. Join a spare game using the public game address. Then use your independent route to find out what is running and where you can read the latest output. Try a planned stop and start and ask a friend to join again.

If your second route needs a link or sign-in you normally open inside the dashboard, put it somewhere you can reach without the dashboard. If the rental panel itself is the only route, identify the host’s support contact and write the information they need to find the server.

## Check what the missed action does when the site returns

During a real outage, write down any manual action you took and what happened. Look at the dashboard history before sending another start or restart after it returns. A game that already recovered may only need a fresh status check.

Keep a three-line fallback with the player join path, the independent management or support path, and where to say the action was completed.

## Sources

- [Facepunch connecting directly to a Rust game server](https://wiki.facepunch.com/rust/Creating-a-server)
- [Google Cloud testing recovery paths and dependencies](https://docs.cloud.google.com/architecture/framework/reliability/perform-testing-for-recovery-from-failures)

## Related resources

- [What to tell players when your Rust server goes down](https://rustsc.com/learn/community/rust-outage-status-post/index.html.md)

---

HTML version: https://rustsc.com/learn/management/manage-rust-without-the-usual-dashboard/
