An agency in Dubai runs 22 sites for its clients: 15 on WordPress, four Laravel applications, two APIs built on Node.js, and an old accounting system written in ASP.NET. cPanel can run the first three, but the fourth needs a Windows server, and cPanel only runs on Linux. Plesk runs on both operating systems with the same interface and concepts, and adds graphical tools for Git, Docker and Node.js. But it isn’t always the better choice. This guide explains how Plesk actually organizes hosting, which licence edition you need, which commands shorten your troubleshooting, and when cPanel remains the right call.
01How Plesk organizes hosting
Plesk builds everything on three levels: the administrator owns the server and creates for customers or for themselves, and each subscription holds one or more domains. The subscription is the unit of isolation: it has its own system user, a directory under /var/www/vhosts on Linux, and limits on disk space, domains, databases and mailboxes that come from the “service plan” it was built on. Change the plan once, and every subscription tied to it changes.
Unlike cPanel, which separates WHM for running the server from cPanel for running each account, Plesk stays one interface that changes with your role: the administrator sees the whole server, a customer sees only their subscriptions. And if you run the server for your own sites, the Power User view trims the interface to what you need, without the customer layer.
02Licence editions: what actually changes
Illevante sells Plesk licences with a server only: you need an active CoreVPS virtual server or dedicated server with Illevante, and the licence is activated automatically with the server. The three editions differ in the number of domains and in managing other people, not in the core site tools:
| Feature | Web Admin | Web Pro | Web Host |
|---|---|---|---|
| Domains | Up to 10 | Up to 30 | Unlimited |
| WP Toolkit and the Sitejet site builder | Included | Included | Included |
| Subscription and customer account management | Not included | Included | Included |
| PostgreSQL and MSSQL modules | Not included | Included | Included |
| Reseller management | Not included | Not included | Included |
| Fits | A server for your own sites | An agency giving clients their own login | Anyone selling hosting through resellers |
The working rule: Web Admin for someone who manages their own sites, Web Pro when your clients need their own login or you need PostgreSQL, and Web Host when you sell hosting. Count the domains you’ll add over the next year, not the ones you have today: upgrading between editions is possible, but planning for it is calmer than being forced into it.
03Site and developer tools
WP Toolkit
It gathers the server’s WordPress sites into one list: installation, bulk updates for core and plugins, cloning a site to a staging copy and syncing it back to live, and a check of hardening measures such as blocking xmlrpc.php and disabling the file editor. Smart Updates, which compare the site before and after an update, are part of WP Toolkit Deluxe, a separate extension.
Git
Plesk’s tool links a site to a repository on GitHub or GitLab, or to a repository on the server itself. You choose automatic deployment on every push through a webhook, or manual deployment when you decide, and add commands that run after each deployment, such as installing Composer packages or running database migrations for a Laravel app.
Docker, Node.js and Python
The extension runs containers on a Linux server from the panel, and maps a domain to a container port with a proxy rule (Docker Proxy Rules), so visitors reach the app over HTTPS without you having to open the container’s port to the world. The Node.js Toolkit extension picks the Node version and startup file and installs packages, while Phusion Passenger manages the process. Python has no tool on the level of Node.js Toolkit, and the cleanest route for a Django or FastAPI app is a Docker container behind a proxy rule. The extension list also includes Laravel Toolkit, Ruby and PHP Composer.
04Security and backups
Four layers of protection that come with Plesk or that you add to it, then the backups that save you when all of them fail:
- SSL certificates: The extension issues a certificate for every domain and renews it automatically. With the maximum lifetime of public certificates down to 200 days since March 2026, and 100 days from March 2027, manual renewal is no longer an option.
- Fail2Ban: reads login logs and bans an address that keeps failing for a period you set, through separate “jails” for the panel, SSH, mail and the web server.
- Firewall: The Plesk firewall manages the system firewall’s rules from the panel. Close every port you don’t need, and restrict SSH and the panel’s port 8443 to your team’s addresses if you can.
- Deeper layers: ModSecurity, a web application firewall, is available in Plesk, and the extensions Illevante offers include Advanced ModSecurity Rules, Imunify, BitNinja and KernelCare.
Plesk’s Backup Manager schedules full or incremental backups of the whole server or of each subscription, and stores them on the server itself, on remote storage over FTP or FTPS, or in the cloud with an extension such as Backup to Cloud Pro. A backup on the same server doesn’t protect you when that server fails, so make the primary destination somewhere else; any space that accepts FTPS will do, including Illevante’s StorX Box. Then restore a full subscription at least once before you need to.
05The Plesk commands you actually need
Almost everything in the panel has a matching command over SSH as root. These cover most day-to-day troubleshooting:
# Plesk version and operating systemplesk version# Check components and configuration without fixing anythingplesk repair all -n# Subscriptions on the serverplesk bin subscription --list# One-time login link for the admin account, handy when the password is lostplesk login# Installed extensions and their versionsplesk bin extension --list# WordPress sites managed by WP Toolkitplesk ext wp-toolkit --list
If the check reports errors, take a backup, then run the same repair command without the -n option; it asks you to confirm each fix. And when a client says they can’t reach the server, start with the Fail2Ban jails:
# Active jailsfail2ban-client status# Addresses banned in the web server jailfail2ban-client status plesk-apache# Lift the ban on an address that was banned by mistakefail2ban-client set plesk-apache unbanip 203.0.113.25
- ProblemThe Plesk panel won’t open on port 8443
- FixMake sure the port is open in the server firewall, and in the provider’s firewall if there is one, and that the panel services sw-cp-server and sw-engine are running; then run the repair check above.
- ProblemA Let’s Encrypt certificate won’t issue or won’t renew
- FixCheck that the A and AAAA records point to the server, that port 80 is open for validation, and that any CAA record allows letsencrypt.org. A wildcard certificate needs DNS validation. Then check the result with the SSL certificate check tool on Illevante’s site.
- ProblemA client suddenly can’t reach their panel or mail from the office
- FixFail2Ban has most likely banned their address after failed logins. Lift the ban, and add fixed office addresses to the trusted list in IP Address Banning settings.
06Plesk or cPanel: an honest comparison
| Criterion | Plesk | cPanel |
|---|---|---|
| Operating system | Linux and Windows, with IIS, ASP.NET and MSSQL | Linux only |
| Interface structure | One interface with roles: admin, reseller, customer | WHM for the server, cPanel for each account |
| Languages beyond PHP | Node.js, Ruby, Docker and Laravel through official extensions | Node.js and Python through Application Manager or CloudLinux, no Docker from the panel |
| Licence basis | Number of domains: 10, 30 or unlimited | Number of accounts: 5, 30, 50 or more |
| Dense shared hosting | Possible with CloudLinux and Imunify | The de facto standard among shared hosting providers |
| Site migration | Plesk Migrator imports from cPanel and other panels | Moving an account to another cPanel server is a standard procedure |
| WordPress at scale | WP Toolkit, which was born in Plesk | WP Toolkit is available too |
| Best fit | Agencies with mixed stacks, and Windows applications | Shared PHP hosting, and teams used to cPanel |
What the table says: the decisive difference isn’t the look of the interface, but the operating system you need, the non-PHP technologies you run, and how the licence is counted. The other features are close enough that moving between the two panels is a choice you make, not a necessity forced on you. We cover cPanel and its limits in detail in a separate article on this blog.
07Before you decide
Choose Plesk if one of three things applies: you need Windows for an ASP.NET app or an MSSQL database; you run Node.js apps or Docker containers alongside PHP and want to manage them from the panel; or you manage a limited number of domains for many clients who each need their own login. Otherwise cPanel remains a solid choice, especially for shared hosting.
At Illevante you can pick Plesk Obsidian as a ready-made app when ordering a CoreVPS server with Ubuntu, so the server arrives with the panel installed, and the edition you choose is activated with the server. Run the repair check on day one, and point backups to a destination off the server before you move your first site. If your application needs Windows, choose a Windows Server template and confirm with support that the Plesk licence will be activated on it before you build on it.
