Restart Services

How to Restart Services with WHM

Updated: 08 October 2024

Introduction

Restarting services through the Web Host Manager (WHM) is a straightforward process. In this tutorial, we will guide you through the steps to restart services like HTTP Server (Apache), SQL Server (MySQL), and others. Let's get started.

Step 1: Access Web Host Manager (WHM)

First, you need to log in to your WHM account. You can do this by typing your website URL followed by ':2087' in your browser's address bar.

Step 2: Navigate to Restart Services

Once you're logged in, look for the Restart Services section in the left-hand sidebar.

If you can't find the Restart Services section, you can use the search bar at the top left corner of the WHM dashboard. Type 'restart services' and click on the relevant result.

Step 3: Select the Service to Restart

The Restart Services section will display a list of all the services that you can restart. Simply click on the service you wish to restart. Here are some of the most commonly restarted services:

  • FTP Server (Pure-FTPd)
  • HTTP Server (Apache)
  • IMAP Server
  • SQL Server (MySQL)
  • DNS Server (BIND/NSD/MyDNS)

Step 4: Confirm the Restart

After selecting the service you wish to restart, you will be taken to a new page. Click on Yes to confirm the restart. WHM will then attempt to stop and restart the selected service.

Step 5: Check the Status of the Service

Once the restart process is complete, WHM will display a status message. If the service was successfully restarted, the status message will indicate 'The service restart was successful'.

Checking Service Status

You can also check the status of a service by navigating to the Service Status section in WHM. This section will provide you with real-time updates about all your services.

And that's it! You've successfully restarted a service through the Web Host Manager. Remember to only restart services when necessary as it may temporarily disrupt your website functionality.

Caution

Restarting a service will temporarily disrupt its operation. Make sure to inform your users if a significant downtime is expected. Also, double-check the service you are restarting to avoid accidentally disrupting a different service.