cPanel on an InterServer VPS (2026): Licence, Slice Size, WHM First Login, Accounts, SSL, Backups

1. What you are buying: slices plus a licence

InterServer's cPanel Cloud Compute page describes the product as "cPanel cloud compute with WHM control on scalable KVM slices" and sums up what the panel is for: "Use cPanel and WHM for websites, email, calendars, databases, DNS, SSL, backups, reseller-style account management, and automation on cloud compute that can grow from 1 to 32 slices." The server part is the same slice ladder as every InterServer Linux VPS; the page's cards for the first four sizes:

Core counts are as printed on InterServer's slice cards, where one and two slices both show one core; its FAQ describes the allocation as "every two slices has access to one CPU core", so a single slice is a share of a core rather than a whole one.

The licence is the second line. InterServer's page: "The VPS slice price starts at $3 per month, then cPanel/WHM licensing is configured during ordering. Select the current cPanel option, operating system template, and any add-ons in the order flow so the final monthly total is clear before checkout." The page does not print a licence price, so the reference is cPanel's own pricing page, which in September 2026 lists four tiers, each marked "Available on Cloud/VPS Only":

The right-hand column is arithmetic on list prices, not InterServer's quote; hosts often resell licences at their own figure, and the one that counts is the total the order form shows before checkout. The point of the table is the proportion: on a small server the panel costs several times what the server does. An "account" in cPanel's sense, from its pricing page, "is another term for a cPanel user account that manages websites, files, domains, and email accounts", so a Solo licence suits one owner with any number of their own sites under one login, and the Admin tier is where separate client logins begin.

2. Which slice count cPanel needs

cPanel publishes hardware requirements per operating system. For AlmaLinux 8, 9 and 10 the table reads the same: a 1.1 GHz processor, 2 GB of RAM minimum and 4 GB recommended, 20 GB of disk minimum and 40 GB recommended, 64-bit only. A warning follows: "We strongly recommend that you install at least 3 GB of RAM if you want to install the Clam AntiVirus Scanner (ClamAV) antivirus software." cPanel also notes that servers hosting many sites with mail and databases need more of everything, without giving figures.

Mapped to slices: one slice is the bare minimum and leaves the panel, Apache, MySQL and Exim sharing 2 GB with no headroom; two slices meet the recommendation at $6 and is the size this guide suggests you start at; three slices if you want ClamAV scanning mail. InterServer's own advice on the cPanel page is the same shape: "Choose the slice count that gives cPanel and WHM enough room to run." On CPU, InterServer's FAQ explains the ladder: "every two slices has access to one CPU core", so a two-slice cPanel server has one core and a four-slice server two. Adding slices later is done from your account rather than by moving servers; the InterServer VPS guide covers the mechanics.

3. Operating system, hostname and IP

Three requirements come from cPanel and one choice from InterServer.

• Operating system. cPanel & WHM installs on AlmaLinux 8 (cPanel 110 or later), AlmaLinux 9 (114 or later) and AlmaLinux 10 (132 or later), as well as CloudLinux, Rocky Linux and Ubuntu, per its installation guide. InterServer's cPanel slice cards each say "AlmaLinux-ready server", and its OS options page puts the rule plainly: "cPanel, DirectAdmin, Webuzo, and Plesk work best when the selected OS template matches the panel vendor requirements." Choose the current AlmaLinux template in the order form.
• Hostname. cPanel requires the hostname to "Be a registered and fully-qualified domain name", something like srv1.yourdomain.com, and says a server without a resolvable one "will automatically receive one" from cPanel's parent company. Decide the hostname before ordering, and create an A record for it pointing at the server's IP as soon as you have the IP.
• Static IP. "You must configure your Ethernet device with a static IP address and a fully-qualified hostname." Every InterServer slice comes with one IPv4 address, which satisfies this; extra addresses are covered in section 10.
• SELinux. cPanel's requirements state that "SELinux in enforcing mode does not allow cPanel & WHM to function properly" and that it must be disabled. On a server InterServer provisions with cPanel this is the installer's concern, not yours; if you ever install cPanel yourself on a plain AlmaLinux slice, it is step one of cPanel's installation guide.

InterServer's FAQ says of a panel server: "we support software installed by the control panel, including the panel itself", and its VPS page says licences and installs are handled inside My.InterServer, so expect to receive a server with cPanel already installed and licensed. The pages do not give a provisioning time.

4. First login to WHM and the first settings

