A forced reboot allows a Server Administrator to restart a server immediately when a standard graceful reboot fails to initiate or complete. This procedure is performed via the WHM interface and is intended for use only when the server is unresponsive to standard commands.
Warning: A forced reboot will immediately terminate all active processes and disconnect all active sessions. This can result in the loss of unsaved data for any users currently logged into the server or any applications currently processing tasks.
Before you begin
You will need:
Server Administrator access to WHM
A confirmed failure of the standard graceful reboot procedure
Performing a forced reboot
Log in to WHM.
In the left-hand navigation menu, go to Server Information > Reboot.
Locate the Force Reboot section.
Select the specific server you need to reboot from the list.
Click Force Reboot.
Confirm the result
The server will begin a hard reboot sequence.
Once the reboot is complete, the server status in WHM will return to Online.
You can verify the uptime by checking the Server Information page.
If the server remains unreachable after a forced reboot
If the server does not come back online or remains in a "Down" state after a forced reboot, the issue may be related to hardware, a kernel panic, or a network configuration error.
In this event, contact Hostek support for a manual investigation of the server's hardware and network status. Provide the server's IP address or hostname to the technician.
Limitations
A forced reboot is a high-level administrative action. It does not perform a graceful shutdown of services; it instructs the hardware to restart immediately. This procedure should only be used as a secondary option when a standard reboot is not successful.
