Setting Up Your First Reseller Client Account

Reseller hosting lets you create cPanel accounts for your own clients, each isolated, all managed from a single WHM (Web Host Manager) interface. The mechanics are simple once you’ve done it once. This guide walks through the first client’s full setup — from creating a package to sending the welcome email.

Before you start

Three things you’ll want in place before provisioning your first account:

• Your reseller plan is active. Confirmed in your iWebVault welcome email — you should have a WHM login URL ending in :2087.
• Your reseller nameservers are configured (optional but recommended). If you’ve set up ns1.yourdomain.com and ns2.yourdomain.com, you can white-label hosting — clients see your branded nameservers instead of ns1.iwebvault.com. See DNS records guide for how to configure these.
• Your client has agreed on a plan size — disk space, bandwidth, email accounts, databases. We’ll codify these as a “package” below.

Step 1 — Log into WHM

Your WHM URL is in your welcome email, typically https://[server-hostname]:2087. Log in with your reseller credentials. You’ll land on the WHM dashboard — a different interface from cPanel, with admin-level controls.

Before doing anything else, secure your WHM:

• Change your reseller password (top-right user menu).
• Enable two-factor authentication on your reseller account (Security Center → Two-Factor Authentication).
• Set your contact email under Reseller Center → Edit Reseller Nameservers and Privileges.

Step 2 — Create a hosting package

A package is a template for client accounts — disk space, bandwidth, email accounts, databases, etc. Create one package per plan tier you offer.

1. WHM → Packages → Add a Package.
2. Package Name: something memorable like starter, business, premium. Clients won’t see this; it’s for your internal use.
3. Resources:
   • Disk Quota: 5000 MB (5 GB) is a sensible starter; scale up for premium tiers.
   • Monthly Bandwidth: 50000 MB (50 GB) for small sites, higher for content-heavy.
   • Max FTP Accounts: 5–10 is usually plenty.
   • Max Email Accounts: 10–50 depending on tier.
   • Max Email Lists, Max Databases, Max Sub Domains, Max Parked Domains, Max Addon Domains: set realistic limits per tier.
4. Settings: Enable shell access only if your plan needs it (most don’t). Enable CGI access if needed by the client’s software.
5. Cpanel Theme: leave as jupiter (the modern default).
6. Feature List: default usually works; you can create custom feature lists later to hide features clients shouldn’t use.
7. Click Add.

Now you have a reusable template. Every account you create from this package gets identical limits.

Step 3 — Create the client account

1. WHM → Account Functions → Create a New Account.
2. Domain Information:
   • Domain: the client’s primary domain (e.g. clientdomain.com).
   • Username: cPanel chooses based on the domain (typically the first 8 characters). You can customize.
   • Password: do not type a password — click Password Generator for a strong random one. Save it to your password manager AND your client’s record.
   • Email: the client’s contact email — important, this is where account notifications go.
3. Package: select the package you just created.
4. Settings:
   • cPanel Theme: jupiter.
   • Locale: usually English unless the client prefers otherwise.
   • Check Enable Apache SpamAssassin.
   • Check Enable Spam Box.
5. DNS Settings: if you have reseller nameservers, select Use the nameservers specified at the Domain’s Registrar and uncheck “Use registrar’s default” only if you’ve set up custom NS — otherwise let WHM use your reseller defaults.
6. Click Create.

WHM creates the account in about 10 seconds. You’ll see a success screen with the account details. Copy them.

Step 4 — Verify the account

Before sending credentials to the client, verify the account works:

1. WHM → Account Information → List Accounts → find the new account → click the cPanel icon to log in as them.
2. Confirm File Manager opens and shows public_html/.
3. Confirm Email Accounts works.
4. Confirm the quota matches what you set.

Three minutes of verification saves an embarrassing back-and-forth with a new client whose account had a typo or missing feature.

Step 5 — Send the welcome email

WHM can send a stock welcome email automatically (configured at Account Functions → Manage Account Suspension… no, in fact: Server Configuration → Tweak Settings → Mail → Send welcome email automatically). But the stock template is generic. Better practice: send your own branded email.

Include in your welcome email:

• cPanel login URL — typically https://[server-hostname]:2083 or https://clientdomain.com:2083
• Username and password
• Your branded nameservers (or iWebVault’s defaults)
• Webmail URL — https://clientdomain.com/webmail
• Your support contact
• Link to any documentation or onboarding resources you’ve prepared

If you’re running WHMCS for billing, your welcome email is automated at the WHMCS level — see WHMCS docs for customizing the template.

Step 6 — Set up ongoing client management

Per-client tasks you’ll handle from WHM:

• Password resets — Account Functions → Change a Password.
• Suspending non-paying accounts — Account Functions → Manage Account Suspension. Suspension blocks site access without deleting; instant un-suspension restores service.
• Upgrading or downgrading packages — Account Functions → Upgrade/Downgrade an Account.
• Backups and restoration — JetBackup (if your reseller plan includes it) handles this; otherwise WHM’s built-in backup tool.
• Terminating accounts — Account Functions → Terminate an Account. Permanent — back up first if you’re not 100% sure.

Full WHM reference for these day-to-day operations is in our WHM for resellers guide.

Common reseller setup issues

“Account creation failed”. Usually because the username clashes with an existing account, the domain is already hosted on the server, or your reseller has hit its account limit. WHM error message specifies which. Open a ticket if the issue isn’t clear.

Client’s site shows a “default” or “blank” page. DNS hasn’t propagated yet, or the client hasn’t uploaded content. Verify public_html/ contains files; verify nameservers at registrar point at iWebVault.

SSL not issued for new account. AutoSSL waits for DNS to fully propagate before issuing. Allow up to a few hours; force-trigger from SSL/TLS → Manage AutoSSL → Run AutoSSL for All Users.

Client can’t log in. Verify they’re using the full email/username and correct port (2083). If they’re trying the IP-based URL and getting certificate warnings, suggest the domain-based URL (works once DNS and SSL are live).

What’s next

• Day-to-day WHM operations: WHM for resellers.
• Picking the right reseller plan size? See choosing the right hosting plan.
• Want to white-label more? Setting up your own branded nameservers via DNS — see DNS records guide.

Once you’ve provisioned a few clients, the process becomes 90-second routine. Most resellers settle into a single “package” for 80% of clients with one or two premium variants for larger accounts.