WHM is the server-owner interface and cPanel the per-account one. cPanel's login documentation gives the addresses: for WHM, "Enter the IP address or domain and the 2087 service port in your preferred browser", for cPanel port 2083 and for webmail port 2096. InterServer's page states the same for the panel: "cPanel is commonly reached on port 2082, with SSL-secured access on port 2083." Use the SSL ports (2083, 2087, 2096) and ignore the plain ones (2082, 2086, 2095). The first visit will show a certificate warning because the server has no certificate for its IP yet; that clears once the hostname has a certificate.

1. Log in as root with the password InterServer issued. cPanel's rule: "In order to log into WHM, you must either be the root user, or a user with reseller privileges."
2. Change the root password from WHM's Server Configuration section, and store it in a password manager.
3. Basic WebHost Manager Setup (WHM, Server Configuration). cPanel's documentation: "This interface allows you to configure basic settings for cPanel & WHM, such as contact information or nameservers." Enter the email address to be alerted at, and the nameservers your accounts will use.
4. Nameservers, two ways. Either the server is its own DNS (register ns1 and ns2 at your registrar pointing at the server IP and enter them here), or DNS stays at the registrar or at Cloudflare and you add A records by hand for each site. The second is simpler for one owner with a few sites and leaves a working DNS if the server is down; the first is what a reseller with client accounts wants. This is the guide's judgement; cPanel's interface supports both.
5. Force SSL for the panel. cPanel's firewall documentation points to a Tweak Settings option (WHM, Server Configuration, Tweak Settings) that redirects the plain ports to the SSL ones; turn it on.
6. Firewall. cPanel's requirements say to disable the OS firewall for installation and then "configure a firewall" once the installation finishes. cPanel's port list is the allow list; the ones a small server needs open inbound are 22 (SSH), 25, 465 and 587 (mail), 53 (DNS, only if the server is a nameserver), 80 and 443 (web), 110, 143, 993 and 995 (mail retrieval), 2083 and 2087 (panel) and 2096 (webmail). Everything else stays closed.

5. The first cPanel account

Sites live in accounts. cPanel's documentation: "The Create a New Account interface allows you to create new cPanel or WHM accounts." It is under Account Functions in WHM, and asks for a domain, a username and a password, and a package.

• Domain. Two options in the interface: a domain you own, or "Choose a domain later", in which case "cPanel & WHM will assign a temporary domain name to the account", with the caveat that "You cannot change an existing cPanel account to use a temporary domain." Use your real domain if you have one; the temporary domain is for testing before DNS moves.
• Package. "A package defines the account's limitations", such as disk space and transfer. Create one first under Packages (WHM) even for your own single account; it is the object you adjust later, and it is what a reseller sells.
• DNS. If the server is not its own nameserver, add an A record for the domain and for www pointing at the server IP at your DNS host. Until that resolves, use the temporary domain or a hosts-file entry to check the site.

