Skip to main content

Get started with cPanel and WHM on your VPS

cPanel & WHM is a commercial control panel for hosting websites, email, DNS and databases on a Linux server. This guide is for people who run their own VPS or cloud server and want to set up cPanel on it, from the first sign-in to a working website with SSL, email and backups.

For a VPS or cloud server you manage yourself

This guide is for a VPS or cloud server where you manage the operating system yourself. If you use DomainPilot web hosting, you don't need to install a control panel.

WHM and cPanel: two interfaces​

The product has two parts that work together:

  • WHM (WebHost Manager) is the administrator side. You sign in as root, the server's all-powerful user, to manage server settings, updates, security and hosting accounts.
  • cPanel is the interface for each hosting account. An account usually holds one main domain plus its files, databases and mailboxes. You can give each client or project its own account and login, without giving them access to the whole server.

Get cPanel onto the server​

There are two ways to start:

  • A ready panel image. Some providers let you pick an image with cPanel already installed when you order the server. This is the quickest option.
  • The official installer. Create the server with a supported operating system, take a snapshot, then follow the installation guide in the cPanel & WHM documentation. Installation can take a while, so let it finish without interrupting the SSH session.
At DomainPilot

DomainPilot VPS plans offer a ready image with cPanel, among other panels. The cPanel licence is billed on top of the server price. VPS is self-managed: DomainPilot looks after the hardware, network and virtualization, and you manage the operating system and the panel.

Sign in for the first time​

WHM and cPanel each have their own HTTPS port:

InterfaceAddress
WHM (administrator)https://server.example.com:2087
cPanel (each account)https://server.example.com:2083

The server's firewall, and any cloud firewall in front of it, must allow these ports. Until the server has a certificate from a trusted authority, your browser may warn that the certificate is self-signed (created by the server itself rather than a certificate authority). That is expected on a new server. Check that the address is your own server before you continue.

Complete the initial setup​

The first time you sign in to WHM, a setup process walks you through the basics. In general terms:

  1. Read and accept the licence terms, and activate the licence or start a trial.
  2. Enter a contact email address for server alerts. Use an address that is not hosted on this server, so alerts still reach you if the server has a problem.
  3. Set the nameservers the server will use, for example ns1.example.com and ns2.example.com, or choose to manage DNS elsewhere. See Nameservers explained and Set up custom nameservers.
  4. Create a package, which sets the resources a hosting account gets, such as disk space and the number of mailboxes.
  5. Create your first hosting account for a domain such as example.com, choosing the package and a strong password.
  6. Point the domain at the server and sign in to cPanel as that account to upload the site or install an app.

SSL certificates​

cPanel includes AutoSSL, which requests and renews free certificates for the domains on each account. It only succeeds once a domain's DNS points at the server, so if a certificate is missing, check the domain's A records first. See SSL certificates for how certificates work.

Email​

Each domain that sends email from the server needs DNS records: an MX record pointing at the server, plus SPF, DKIM and DMARC records that prove the mail is genuine. cPanel can show you the values it expects. See SPF, DKIM and DMARC.

Receiving providers also check reverse DNS, which maps the server's IP address back to a name. It should match the server's hostname. Reverse DNS is set by whoever controls the IP address, so ask your server provider how to set it.

Backups​

WHM can create scheduled backups of every account. Store copies off the server too, for example in remote storage, because a backup on the same disk is lost with the server. Server snapshots add another layer before risky changes. See Snapshots and server backups.

Updates and security​

  • Keep cPanel and the operating system updated. WHM can install updates automatically.
  • Use a strong, unique root password, and turn on two-factor authentication for WHM and cPanel logins.
  • Open only the ports you need, and restrict SSH where you can.
  • Give clients their own cPanel accounts instead of sharing the root login.

Secure a new Linux server covers the general approach.

Official documentation​

Did this article help you?