How to Reboot Your Dedicated Server
This guide explains how to reboot your Dedicated Server.
You can reboot the server in two ways:
- from the operating system, if SSH access is working,
- from the Client Area, using the server reboot option.
Reboot from SSH
If your server is working and you can connect to it via SSH, we recommend rebooting it from the operating system first.
Log in to your server as root and run:
reboot
The server will restart using the operating system reboot procedure.
After a few minutes, check if the server is online again. You can test it with ping:
ping your.server.hostname
When the server is reachable again, log in via SSH and check the uptime:
uptime
If SSH is working, rebooting from the operating system is usually the preferred method.
Reboot from the Client Area
If your server does not respond correctly, SSH is not working or you cannot reboot it from the operating system, you can reboot it from the Client Area.
To reboot the server from the Client Area:
- Log in to the Client Area.
- Go to My Services.
- Open the Dedicated Server you want to reboot.
- Click the Reboot button.
The Client Area reboot performs a power cycle through the PDU. This means that the server power is switched off for a short moment and then switched on again.
A reboot from the Client Area is a power reboot. The operating system may not shut down cleanly before the power cycle. If the server is responding to SSH, it is better to reboot it from the operating system first.
After Reboot
After starting the reboot, wait a few minutes and then check if the server responds to ping:
ping your.server.hostname
A normal reboot usually takes a few minutes. In most cases, the server should be reachable again within 10–15 minutes.
When the server starts responding, try to connect via SSH again.
If SSH does not work immediately after the reboot, wait a few more minutes. The server may still be booting, checking the filesystem or starting services.
After a power reboot, the operating system may perform a filesystem check during startup. Depending on the disk size, RAID configuration and filesystem state, this may take from a few minutes to longer.
If the server does not come back online after 10–15 minutes, you can check the server console using IPMI, if IPMI access is available for your service. If you cannot check it or the server does not boot correctly, please open a support ticket and include information that the reboot was requested but the server did not come back online.
Verification
If the server responds to ping and the uptime has changed after logging in, the reboot was completed successfully.
If the server does not respond after reboot or you cannot access it after waiting, please open a support ticket and describe what happened before the reboot.