Then log in to the account itself on port 2083, upload files or install WordPress with WP Toolkit (cPanel's pricing page lists WP Toolkit as included on every plan), create a database and a mailbox. From here the workflow is cPanel's and its documentation is thorough; this site's WordPress guide and migration guide cover moving an existing site's files and database onto the new account.

6. SSL with AutoSSL

WHM's Manage AutoSSL (SSL/TLS section) is the feature "which automatically installs domain-validated SSL certificates" for the accounts' domains across the web, mail and panel services, and "By default, the system uses the Let's Encrypt provider." There is nothing to buy. Two steps matter on a new server: make sure the domain's DNS points at the server before you expect a certificate (AutoSSL runs a preflight check and adds a CAA record in the zone before ordering), and use the "Run AutoSSL for All Users" button after the first account rather than waiting for the scheduled run. The interface also lists which users receive AutoSSL certificates and keeps a log per run, which is where to look when a domain stays on the warning page.

7. Email on the server

A cPanel account includes mailboxes, webmail on port 2096 and the mail server itself (Exim), and InterServer's FAQ counts mail among the panel software it supports. Two things are outside the panel and worth doing in the first week. First, ask InterServer by ticket to set the reverse DNS (PTR) record of your IP to the server hostname; receiving servers check it, and only the IP's owner can set it. Second, publish SPF and DKIM records for each sending domain; cPanel generates both and shows them in the account's email tools, and if DNS is at your registrar or Cloudflare you copy them there. Whether InterServer filters outbound port 25 on new servers is not stated on the pages this guide read; if a test message does not leave the server, that is the first question for the ticket.

8. Backups to a destination off the server

WHM's Backup Configuration (Backup section) is the tool, and its documentation is direct about where the copies should go: "We strongly recommend that you also save your backups to a remote Additional Destinations location." The reasoning is disk: the backup queue and the transfer queue are separate, and local copies can fill the drive. InterServer's cPanel page says the same from the other side: "Add off-server backup storage when the VPS hosts important accounts, databases, email, or production sites that need a separate restore path."

1. Enable backups on the Backup Settings tab and choose the type. Compressed or uncompressed full backups work with any destination; "If you use the Incremental backup type, you can only use Rsync additional destinations."
2. Schedule and retention. Daily, weekly and monthly runs can be combined; each has its own retention count. A daily run kept for a week plus a monthly kept for three is a sensible floor for a small server.
3. Keep a local copy and a remote one. cPanel: "We recommend that you both enable this setting and specify a remote destination." Without either, the run fails with a "Nowhere to back up" error.
4. Pick a destination type on the Additional Destinations tab. cPanel's documentation lists Additional Local Directory, Amazon S3, S3 Compatible, Backblaze B2, Google Drive, FTP, SFTP, Rsync, WebDAV and Custom. For an InterServer server the natural remote is a second, cheap machine reached by SFTP or rsync: InterServer's own Storage Cloud Compute line starts at 1 TB for $3 a month (per its storage page, and covered on the storage page), or a Hetzner Storage Box, or Backblaze B2 as object storage.
5. Validate. The Validation Results tab tests the destination; run it, then restore one account to a test domain once so you know the path works before you need it.

InterServer does not advertise VPS snapshots (see the InterServer VPS guide), so WHM's backups are the only point-in-time copy of the server you will have. That is the reason to configure them on day one rather than when the first account matters.

9. What InterServer supports, and what is yours

InterServer's FAQ draws the line by panel: "If you order a VPS without a control panel, we manage the operating system and help with operating-system problems such as boot issues, security updates, patches, and reinstalls. If the server includes a control panel such as cPanel, we support software installed by the control panel, including the panel itself, web server, FTP, and mail." Its cPanel page adds: "Managed support is included on Linux VPS plans with 8 or more slices for common service and panel issues."

Read together: a cPanel server gets support for the panel and its stack at any size, and a broader managed tier from eight slices. What remains yours at every size is what runs inside the accounts (a plugin that breaks a site, a theme's PHP errors, a full mailbox) and the decisions about DNS, backups and updates. The two sentences come from two InterServer pages, and the exact boundary for a two-slice cPanel server is worth confirming in a ticket before you depend on it. Click-level steps for InterServer's own panels live in its knowledge base, which this site could not read on the day of writing and links rather than quotes.

10. Growing: slices, accounts, IPs

• Slices. Add them from My.InterServer when memory or CPU runs short; each adds 2 GB, 40 GB and 2 TB for $3, and every second slice a core. WHM's Server Status shows memory and load; cPanel's own figures (2 GB minimum, 4 GB recommended) are for the panel alone, so a server carrying several busy accounts will want four slices or more.
• Accounts. The licence tier sets the ceiling: 1, 5, 30 or 100 cPanel accounts on cPanel's list. When you outgrow Solo, the change is a licence upgrade, not a server change.
• IP addresses. InterServer's FAQ: "You can have up to five additional IPs on your VPS or cloud server, and additional IPs can be purchased for $3 per IP per month directly in the control panel." Reasons to want one: a separate sending IP for mail, or a client who needs a dedicated address.
• Reselling. WHM's reseller functions let you hand a client their own WHM login limited to their accounts; cPanel's create-account documentation covers the reseller privilege model. Pro or Premier licences are the tiers built for it.

11. When cPanel is the wrong panel for this server

The licence is the deciding number. cPanel earns it when you host other people's accounts, sell hosting, or want the largest ecosystem of documentation and third-party tooling. For one owner with a handful of their own sites, two of InterServer's other paths cost less:

• Webuzo. InterServer's Webuzo page describes it as "a single-user control panel" with one-click applications, domain tools, email, databases, FTP and SSH controls, and says "Webuzo is included with InterServer Webuzo VPS orders, so there is no separate control panel license cost". One owner, no client logins, $3 a slice and nothing else.
• DirectAdmin. Named in InterServer's FAQ: "We offer cPanel and DirectAdmin control panels on Linux VPS." A multi-account panel with a lower licence price than cPanel; the control panel comparison covers it.

InterServer's pages are not fully consistent on the panel list (the FAQ names cPanel and DirectAdmin for Linux, the OS page names those two plus Webuzo and Plesk, and the FAQ says no panels for Windows while the Windows page offers Plesk), so the order form is the current answer for any panel other than cPanel. For cPanel, the path on this page is the one the product page describes. If that is your server, order two slices with the AlmaLinux template and the cPanel option, log in on port 2087, and work down sections 4 to 8 in order.