What’s new: the Restart recommended notice
The notice appears at the top of your instance page, and only when a configuration update is waiting to be applied. The rest of the time, nothing shows. Its wording follows the state of the instance:- Running instance: “A configuration update for your instance will be applied at its next restart from the console. Restarting from the operating system is not enough.”
- Stopped instance: “A configuration update for your instance will be applied at its next start.”
Why sudo reboot is not enough
sudo reboot restarts the operating system without powering off the virtual machine. The pending configuration stays pending.
A restart started from the console, or from the API, is a full stop of the virtual machine followed by a start. That cycle is what applies the update.
Starting a stopped instance from the console applies the pending configuration too.
Apply the update from the console
- Open your instance page in the console.
- In the Restart recommended notice, click Restart now (or Start now if the instance is stopped).
- Confirm in the usual confirmation dialog.
- Follow the operation in the progress dialog.
The button is disabled while an operation is running on the instance. It becomes available again once that operation ends.
What you can do
Track it through the API
In the public API, the instance exposes a read-only field,restart_required. It is true when a configuration update is waiting to be applied.
Your scripts and monitoring tools can read it to schedule the restart in your maintenance window, then trigger it through the API.
Go further
- Step-by-step guide: restart your VPS.
- Keep a return point before any change: try free VPS backups.
- VPS won’t boot? Try rescue mode.

