1. bluehost knowledge base

VPS & Dedicated Hosting: Restarting Services

This article will explain how to restart your Dedicated or VPS server.

Note: When possible, it's best to restart only the service having issues on your server instead of restarting the entire server.



Restarting a Single Service

To begin, you will need to log in to WHM. If you have never done this before, please see Log in to WHM.

Note: If this is your first time logging into the WHM, you may see a page titled "Feature Showcase." Click on Exit to WHM at the bottom of the page.

Once logged in:
  1. In the top-left search bar, type "Restart."
  2. Under Restart Services, select the service you want to restart. 
    Note: If you aren't sure which service to restart, you can restart each service one at a time to see if it resolves your issue.
  3. Click the Yes button to restart the service.
  4. Wait for the service to be restarted, then check if your issue has been resolved.
 

Restarting the Server

The server can be easily restarted from your Bluehost account. 

Note: If you have tried to restart individual services and still need to do a full system reboot, it's best to contact support so we can watch the server reboot safely. Occasionally, a reboot can fail and cause unintended problems like "FSCK" and other types of data loss and corruption. FSCK (file system consistency check) is a command that is usually run non-interactively to preen the file systems after an abrupt system halt in which the latest file system changes were not written to disk. Preening automatically fixes any basic file system inconsistencies and does not try to repair more serious errors.

  1. Login to your Bluehost account.
  2. Click on the hosting tab at the top menu.
  3. Click on the performance link under the hosting tab.
  4. Click on the server management on the left side.
  5. Click the reboot button.
    legacy-server-reboot.png
The "server is:" status should change from running to rebooting.
Server is Rebooting
Once the reboot is finished, it should change back to running. Then you can check if your issue has been resolved.