To install Plesk on Ubuntu, start with a clean supported Ubuntu server, configure a valid hostname and DNS record, download the official Plesk Installer over HTTPS, install the latest generally available Plesk release, and complete the first login on port 8443.
| Stage | Requirement | Check |
|---|---|---|
| Operating system | Fresh 64-bit Ubuntu 24.04 LTS is recommended; Ubuntu 22.04 is supported. | cat /etc/os-release |
| Hostname | A fully qualified hostname such as panel.example.com that resolves to the server. |
hostname -f and getent hosts panel.example.com |
| Network | A stable public IP and outbound HTTPS access to Plesk repositories. | curl -I https://autoinstall.plesk.com/ |
| Administration | Root access or an account with unrestricted sudo access. | sudo -v |
| Panel access | TCP 8443 allowed only from trusted administrator addresses when possible. | sudo ss -ltnp | grep ':8443 ' after installation |
Plesk installation prerequisites
Use a fresh server whenever possible. Installing Plesk on a machine that already runs a manually configured web, mail or database stack can create package and port conflicts. Take a provider snapshot before installation so the server can be restored if the deployment fails.
Confirm the Ubuntu release and architecture:
cat /etc/os-release
uname -mFor a new deployment, use Ubuntu 24.04 LTS on x86-64 unless a required Plesk component has a documented limitation. Plesk supports Ubuntu 24.04 starting with Obsidian 18.0.61. Check the current official system-requirements page immediately before installing because supported operating systems and component limitations can change.
Step 1: Prepare the Ubuntu server
Set a fully qualified hostname. Replace the example with a hostname you control:
sudo hostnamectl set-hostname panel.example.com
hostname -fCreate an A record for the hostname pointing to the server’s public IPv4 address. If IPv6 is enabled, add a correct AAAA record as well. Forward and reverse DNS should be planned before hosting mail because mismatched DNS can damage deliverability.
Install current Ubuntu updates and reboot if the kernel or core libraries were upgraded:
sudo apt update
sudo apt full-upgrade -y
sudo rebootAfter reconnecting, check free disk space and memory:
df -h /
free -hThe exact capacity required depends on the services, websites, mailboxes, backups and logs you will host. Use the current Plesk requirements rather than treating an old minimum as a production recommendation.
Step 2: Download and run the official Plesk Installer
Download the installer directly from Plesk using HTTPS:
cd /root
wget https://autoinstall.plesk.com/plesk-installer
chmod +x plesk-installerFor an interactive installation, run:
sudo ./plesk-installerThe installer lets you choose the current release and a Recommended, Full or Custom component set. The Recommended set is appropriate for most first installations. Install only the services you will operate; every unused network service adds maintenance work and attack surface.
To install the latest generally available Plesk release with its recommended components without walking through the menus, use:
sudo ./plesk-installer install pleskDo not download old copies of the installer from third-party websites. The official installer selects packages compatible with the detected operating system and Plesk release.
Step 3: Check the installation
When installation finishes, inspect the panel service and installed version:
sudo systemctl status sw-cp-server --no-pager
sudo plesk versionConfirm that the secure panel port is listening:
sudo ss -ltnp | grep ':8443 'If UFW is enabled, permit the services you intentionally use. For initial administration, allow the secure panel port from your own public IP instead of the whole internet:
sudo ufw allow from 203.0.113.25 to any port 8443 proto tcp
sudo ufw status numberedReplace 203.0.113.25 with the administrator’s real public IP. Websites normally also need TCP 80 and 443. Mail, DNS and FTP require additional ports only if those services are enabled. Apply equivalent restrictions in the hosting provider’s cloud firewall or security group.
Step 4: Log in to Plesk securely
Create a temporary authenticated login URL from the server:
sudo plesk loginAlternatively, open the secure panel address:
https://panel.example.com:8443Complete the administrator profile, accept the licence terms and install a valid licence. Use the HTTPS hostname instead of the old unencrypted port 8880. A temporary certificate warning can appear before the hostname certificate is configured; verify that you are connecting to the correct server rather than ignoring warnings on an unknown address.
Step 5: Secure Plesk after installation
- Install a trusted certificate for the Plesk hostname.
- Keep automatic Plesk updates enabled and install Ubuntu security updates.
- Restrict panel and SSH access to trusted networks where practical.
- Use a separate Plesk administrator password and enable multi-factor authentication.
- Configure remote backups and test a restore before hosting production data.
- Review installed components and remove services you do not operate.
- Configure monitoring for disk space, certificates, services and backup failures.
Do not expose the server’s root password to ordinary Plesk users. Create subscriptions, customers and additional administrators with only the access each person requires.
Common Plesk installation problems
The installer reports an unsupported operating system
Confirm the Ubuntu version and architecture against Plesk’s current system requirements. Do not force installation on an unsupported release. Rebuild or migrate to a supported Ubuntu version.
The installer cannot download packages
Check DNS resolution, system time, outbound HTTPS access, proxy settings and available disk space:
getent hosts autoinstall.plesk.com
timedatectl status
curl -I https://autoinstall.plesk.com/
df -hPort 8443 does not open
Check sw-cp-server, the local firewall and the provider firewall:
sudo systemctl status sw-cp-server --no-pager
sudo ss -ltnp | grep ':8443 '
sudo ufw status numberedThe panel hostname does not resolve
Verify the public DNS record and allow time for DNS caches to update. The hostname must point to this server before a publicly trusted certificate can be issued reliably.
Installation stops after detecting existing services
Save the installer log and review the reported conflict. On a new deployment, rebuilding a clean server is normally safer than forcing Plesk over a manually assembled hosting stack.
Frequently asked questions
Does Plesk support Ubuntu 24.04?
Yes. Plesk supports Ubuntu 24.04 LTS starting with Plesk Obsidian 18.0.61 and currently lists it as the recommended Ubuntu release. Review the official limitations before choosing optional components.
Can I still install Plesk on Ubuntu 20.04?
Plesk lists Ubuntu 20.04 under its Extended Lifecycle Support programme. For a new server, choose Ubuntu 24.04 or another currently supported operating system instead of beginning on an ageing platform.
Which port opens the Plesk panel?
The secure administrator interface normally uses TCP 8443. Restrict it to trusted administrator addresses when possible and use a valid certificate for the panel hostname.
Official references
- Plesk Obsidian system requirements
- Plesk support for Ubuntu 24.04 LTS
- Plesk deployment quick start
- Installing Plesk for Linux in unattended mode
The installation itself is straightforward, but a dependable hosting server also needs correct DNS, narrow firewall rules, updates, monitoring and tested backups. Finish those controls before moving production websites or mailboxes to the new panel.
Comments