How to Install Plesk Obsidian on Ubuntu 22.04 VPS: Enterprise Hosting Control Panel

Plesk Obsidian is the world's most widely deployed commercial hosting control panel, running more than 380,000 servers and powering over 11 million domains worldwide. This guide walks you through installing Plesk Obsidian on an Ubuntu 22.04 LTS VPS, from the one-click installer to creating your first domain with a Let's Encrypt certificate, WordPress site, mailbox, and scheduled off-site backups.

Skip the setup? Deploy a Plesk-ready VPS in a single click with our CloudCore Professional plan. Launch a hosting-ready VPS now and have your control panel online in under five minutes.

Table of Contents

What is Plesk Obsidian?

Plesk Obsidian is a commercial web hosting and server management control panel developed by WebPros International. It provides a unified graphical interface for creating domains, managing DNS, deploying websites, configuring web servers (Apache and Nginx), handling mail services, scheduling backups, and securing servers. Where a plain Linux VPS requires you to edit config files over SSH, Plesk reduces the same operations to a few clicks in a modern browser-based UI.

Plesk Obsidian is the direct competitor to cPanel/WHM, but with several structural differences. Plesk is multi-platform — it runs on Ubuntu, Debian, AlmaLinux, Rocky Linux, CloudLinux, and Windows Server, whereas cPanel only supports RHEL-family Linux. Plesk's interface is widely regarded as cleaner and more modern, with a single-pane dashboard that exposes both a Service Provider view (for hosts reselling to multiple customers) and a Power User view (a flattened UI for single-site owners). And Plesk ships with a first-class WordPress Toolkit that does staging, cloning, mass updates, and security hardening across every WordPress install on the server — a feature cPanel only started matching much later.

Common use cases for Plesk include freelance web developers managing 5–50 client sites from one server, digital agencies who need staging and cloning for WordPress builds, small hosting companies reselling email and web hosting, SaaS operators self-hosting their own web properties, and in-house IT teams consolidating corporate websites, intranets, and mail onto a single managed stack. Plesk's extension catalog — covering Git deployment, Docker, Node.js, Ruby, Let's Encrypt, ImunifyAV, Cloudflare, Acronis Backup, SEO Toolkit, and many others — lets you extend a base install into a full DevOps platform without leaving the panel.

Why Self-Host Plesk on Your Own VPS?

Running Plesk on your own VPS instead of buying shared hosting or a managed Plesk plan from a reseller gives you several concrete advantages:

• Full root access — You own the server. Install any system package, tune kernel parameters, run custom cron jobs, and attach block storage without filing a ticket.
• Flat-rate, predictable cost — A VPS plus a Plesk license is a fixed monthly cost regardless of how many domains, mailboxes, or databases you create. No per-site overage fees.
• Better performance than shared hosting — A dedicated 6 vCPU / 12 GB RAM VPS will outperform almost any shared hosting account, which typically throttles CPU and I/O per tenant.
• Complete data control — Your sites, databases, and mail are on hardware you rent directly. No mystery co-tenants, no opaque reseller chain.
• Full extension freedom — Install any Plesk extension, any PHP version (from 5.6 through 8.3), any web server stack. Shared Plesk providers often restrict extensions and PHP modules.
• Easy vertical scaling — Upgrade the VPS from 4 GB to 16 GB RAM in minutes when traffic grows. Shared plans require migrating to a new provider tier.
• GDPR and data-locality compliance — Pick your data center (EU, UK, Canada, US) to satisfy data residency requirements, and keep backup destinations you control.

Plesk vs. Shared Hosting vs. Plain VPS

Licensing Options

Plesk Obsidian is commercial software and requires a paid license to use beyond the trial. Three primary editions are available:

Plesk offers a 14-day free trial that unlocks all Web Host features so you can evaluate before purchasing. You can also buy licenses from Plesk directly, from Plesk partners (often bundled with VPS plans), or monthly through the Plesk Partner Program. Licenses are tied to the server IP address; if you migrate to a new server, you deactivate the license on the old one and re-activate on the new one.

Prerequisites

Before you begin, make sure you have:

