Managing Multiple Clients on Reseller Hosting: A Practical WHM Guide

Overview

Reseller hosting lets you create and manage multiple cPanel accounts under a single WHM (Web Host Manager) login. Each account belongs to one of your clients, and they get their own cPanel interface while you control the limits, packages, and overall environment from WHM. Good reseller management means your clients rarely need to contact you — and when they do, you can fix things fast.

Most resellers run into trouble early on by skipping package setup and creating accounts ad hoc. That makes billing, resource tracking, and support a mess when you have 15+ clients. This article covers how to do it properly from the start, and how to clean things up if you’ve already gone down that road.

If you’re still evaluating whether reseller hosting fits your business model, take a look at our Reseller Hosting plans to understand what resources you’re working with before setting anything up.

Prerequisites

• An active reseller hosting account with WHM access
• WHM login credentials (typically at https://yourdomain.com:2087)
• A registered domain for each client you’re onboarding (or a subdomain if you’re using a temporary URL)
• Private nameservers configured for your reseller account (covered in Step 1)
• Basic understanding of DNS — specifically A records and nameserver records
• cPanel/WHM version 118 or later (steps may differ slightly on older builds)

Step-by-Step Instructions

Step 1: Configure Private Nameservers

Do this before you create a single client account. Private nameservers let your clients’ sites resolve under your brand (e.g. ns1.youragency.com) instead of your host’s nameservers. It’s a white-label baseline — without it, your clients can see who you’re hosting with.

1. In WHM, go to Server Configuration > Basic WebHost Manager Setup.
2. Scroll to the Nameservers section and enter your primary and secondary nameservers (e.g. ns1.youragency.com and ns2.youragency.com).
3. Save changes, then go to DNS Functions > Add a DNS Zone — but actually, you’ll handle the A records for those nameservers at your domain registrar. Point ns1 and ns2 to your reseller server’s IP address.
4. Back in WHM, go to Server Configuration > Nameserver Selection and confirm you’re using BIND or PowerDNS (BIND is the default and most compatible).

📝 Note: DNS propagation for new nameservers can take up to 24 hours. I’d recommend setting these up a day before you start onboarding clients.

Step 2: Create Hosting Packages

Packages (also called plans) define the resource limits for each account type. Think of them as templates. Instead of manually setting disk space and bandwidth every time you create an account, you assign a package and it applies everything at once.

1. In WHM, navigate to Packages > Add a Package.
2. Name it something descriptive — starter_5gb, business_20gb, or match your billing plan names exactly so there’s no ambiguity.
3. Set your limits:
   • Disk Space (MB): 5120 for 5 GB, 20480 for 20 GB, etc.
   • Monthly Bandwidth (MB): Set a real number. Avoid “unlimited” — it just passes whatever your host allows, and you won’t know when a client is hammering resources.
   • Max Email Accounts, FTP Accounts, Databases: Set sensible defaults. 50 email accounts is reasonable for a small business package.
   • Max Addon Domains: Set to 0 for single-site plans, or higher if you’re offering multi-site packages.
4. Click Add.

⚠ Warning: Don’t set every resource to unlimited across all packages. If a single client gets compromised or runs a runaway script, they can consume your entire reseller allocation and take down everyone else.

Step 3: Create a Client Account

1. Go to Account Functions > Create a New Account.
2. Fill in the Domain field with the client’s primary domain.
3. Set a Username (max 16 characters, alphanumeric, no hyphens). I’d suggest using something tied to their domain — e.g. smithlaw for smithlawfirm.com.
4. Enter a strong password or use the generator. Copy it somewhere — you won’t be able to retrieve it later, only reset it.
5. Under Package, select the package you created in Step 2.
6. Leave Mail Routing Settings on Automatically Detect Configuration unless you know their mail is hosted elsewhere.
7. Click Create.

📝 Note: If you need to create many accounts at once, WHM supports bulk account creation via the API. The endpoint is /json-api/createacct and you can script it with curl or any WHM API wrapper.

Step 4: Log In as a Client (Without Their Password)

This is one of the most useful features in WHM that new resellers don’t know about. You can access any client’s cPanel directly without knowing their password.

1. Go to Account Information > List Accounts.
2. Find the client’s account and click the cPanel icon (it looks like the cPanel logo) on the right side of their row.
3. You’re now inside their cPanel. Make your changes and close the tab when done.

This is a lot faster than asking clients to share credentials and is fully logged in WHM’s audit trail.

Step 5: Apply Branding to WHM (Optional but Recommended)

1. Go to cPanel/WHM > Customize Style in WHM.
2. You can upload a logo and set a custom theme name. This branding appears in the client-facing cPanel interface.
3. For more control, use the Styled Links feature to white-label the support and documentation URLs your clients see.

Step 6: Suspend or Terminate Accounts

When a client cancels or doesn’t pay, you’ll need to act fast.

1. To suspend (reversible): Go to Account Functions > Manage Account Suspension, select the account, add a reason, and click Suspend. Their site goes offline but data is preserved.
2. To terminate (permanent): Go to Account Functions > Terminate Accounts. Select the account and confirm.

⚠ Warning: Termination is irreversible in WHM. All files, databases, and emails are deleted immediately. Always take a full cPanel backup before terminating — use Backup > Generate/Download a Full Backup inside their cPanel first.

Common Issues & Troubleshooting

“Account Creation Failed: Insufficient Disk Space”

Your reseller account has a total disk quota, and the sum of all package allocations has exceeded it. Even if clients aren’t using their full allocation, WHM counts the allocated amount. Go to Account Information > View Bandwidth Usage to see total allocation vs. actual usage, then either upgrade your reseller plan or reduce package limits. In my experience, resellers on shared infrastructure hit this faster than expected once they have 8–10 clients.

New Client’s Site Shows the Default cPanel Placeholder Page

The domain’s DNS is pointing to the right IP, but the account was created after the DNS was already propagating. Or more commonly, the client’s domain is still pointing at their old host. Confirm the domain’s A record resolves to your server IP using dig yourdomain.com A +short from a terminal. If it’s correct, try a hard refresh or test via a different network to rule out local DNS caching.

Client Can’t Send Email — “Relay Access Denied”

This usually means the account’s mail routing is misconfigured. In WHM, go to Email > MX Entry, find their domain, and confirm it’s set to Local Mail Exchanger if you’re hosting their email. If their MX records point somewhere else (like Google Workspace), it should be set to Remote Mail Exchanger. This mismatch is annoyingly common when clients migrate from another host and the MX records haven’t been updated yet.

“Package Does Not Exist” Error When Creating Account

This happens when a package was created in WHM but the account creation form isn’t refreshing properly, or the package name contains special characters that WHM rejects silently. Delete and recreate the package using only lowercase letters, numbers, and underscores. Then reload the account creation page completely before trying again.

Reseller Runs Out of Inodes Before Disk Space

Inodes represent the number of files and directories an account can have. Shared and reseller hosting environments have inode limits separate from disk quotas. A WordPress site with a full cache and large plugin set can have 200,000+ inodes. If a client hits their inode limit, they can’t create new files even if they have disk space left. Check usage via WHM under Account Information > List Accounts — the inode column shows current vs. limit. Either raise the per-account inode limit in the package settings or help the client clean up unnecessary files.

FAQ