WHM and cPanel for Resellers: The Day-One Guide

As a reseller you use two control panels: WHM to run your hosting business, and cPanel that your clients use to run their sites. WHM (Web Host Manager) is where you create accounts, define resource packages, set private nameservers, brand everything and suspend non-payers. cPanel is the familiar panel each client logs into for files, email, databases and one-click installs. Learning a handful of WHM tasks is the only real technical skill reselling asks of you.

WHM vs cPanel: who uses what

WHM is the admin layer; cPanel is the user layer. You live in WHM; your clients never see it. They receive a cPanel login that lets them manage only their own account, with no visibility into other accounts or your reseller settings. This separation is what lets you run many clients safely from one plan. If the reseller model itself is new, what reseller hosting is gives the overview.

Day-one task 1: create hosting packages

Start by defining packages, because every account is created from one. A package is a reusable template setting disk space, bandwidth, email accounts, databases and other limits — your equivalent of the "Starter", "Business" and "Pro" plans a host sells. Create two or three that map to what you will offer clients. Sensible limits here are also your first defence against one account starving the others, so resist the urge to make everything unlimited.

Day-one task 2: set private nameservers and branding

In WHM's Basic WebHost Manager Setup, set the default nameservers to your private ones (ns1.yourbrand.com and ns2.yourbrand.com) after creating the matching host records at your registrar. While you are there, add your company name and logo so new accounts and the cPanel your clients see carry your brand. This is the step that makes your hosting white-label; the full walkthrough is in white-label hosting explained.

Day-one task 3: create a client account

Use WHM's Create a New Account: enter the client's domain, a username, an email and a password, pick one of your packages, and create. WHM provisions a full cPanel account in seconds and emails the login details (from your brand, if you set it up). To move an existing site in, use the transfer or backup-restore tools rather than rebuilding it. Suspending, terminating and upgrading accounts live in the same Account Functions area.

Day-one task 4: know your suspension and support tools

Two WHM tools you will use constantly are suspension and "Log in as" support access. Suspending an account for non-payment disables the site without deleting data, so a client who pays late can be restored instantly. The support access lets you enter a client's cPanel to fix an issue without asking for their password. Knowing these before you have angry clients or overdue invoices saves real stress.

The cPanel and WHM ecosystem is powerful, but you only need a dozen screens to run a reseller business. Do not let the hundreds of settings intimidate you — learn the account, package, nameserver and suspension tools first, and pick up the rest as you need them.

A note on cPanel licence costs

On a reseller plan the host pays the cPanel licence, so its rising cost is not your problem — a reason to resell rather than run your own server early on. cPanel raised its 2026 pricing across tiers, which matters only once you move to your own VPS. For now, pick a plan from the best reseller hosting ranking where cPanel is included, and pair it with billing from free WHMCS and billing for resellers to automate account creation later.

Build packages that protect the whole server

Your packages are not just price tiers, they are the guardrails that stop one account from harming the rest. Set realistic disk and, where available, inode limits, and lean on any CPU and memory controls the host exposes. A single runaway site — a misconfigured plugin, a scraper, a mail loop — can degrade every account it shares a server with, and your sensible package limits are the first thing standing between one bad site and a page of angry tickets. Resist making everything unlimited just because the marketing does.

Backups are your job, not the host's

Most hosts run backups, but their policy is for disaster recovery of the whole server, not for restoring one client's file they deleted last Tuesday. Assume you need your own backup routine: many resellers use a cPanel-integrated backup add-on or a third-party service that keeps daily off-site copies of each account. When a client emails in a panic having overwritten their site, being able to restore it in minutes is worth more to your reputation than almost anything else you do. Never assume the host has you covered.

Migrations and DNS without downtime

Bringing a client's existing site into your reseller account is a routine WHM task, but the order matters. Copy the site in first and test it on a temporary URL, lower the domain's DNS time-to-live a day ahead, then switch the nameservers or records and watch it propagate before removing the old host. Rushing the DNS step is the usual cause of a client seeing downtime during a move. Done methodically, a migration is invisible to the client, which is exactly how it should be.

Security settings you should not skip

A few WHM security steps protect you and every client on your account. Enforce strong passwords and, where available, two-factor authentication on your own WHM login, because it holds the keys to every account. Keep the account you use for daily work separate from the master reseller login. Make sure SSL is issued automatically for new accounts so no client site loads insecurely, and review the host's default firewall and brute-force protection. You do not administer the server on a reseller plan, but the accounts and their access are yours to secure — and one compromised client account can drag your whole reputation down with it, so these few minutes of setup are well spent.

As your account grows, spend an hour learning WHM's monitoring and account-listing views. Being able to see disk and bandwidth usage across all your accounts at a glance lets you spot a client approaching their limit before they hit it, or a site consuming far more than it should. Catching these early — a quick email offering an upgrade, or flagging a runaway plugin — is the difference between proactive service and reactive firefighting. The same views help you plan capacity, telling you when your plan is genuinely filling up versus when you simply set quotas too generously.