• A VPS running a fresh Ubuntu 22.04 LTS with root or sudo access (Plesk is strict about clean installs — existing web servers, database servers, or mail servers on the host will cause installer failures)
• SSH access to your server (PuTTY on Windows, or the built-in terminal on macOS/Linux)
• At least 2 GB of RAM (4 GB+ strongly recommended for running WordPress Toolkit and the mail stack comfortably)
• At least 20 GB of free disk space (40 GB+ recommended once you factor in mail, databases, and a few weeks of backups)
• A public IPv4 address with ports 22 (SSH), 80 (HTTP), 443 (HTTPS), 8443 (Plesk panel), 8447 (Plesk updates), 25/465/587 (SMTP), and 143/993 (IMAP) reachable
• A domain name pointed at your server IP (optional for the initial install, required before issuing Let's Encrypt certificates)

Recommended Plan: CloudCore Professional

For hosting 10-30 domains including WordPress sites, mailboxes, and a few databases, we recommend the CloudCore Professional plan:

- 6 vCPU cores

- 12 GB RAM

- 100 GB NVMe SSD

- Unmetered bandwidth

- EUR 19.99/month

This comfortably handles a Plesk install plus 20-30 active WordPress sites, a full mail stack, and daily incremental backups. For single-site or development use, our entry VPS tier is sufficient; for busy agencies hosting 50+ sites, consider scaling up the RAM tier.

Connect to your server via SSH to get started:

ssh root@your-server-ip

Step 1: Update System Packages

Start by updating your package index and upgrading installed packages. Plesk's installer is strict about dependency state — out-of-date packages are the single most common cause of install failures.

sudo apt update && sudo apt upgrade -y

Expected output (abbreviated):

Hit:1 http://archive.ubuntu.com/ubuntu jammy InRelease
Hit:2 http://archive.ubuntu.com/ubuntu jammy-updates InRelease
Reading package lists... Done
Building dependency tree... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

If the kernel was updated during the upgrade, reboot before continuing:

sudo reboot

Set a fully qualified hostname — Plesk requires a valid FQDN on first boot:

sudo hostnamectl set-hostname panel.yourdomain.com

Reconnect via SSH after the reboot and move on to the installer.

Step 2: Run the Plesk One-Click Installer

Plesk provides an official one-click installer that downloads the correct package set for your Linux distribution, runs all dependency installs, configures Apache + Nginx + Postfix + Dovecot + MariaDB + PHP, sets up systemd units, and launches the panel on port 8443 — all with a single command.

Run the installer:

sh <(curl https://autoinstall.plesk.com/one-click-installer)

Expected output (abbreviated):

Welcome to the Plesk one-click installer
Fetching installer archive...
Running installer...
Starting installation of Plesk Obsidian...
Detected Ubuntu 22.04
Installing required packages: apache2 nginx mariadb-server postfix dovecot-core...
Configuring Apache...
Configuring Nginx...
Configuring MariaDB...
Configuring Postfix...
Configuring Dovecot...
Installing Plesk panel...
Installing WordPress Toolkit...
Installing Plesk Firewall extension...
Installing Let's Encrypt extension...
Finalizing installation...
*
Plesk Obsidian has been successfully installed on your server.
Access the panel at: https://your-server-ip:8443
*

The installer typically takes 10-15 minutes to complete depending on your server's bandwidth. During this time, it will:

Do not interrupt the installer. If it fails midway, Plesk is extremely difficult to clean up — you will usually want to redeploy the VPS from scratch rather than attempt to resume.

Step 3: Log In for the First Time

Once the installer completes, Plesk listens on port 8443 over HTTPS with a self-signed certificate. Browse to:

https://your-server-ip:8443

Your browser will warn about the self-signed certificate — accept and continue (you will replace this with a real Let's Encrypt cert in Step 8).

You will see the Plesk login screen. There are two ways to authenticate on first login:

Option A: One-time login link via CLI

The safest way to get a first-time login without having to set a password blind is to generate a one-time login link from SSH:

sudo plesk login

Expected output:

https://your-server-ip:8443/login?secret=abc123XYZ...

Copy that URL into your browser — you will be logged in directly as admin.

Option B: Log in with the generated admin password

During installation, Plesk generates an initial admin password stored in a protected file. Retrieve it with:

sudo plesk bin admin --show-password

Log in with the username admin and the displayed password. Plesk will immediately prompt you to change the password on first login.

On first successful login, Plesk launches a setup wizard:

Click Enter Plesk and the main dashboard loads.

Step 4: Activate Your License

On a fresh install, Plesk runs in trial mode for 14 days with all features unlocked. To continue beyond the trial, install a license key.

In the Plesk UI:

Plesk contacts the WebPros license server to activate. Within a few seconds, the License Management page will show:

Status: Active
Edition: Plesk Web Pro Edition
Domain limit: 30
Expires: 2027-04-16

If the server cannot reach the license server, activation fails — see the Troubleshooting section below for the relevant firewall ports.

You can also activate a license from SSH:

sudo plesk bin license --install YOUR-ACTIVATION-CODE

Step 5: Create Your First Domain

With the panel live and licensed, create your first hosted domain.

In the Plesk UI:

Plesk creates:

• A Linux system user under /var/www/vhosts/example.com/
• An Apache virtual host at /etc/apache2/plesk.conf.d/vhosts/example.com.conf
• An Nginx reverse proxy vhost in front of Apache
• A DNS zone on the local BIND server
• An example.com mail domain (with mail disabled by default until you add a mailbox)
• Default index.html placeholder in the docroot

• Apache & nginx Settings — enable PHP, Python, or Node.js; configure additional directives; turn on nginx caching
• PHP Settings — switch between PHP 7.4, 8.0, 8.1, 8.2, 8.3 (per-domain); adjust memory_limit, max_execution_time, upload_max_filesize
• DNS Settings — edit A, AAAA, MX, TXT, CNAME records directly
• Web Application Firewall (ModSecurity) — enable OWASP, Atomic, or Comodo rule sets
• Hotlink Protection, IP Address Access Restrictions, Custom Error Pages

Step 6: Install WordPress with WordPress Toolkit

Plesk's WordPress Toolkit is a premium extension bundled with Web Pro and Web Host editions that handles every aspect of WordPress lifecycle management from one screen.

In the Plesk UI:

Plesk downloads the latest WordPress release, creates a MySQL database and user, configures wp-config.php, installs WordPress, and logs you in automatically. The entire process takes about 30 seconds.

Once installed, the WordPress Toolkit card for your site exposes:

• Log in — auto-login to /wp-admin without typing credentials
• Files — inline file manager
• Database — phpMyAdmin shortcut
• Clone — create an exact copy of the site at a new domain or subdomain (perfect for a staging environment)
• Copy Data — push changes from staging back to production (with selective database-table sync)
• Updates — one-click update of WordPress core, all themes, all plugins across every WP install on the server
• Security — run 15+ hardening checks (disable file editing in wp-admin, block directory listing, block access to sensitive files, etc.) with one-click apply
• Labs / Smart Updates — test updates in a sandboxed clone with visual regression before applying to production

Create a Staging Environment

To clone your production site to a staging subdomain:

Plesk creates the subdomain, copies all files, clones the database, rewrites URLs, and issues a Let's Encrypt cert for the staging host (if DNS is configured). You now have an isolated copy you can break without touching production. When changes are ready, click Copy Data to push the staging database and/or files back to production.

Step 7: Enable Mail Service

Plesk bundles a full mail stack: Postfix (SMTP), Dovecot (IMAP/POP3), SpamAssassin (filtering), and Roundcube (webmail). Mail is created per-domain.

The mailbox is live immediately. Users can access it at:

• Webmail: https://webmail.example.com (Roundcube, auto-configured)
• IMAP: mail.example.com:993 (SSL)
• SMTP: mail.example.com:465 (SSL) or :587 (STARTTLS)

DNS Records for Deliverability

For mail to deliver reliably to Gmail, Outlook, and other big providers, add these DNS records for your domain (Plesk auto-creates some of them in its DNS zone, but if you use external DNS, set them there):

• MX: example.com. IN MX 10 mail.example.com.
• A: mail.example.com. IN A your-server-ip
• SPF (TXT): "v=spf1 mx a -all"
• DKIM: enable in Plesk via Mail -> Mail Settings -> tick Use DKIM spam protection system. Plesk shows the TXT record to add.
• DMARC (TXT): _dmarc.example.com. IN TXT "v=DMARC1; p=quarantine; rua=mailto:[email protected]"
• PTR (reverse DNS): point your server IP to mail.example.com via your VPS provider's control panel

Step 8: Issue a Let's Encrypt Certificate

Plesk ships with the Let's Encrypt extension pre-installed. Issuing a certificate for a domain takes one click once DNS is pointed at your server.

Plesk performs the ACME HTTP-01 challenge and installs the certificate on Apache + Nginx + Dovecot + Postfix. Renewal is automatic 30 days before expiry.

To secure the Plesk panel itself (the :8443 interface) with a Let's Encrypt cert:

Your panel URL becomes https://panel.yourdomain.com:8443 with a trusted certificate — no more browser warnings.

Step 9: Install the Plesk Firewall Extension

The Plesk Firewall extension wraps iptables in a friendly UI so you do not have to hand-write rules.

Recommended additional rules:

• SSH (port 22): restrict to your office/home IP range if possible
• Plesk Panel (port 8443): same, or leave open if you manage from varied locations
• Block ICMP (optional): reduces drive-by scans but breaks ping diagnostics

Step 10: Configure the Backup Manager

Plesk's Backup Manager creates full or incremental backups of your entire server state — sites, databases, mail, panel configuration — and ships them to local or remote storage.

Now schedule a backup:

The first full backup runs on the next scheduled window. To trigger an immediate backup, click Back Up on the Backup Manager page and leave defaults.

Restoration is equally GUI-driven: click any backup archive and pick which domains, databases, or mail accounts to restore, down to individual file level.

Post-Install: Explore the Plesk UI

Now that the stack is live, spend a few minutes getting familiar with the key parts of the Plesk interface:

• Home dashboard — a server health overview: CPU, RAM, disk, network traffic, number of domains/mailboxes/databases. Notifications for pending updates, expiring certificates, failed backups.
• Websites & Domains — the per-domain operations hub. Everything tied to a single site lives under its card.
• WordPress — centralised view across all WP installs on the server. Bulk-update cores, bulk-apply security hardening, see which plugins are outdated across every site.
• Mail — list of all mail domains and mailboxes; configure server-wide mail settings (DKIM, spam filter, greylisting).
• Extensions — the catalog. Browse and install Git deployment, Docker, Node.js, ImunifyAV, SEO Toolkit, Cloudflare, monitoring agents, and hundreds more.
• Tools & Settings — every server-wide setting lives here: PHP versions, Apache/nginx tuning, backup manager, firewall, IP banning, scheduled tasks, license management.
• Server Health Monitor (if installed) — historical CPU/RAM/disk graphs with alerting.

Keeping Plesk Updated

Plesk releases micro-updates (bug fixes, security patches) every 1-2 weeks and major updates (new versions of Obsidian) once or twice a year. Staying current is important for security.

Configure auto-updates:

To apply updates manually through the UI, go to Tools & Settings -> Updates. The page shows pending Plesk updates and available component upgrades (PHP, MariaDB, etc.). Review and click Continue to apply.

From SSH, the same update runs with:

sudo plesk installer --select-release-current
sudo plesk installer update

Always take a fresh backup before major version upgrades. Plesk's update process is reliable, but Murphy's law applies to control panels.

Troubleshooting

Viewing Logs

The most useful debugging logs on a Plesk server:

# Plesk panel errors
sudo tail -f /var/log/plesk/panel.log
Plesk installer (during install/upgrade)
sudo tail -f /var/log/plesk/install/autoinstaller3.log
Apache errors
sudo tail -f /var/log/apache2/error.log
Nginx errors
sudo tail -f /var/log/nginx/error.log
Mail log (Postfix + Dovecot)
sudo tail -f /var/log/mail.log

FAQ

Is Plesk free?

No. Plesk is commercial software. Licenses range from ~USD 12/mo for the Web Admin edition (10 domains) to ~USD 36/mo for Web Host (unlimited domains). A 14-day free trial is available to evaluate the full feature set. If you need a free alternative, look at open-source panels like Hestia Control Panel, CyberPanel, or aaPanel — but Plesk's polish, WordPress Toolkit, and commercial support are unmatched at this price point.

How does Plesk compare to cPanel?

Both are mature commercial panels with strong feature overlap. The practical differences: Plesk runs on Ubuntu/Debian in addition to RHEL-family Linux, while cPanel is RHEL-only. Plesk's UI is generally considered more modern — one unified dashboard vs cPanel's split between cPanel (end-user) and WHM (admin). Plesk's WordPress Toolkit is widely regarded as the best WordPress management tool in any control panel. cPanel has a longer market presence, especially in US hosting resellers, which means more third-party documentation and forum answers. Pricing is broadly similar. If you already know one, there's rarely a strong technical reason to switch.

Can I install Plesk on an existing Ubuntu server that already has Apache or MySQL?

Officially, no. Plesk expects a fresh, unmodified distribution and will refuse to install over an existing LAMP stack. In practice, you will save hours of pain by redeploying a clean Ubuntu 22.04 VPS and running the installer against that. If you must migrate from an existing server, install Plesk on a new server and use the Plesk migration tool (Tools & Settings -> Migration & Transfer Manager) to import the old sites.

What ports does Plesk require open?

Inbound: 22 (SSH), 80 (HTTP), 443 (HTTPS), 8443 (Plesk panel), 8447 (Plesk updates), 25/465/587 (SMTP), 143/993 (IMAP), 110/995 (POP3), 53 (DNS, if your server is authoritative). Outbound: 443 (to autoinstall.plesk.com, ka.plesk.com, Let's Encrypt ACME, extension catalog) and 5224 (license activation). Most managed VPS providers open all these by default; if yours doesn't, open a ticket or use the provider's firewall UI.

Can I run Plesk behind Cloudflare?

Yes, and Plesk ships with a Cloudflare extension that automates the integration. After installing the extension and providing your Cloudflare API token, you can proxy any domain through Cloudflare with one click. The extension handles DNS record sync and cache purging from inside the Plesk UI. Full HTTPS works as long as you set Cloudflare's SSL mode to "Full (Strict)" and have a valid Let's Encrypt cert on the origin — which Plesk issues for you in Step 8.

How do I migrate from WHMCS / cPanel to Plesk?

Plesk ships with a first-class Migration & Transfer Manager under Tools & Settings. It connects to a source server over SSH, enumerates domains/databases/mailboxes on cPanel, Plesk, DirectAdmin, or even plain Linux hosts, and imports them to the new Plesk server with DNS and mail intact. For WHMCS itself (the billing layer, not the hosting layer), you migrate the customer/invoice data separately into your new billing platform; the underlying web/mail/DNS data moves via the Plesk migration tool. Test with one or two low-traffic sites before cutting over DNS for everything.

Next Steps

Now that Plesk is running on your VPS, here are recommended next steps to get more out of your setup:

• Install ImunifyAV for malware scanning — ImunifyAV scans every domain for malware and reports compromised WordPress/Joomla files. Install from Extensions -> Imunify. Pairs well with WordPress Toolkit's security hardening.

• Enable Git deployment — Plesk's Git extension lets you push a GitHub/GitLab/Bitbucket repository into a domain's docroot with auto-deploy on each commit. Perfect for static sites and modern PHP frameworks. Install from Extensions -> Git.

• Set up Docker — The Docker extension exposes a GUI on top of the Docker daemon so you can run containerised apps (Nextcloud, Mattermost, custom apps) alongside traditional hosted domains. Find it in Extensions -> Docker.

• Install the SEO Toolkit — Plesk's SEO Toolkit crawls each site monthly, flags broken links, missing meta tags, slow pages, and keyword issues, and gives you a weekly email report per site. Available under Extensions -> SEO Toolkit.

• Read the official docs — The complete administrator guide is at docs.plesk.com. The "Getting Started" section covers advanced topics like server templates, service plans, reseller accounts, and API automation.

• Explore the extension catalog — Browse over 100 extensions at plesk.com/extensions. Notable picks: Acronis Backup, WP Guardian, Monitoring (Grafana), Juggernaut (caching), and Advisor.

Skip the Manual Install — Get a Plesk-Ready VPS

Our CloudCore Professional VPS is purpose-built for hosting control panels like Plesk. Deploy in 60 seconds and start creating domains immediately.

- 6 vCPU, 12 GB RAM, 100 GB NVMe SSD

- Clean Ubuntu 22.04 LTS image, ready for the Plesk one-click installer

- All required ports open by default (8443, 8447, 25, 587, 465, 143, 993)

- Reverse DNS configurable from your dashboard for reliable mail delivery

- Hourly snapshots + off-site backup targets included

Deploy Your Hosting VPS Now — Plans start at EUR 19.99/month. Plesk licenses available as an add-on at checkout.