Reseller playbook · Beginner · 2 minutes
How to log in to cPanel — The Login URL You Hand a Client Says Who You Buy From
There are several ways into cPanel and they do not all look like your business, which matters when the address goes into a welcome email you send forty times.
Straight answer first
Give clients one address on their own domain — clientdomain.com/cpanel, resolving through your private nameservers — because the server-hostname route works perfectly well and puts the name of the machine, and therefore your supplier, in front of the client.
Two minutes covers a single login. The decision worth making once is which of the three doors goes into your welcome template, and keeping the WHM door out of it entirely.
Written by the Hosting Seller staff · Checked 24 August 2026
Beginner
Skill assumed
2 minutes
Per login
4
Routes worth knowing
24/7
Cover at any hour
Written for the reseller composing a welcome email rather than the person reading one. It assumes you create accounts in WHM and that the address you standardise on will be seen by every client you ever take on.
None of this is difficult. It is simply the kind of default that is set once by accident and then repeated for years, so it is worth setting it on purpose.
Three doors, and only one of them looks like yours
cPanel answers on the client's own domain, on the server's hostname, and through your billing system's single sign-on. All three work. Only the first two are ones you would send to a client, and only the first reads as your infrastructure, because the address is theirs and the nameservers behind it are yours.
The server-hostname route is the one that leaks. It is convenient for you, it survives DNS problems, and it names the machine — which is precisely why it belongs in your own bookmarks and not in a template you send to strangers.
What the login page shows before anyone types anything
A login screen is not neutral. Depending on how the account is reached, a client can see a hostname, a certificate covering a name that is not theirs, and a redirect that resolves somewhere unexpected. None of that is secret information, but all of it answers a question the client had not thought to ask.
Reach cPanel through the client's own domain and the certificate matches, the hostname matches, and there is nothing to explain. That is the whole reason private nameservers under your own brand are worth configuring before your first client rather than after your tenth.
Your door: WHM, and why the client never needs it
WHM is where you create accounts, set package limits, reset passwords and read the mail queue. It answers on its own address with your reseller credentials, and a client account cannot reach it — a cPanel login is confined to that one account by design, which is what makes reselling on shared infrastructure viable at all.
Keep those two worlds separate in your own habits as well. Do the administration in WHM and only enter a client's cPanel when you actually need to see what they see, because logging in as a client is how settings get changed by whoever was last there.
Credentials, resets and the ticket you can stop receiving
The most common cPanel support request a reseller receives is not a fault. It is a client who cannot find the password from a welcome email sent eighteen months ago. Answer it once by resetting from WHM's account list rather than resending the original email, and tell the client to store the new credentials in a password manager.
Repeated failed logins trip the server's brute-force protection and will block the client's own address for a while, which turns a forgotten password into an apparent outage. Say that in your welcome note: if it stops accepting the password, stop typing and contact us.
What makes the white-label part work
Private nameservers run under your own brand, so the address a client uses to reach their panel sits on a domain that belongs to the relationship rather than to a supplier.
WHM is yours and every client gets a cPanel of their own, with the limits you set — which is what keeps forty accounts administrable from one screen.
- One client-facing address, on their own domain
- The hostname route kept for your bookmarks
- WHM as the door clients cannot reach
- Resets from the account list, not the old email
Why Hosting Seller
On every plan, as standard
One address in the template
Settles which URL goes into a welcome email you will send to every client you ever take on.
Nothing to explain
Reaching the panel on the client's own domain means the hostname and the certificate both match.
Two worlds kept apart
Administration in WHM, client view only when you need it, so nobody changes settings by accident.
The commonest ticket, closed
Handles the forgotten-password request with a reset from the account list rather than a resent email.
The lockout, pre-explained
Warns clients that repeated attempts trip protection, so a forgotten password never looks like an outage.
Branded where it counts
Private nameservers under your own brand, so the client-facing route belongs to your business.
First Steps
From choosing to live
- 1
Standardise on the client's own domain
clientdomain.com/cpanel, answered through your private nameservers. Put that single address in the welcome template and never vary it, because a consistent route is one fewer thing every client has to be told twice.
- 2
Keep the server hostname for your own bookmarks
The hostname route is useful when DNS is mid-change or a domain has not resolved yet. It also names the machine, so it belongs in your browser rather than in anything a client will read.
- 3
Log in to WHM by the door clients never see
Your reseller credentials open the account list, the package settings, the mail queue and the resets. That screen is where nearly all your administration should happen, not inside individual client panels.
- 4
Reset from the account list instead of resending emails
When a client loses their password, generate a new one in WHM and hand it over with a note about storing it properly. Digging out the original welcome email teaches the client to keep asking you.
In the Box
Packed with every plan
- Private nameservers running under your own brand
- WHM for you, a cPanel of their own for every client
- You set the limits each client account gets
- cPanel, the panel the rest of the trade already knows
- Packages you build and name yourself
- Free SSL on every client site, reissued before it lapses
- Daily backups across every client account
- Ready to wire into WHMCS billing
- A 99.9% uptime target, watched day and night
- Real people answer, for you and for them
Across the Counter
Things people ask us all the time
Which cPanel address should go in my welcome email?
The one on the client's own domain, answered by your private nameservers. It works, the certificate matches, and it says nothing about the machine underneath. Keep the server-hostname route for yourself, where it earns its keep during DNS changes.
Can a client get from their cPanel into my WHM?
No. A cPanel login is confined to its own account, and reseller administration lives on a separate login entirely. That separation is what makes selling accounts on shared infrastructure workable, and it is worth understanding before you start handing out logins.
Which control panel do the accounts I resell actually run?
cPanel, which the whole trade already knows — so every tutorial online matches what your clients see, and a backup restores onto any cPanel host anywhere. Plesk and DirectAdmin reseller options are on the shelf for anyone who prefers them.
Is the SSL on client sites genuinely free?
On every plan, with nothing held back. Certificates are issued once the domain points here and reissue themselves before expiry. The encryption matches a paid DV certificate — the paid tiers exist for wildcard coverage and organisation validation, which most client sites never need.
Read next
Agency Hosting
Client accounts, staging and care-plan plumbing built for agencies.
WordPress Hosting
WordPress hosting for the client sites you look after — LiteSpeed, staging and daily backups.
Moving your site to another host? Start with this checklist.
A step-by-step order of work for a move your visitors never spot: which files to copy first, how to carry email across without losing one message, the right moment to repoint DNS, and the two mistakes behind nearly every hour of downtime people ring us about.
Make the hosting look like yours.
Private nameservers, WHM, packages you name yourself, and a cPanel of their own for every client.
See Agency Hosting plans