How to install Plesk on a Linux VPS (AlmaLinux and Ubuntu)
Install Plesk on a fresh Linux VPS with the official one-click installer, apply your licence key and log in to the panel for the first time on port 8443.
- Beginner
- Linux VPS
- 8 min read
You install Plesk on a Linux VPS by running the official one-click installer as root on a clean server. It takes a few commands and one reboot-free script run, after which you log in to the panel on port 8443, apply your licence key and start creating sites.
This guide uses AlmaLinux and Ubuntu as examples, which are the two distributions most people pick on a Linux VPS. The commands are the same on Rocky Linux and Debian.
Before you start
- A Linux VPS with root access. Plesk supports a limited set of distributions and versions, so check the current system requirements on the Plesk website before you begin. AlmaLinux 8/9, Rocky 8/9, Ubuntu 22.04/24.04 and Debian 12 are the usual choices.
- A clean server. Plesk expects to manage its own web server, database server and mail stack. If nginx, Apache, MySQL, another control panel or a site already runs on the VPS, back it up and rebuild the server before installing.
- A hostname in fully qualified form (FQDN), for example
vps.example.com, with an A record pointing to your server IP. - A Plesk licence key. You can start with a trial key from Plesk or enter a key you purchased from them. RunRacks does not sell panel licences — buy those directly from the vendor, and check their site for current licence types.
- An SSH client. If you are new to this, see Connect to your Linux VPS with SSH.
Do not run the installer on a server that already hosts live sites or mail. The installer changes system services and can disable SELinux on RHEL-based systems, so treat it as a fresh-install operation.
Set the hostname and DNS
Plesk uses the server hostname for its own panel certificate and for mail services, so set it first.
hostnamectl set-hostname vps.example.com
hostname -fhostname -f must print the full FQDN, not a short name. On Ubuntu and Debian, add the matching entry to /etc/hosts if it is missing:
127.0.1.1 vps.example.com vpsThen create the DNS records at your registrar or DNS provider:
A vps.example.com→ your server IPAorCNAMErecords for any domains you plan to host on the panel
If you manage DNS inside Plesk later, you still need the initial record for the server hostname elsewhere.
Update the system
Bring the OS packages up to date so the installer does not fight a half-finished upgrade.
On AlmaLinux and Rocky Linux:
dnf -y updateOn Ubuntu and Debian:
apt update && apt -y upgradeCheck that nothing is already listening on the ports Plesk needs (80, 443 and 8443):
ss -tulpn | grep -E ':80|:443|:8443'No output means you are clear. If something is listed, stop and remove that service before continuing — see netstat and ss for network analysis for reading the output.
Run the Plesk one-click installer
Start a screen or tmux session first, so a dropped SSH connection does not kill the installation:
tmux new -s pleskThen download and run the installer as root:
cd /root
wget https://autoinstall.plesk.com/one-click-installer
chmod +x one-click-installer
./one-click-installerThe script downloads the Plesk packages, installs the panel, web server, PHP handlers, database server and supporting services, and then runs its own post-install configuration. Expect several minutes of scrolling output. When it finishes you will see the panel URL and the login details near the end of the log.
If your provider gives you a cloud firewall or security group, open TCP 8443 (panel), 80 and 443 (websites), and 21/22 only if you actually use them. Mail ports are only needed if you plan to host mail.
On AlmaLinux, Rocky and other RHEL-based systems the installer usually disables SELinux. If you rely on SELinux for compliance, confirm whether Plesk's current policy allows it before you install, and do not re-enable it afterwards without checking the vendor documentation.
Open the firewall
If firewalld is running, the installer normally adds the Plesk rules for you. Verify them, and add anything missing.
On AlmaLinux and Rocky:
firewall-cmd --add-service=http --permanent
firewall-cmd --add-service=https --permanent
firewall-cmd --add-port=8443/tcp --permanent
firewall-cmd --reload
firewall-cmd --list-allOn Ubuntu with UFW:
ufw allow 8443/tcp
ufw allow 80/tcp
ufw allow 443/tcp
ufw statusMore detail is in Configure firewalld on AlmaLinux and Rocky Linux and UFW vs firewalld vs nftables vs iptables.
Log in to Plesk for the first time
Open the panel in a browser:
https://vps.example.com:8443The certificate warning is expected at this stage — the panel still uses a self-signed certificate. Log in with the username root and your server root password. You can also generate a one-time login link from the shell, which avoids typing the root password into a browser:
plesk loginThe command prints a single-use URL. Treat it like a password: anyone who opens it before you do gets admin access.
On first login Plesk asks you to:
- Enter your licence key, or start a trial key from the vendor.
- Set the administrator email address and a panel password.
- Accept the end-user licence agreement.
After that you land on the dashboard. The email address matters — Plesk sends licence and update notices there.
Never share the one-time login URL, and never leave the panel exposed with the root password over plain HTTP. Keep 8443 open only to addresses that need it where possible.
Finish the initial setup
A few settings are worth doing straight away:
- Secure the panel. In Plesk, go to Tools & Settings > SSL/TLS Certificates and issue a free Let's Encrypt certificate for the server hostname so port 8443 stops showing warnings.
- Install optional components. Open Tools & Settings > Updates and Upgrades (Plesk Installer) and add what you need, such as extra PHP versions, a mail server, or a different database engine. Add components after installation rather than during it if you are unsure.
- Check automatic updates. Plesk keeps itself updated by default; confirm the schedule in Tools & Settings > Update Settings and decide whether updates may run automatically.
- Create a backup routine. Plesk has its own backup manager, but it does not replace an off-server copy. Combine it with Back up your Linux VPS with rsync, restic and cron.
If you prefer to work with a non-root admin account in the shell, create one and give it sudo access — see Create a sudo user on Ubuntu, Debian, AlmaLinux and Rocky Linux. Plesk itself keeps using root for its CLI.
Check it works
From the shell:
plesk version
systemctl status sw-engine --no-pager
ss -tulpn | grep 8443You should see the Plesk version string, an active sw-engine service, and a process listening on 8443. Plesk also ships a repair tool if a component looks wrong:
plesk repair installationThen, in the browser:
- Log in at
https://vps.example.com:8443. - Create a test domain and confirm it serves a default page over HTTP and HTTPS.
- Reboot the VPS from the dashboard and check that the panel and your test site come back without manual intervention.
If the panel loads and your test domain answers after a reboot, the installation is sound.
Troubleshooting
- Installer exits early with a hostname error → the server hostname is not a FQDN. Run
hostnamectl set-hostname vps.example.com, fix/etc/hosts, then run the installer again. - Panel URL does not load in the browser → almost always a closed port. Check the OS firewall rules and any cloud security group for TCP 8443, then confirm with
ss -tulpn | grep 8443that Plesk is listening. - Installer fails on a package conflict → another web server or control panel is installed. Plesk needs a clean server; remove the conflicting service or rebuild the VPS before retrying.
- Installation stops partway with disk or memory errors → the VPS is below Plesk's current minimums. Check the vendor's system requirements, resize the plan, and add swap if the OS needs it — see Add a swap file on a Linux VPS.
- Login page returns an error after a reboot → a Plesk service did not start. Run
plesk repair installationand checksystemctl status sw-engine. If SELinux was re-enabled after installation, disable it again or follow the vendor's guidance.
Next steps
- Work through First steps after your Linux VPS is ready to lock down the base system.
- If you plan to host mail on the same server, read Postfix and Dovecot mail server setup on a Linux VPS and confirm Plesk's mail settings match.
- Learn the panel's file manager alternatives for larger transfers in Transfer files to your Linux VPS with SCP, SFTP, WinSCP or FileZilla.
- Compare plan sizes before you install a panel, since Plesk plus a database and mail stack needs more memory than a bare server — see Linux VPS hosting.
Was this guide helpful?
Still stuck?
Ask RunRacks AI for a quick answer, or open a ticket and our team will take a look at your server.
Related guides
Control panels
CyberPanel: back up and restore a website
Create on-demand and scheduled website backups in CyberPanel, download the archives off the server, and restore a site from a backup when something breaks.
- Intermediate
- Linux VPS
- 6 min read
Control panels
Plesk Backup Manager: schedule backups and restore a site
Set up scheduled backups in Plesk Backup Manager, keep a copy off the server, and restore a single domain or subscription when something goes wrong.
- Intermediate
- Linux VPS
- 7 min read
Control panels
Postfix and Dovecot mail server setup on a Linux VPS
Install Postfix and Dovecot on a Linux VPS, configure authenticated SMTP submission and IMAP over TLS, then verify that mail is delivered into a Maildir and can be read back.
- Advanced
- Linux VPS
- 5 min read