Start and stop your server safely
Audience: server users with control.power. Controls also depend on server state and current operations.
Choose an action
Section titled “Choose an action”| Action | Meaning | Before you use it |
|---|---|---|
| Start | Request startup of a stopped machine. | Check installation and host availability. |
| Shutdown | Ask the guest to stop gracefully. | Save work and allow applications to finish. |
| Restart | Request a guest restart. | Warn active users and save work. |
| Kill | Force the machine off. | Use only after assessing the data-loss risk. |
An unavailable button can reflect missing permission, unknown state, or an operation already in progress. A graceful action depends on guest support; lack of immediate response is not permission to force stop blindly.
Request and verify an action
Section titled “Request and verify an action”- Open Servers and select the server.
- Confirm its identity and current state on Overview.
- Save guest work and notify affected users.
- Select the intended power action.
- Read the confirmation, if shown.
- Enter the requested server identifier for a force action.
- Wait for the action result and refreshed state.
- Verify the expected guest or application state separately.
An accepted request is not a completed transition. Avoid repeated clicks while the operation is busy. A machine can be running while its application is unavailable.
If the state does not change
Section titled “If the state does not change”Check Activity for a failure and Telemetry for freshness. If status is unknown or the node is unavailable, contact support with the action and time. Do not repeat force controls to resolve an offline host. Stopping runtime does not necessarily stop provider billing.