Install Plesk on a VPS or Dedicated Server
Install Plesk Obsidian on your own Debian or Ubuntu VPS or dedicated server: prerequisites, license, ports, initial setup, security, updates and backup.
On this page
Your values
Enter them once and the commands in this guide update.
This guide explains how to install Plesk Obsidian on a VPS or dedicated server that you administer yourself, then how to choose a license, complete the initial setup and secure access to the panel.
By the end of the guide, Plesk answers on https://panel.your-domain.com:8443 with a valid certificate, administrator access is limited to your IP address, and you know how to update and back up the server.
This Guide Does Not Apply to Shared Hosting
Plesk is also the interface of HostMyServers web hosting, but that is a very different case:
| HostMyServers web hosting | Plesk on your VPS or dedicated server | |
|---|---|---|
| Server | Shared and administered by HostMyServers | Your own, with root access |
| Installation | Nothing to install | Up to you, with this guide |
| Plesk license | Interface provided with the plan | To be activated and paid for separately |
| Panel address | https://plesk.hostmyservers.fr or client area |
https://your-name:8443 |
| Server updates, firewall, backups | Outside your scope | Your responsibility |
If you have web hosting, do not run anything from this guide: see Log In to the Plesk Interface.
Order a Server
This guide applies to servers that you administer yourself:
Prerequisites
- A freshly installed server, with no existing site or panel, and Internet access
- SSH access as
root, or a user who can open arootshell withsudo -i - A system using
systemd, among those in the following table - A domain name whose DNS zone you manage, for the server's hostname
- At least 1 GB of RAM and 1 GB of swap, and 20 GB of disk according to Plesk. Allow more to host real sites
| System | Minimum Plesk version | Limitations reported by Plesk |
|---|---|---|
| Debian 13 | 18.0.74 | Debian version recommended by Plesk. Webalizer, the .NET Toolkit extension and Qmail are not supported |
| Debian 12 | 18.0.57 | x86-64 architecture only |
| Ubuntu 24.04 | 18.0.61 | x86-64 only, no PHP 7.3 or earlier, Mailman unavailable, MySQL 5.7 not supported |
| Ubuntu 22.04 | See the official requirements | Several limitations. The only version in this list also offered on ARM |
These lists change: check the official Plesk requirements before installing.
Choose a License
After installation, Plesk offers two options:
- Trial: a full 14-day license, limited to 3 domains.
- Paid license: activated with a code. Plesk offers it in Web Admin, Web Pro and Web Host editions, which differ in their features and limits.
Compare the editions on the Plesk website. For a license ordered with a HostMyServers VPS, ask support from your client area.
Ports Used
| Port | Service | Recommendation |
|---|---|---|
| 22/tcp | SSH, or your custom port | Open, ideally limited to your addresses |
| 80/tcp | Websites and Let's Encrypt validation | Open |
| 443/tcp and 443/udp | Websites over HTTPS | Open |
| 8443/tcp and 8443/udp | Plesk panel over HTTPS | Limit to YOUR_IP |
| 8880/tcp | Plesk panel over HTTP | Keep closed |
| 8447/tcp | Plesk Installer and updates interface | Limit to YOUR_IP, if needed |
| 25, 465/tcp | Sending email | If the server handles mail |
| 110, 995, 143, 993/tcp | POP3 and IMAP | If the server handles mail |
| 53/tcp and 53/udp | DNS | If Plesk hosts your DNS zones |
| 21/tcp | FTP | If needed. Prefer SFTP |
| 3306, 5432/tcp | MySQL/MariaDB and PostgreSQL | Keep closed, unless you have a specific need |
Open only the ports of the services you actually use. If you use your instance's built-in firewall, also apply these rules from your client area.
Step 1: Prepare the Hostname
Choose a fully qualified name, for example panel.your-domain.com, and create an A record pointing to YOUR_SERVER_IP. If your domain is managed at HostMyServers, follow the guide Create an A record.
This name must resolve before installation. Plesk uses it to obtain a Let's Encrypt certificate automatically. Otherwise, it generates a temporary name, and you will then have to request the certificate for the real name yourself.
Log in as root, then configure and check the name:
sudo -i
apt update
apt install -y bind9-dnsutils wget
hostnamectl set-hostname panel.your-domain.com
hostname -f
dig +short A panel.your-domain.comhostname -f must display the full name, and dig your server's address. Avoid a fully numeric name: it can make the installation fail.
Step 2: Prepare the System
Update the system and check the available memory:
apt upgrade -y
free -h
df -h /On Debian only, Plesk's requirements call for disabling AppArmor before installation:
systemctl disable --now apparmor
systemctl is-enabled apparmor
rebootThe second command must display disabled. Log back in as root after the reboot.
Step 3: Set the Firewall for Installation
Check whether UFW is active:
ufw status verboseIf it is active, add these rules and keep the one for your SSH port:
ufw allow 80/tcp
ufw allow 443/tcp
ufw allow 443/udp
ufw allow from YOUR_IP to any port 8443 proto tcp
ufw allow from YOUR_IP to any port 8447 proto tcpIf it is inactive, do not enable it for this: you will enable Plesk's firewall in step 6. The panel is then reachable during installation, but it requires the root password or a one-time login link.
Step 4: Install Plesk
Download the official installer, then list the available versions:
cd /root
wget https://autoinstall.plesk.com/plesk-installer
chmod +x plesk-installer
./plesk-installer list-allThen install a specific version with the recommended components. 18.0.82 is the latest version at the time of writing, in November 2026: use the most recent identifier shown by the previous command.
./plesk-installer install PLESK_18_0_82 --preset RecommendedInstallation takes about 15 minutes depending on the server and the connection. Keep the SSH session open. You can follow the details from a second session:
tail -f /var/log/plesk/install/autoinstaller3.logThen check the installation:
plesk version
plesk repair installation -nThe -n option checks without changing anything.
Step 5: Complete the Initial Setup
Generate a one-time login link. It grants administrator access: do not share it.
plesk loginOpen the link in your browser, preferably the one containing the hostname, then:
- Enter the email address and a strong password for the administrator account. Use a password different from the
rootone. - Choose the trial license, or enter your activation code.
- Accept the license agreement, then click Enter Plesk.
Menu names are given in English and may be translated depending on your interface language. Later logins use https://panel.your-domain.com:8443, with the admin user.
You can also activate or check a license from the command line, replacing the example code:
plesk bin license -i AB1C23-4DEF56-7GHI89-JK1L23-MNP456
plesk bin license -c
echo $?The last command prints 0 if the license is valid.
Step 6: Secure the Panel
Check the Certificate
Plesk secures itself automatically with Let's Encrypt when the hostname resolves. Check the certificate from your computer:
echo | openssl s_client -connect panel.your-domain.com:8443 -servername panel.your-domain.com 2>/dev/null | openssl x509 -noout -subject -issuer -datesIf it is not valid, install the Let's Encrypt extension if needed, open Tools & Settings, then SSL/TLS Certificates, and click + Let's Encrypt.
Limit Administrator Access to Your Address
- Open Tools & Settings, then IP Access Restriction Management.
- Click Add Network and enter
YOUR_IP. - Click Settings, choose Denied from the networks that are not listed, then confirm.
Add your address before changing the policy. This restriction applies to the administrator: it does not block resellers, customers or SSH. If your address changes often, reserve access for a private network instead, using WireGuard or Tailscale.
Enable the Plesk Firewall
Plesk documents its Firewall extension as its firewall management tool. It manages iptables, and Plesk advises against using it with firewalld, because the two tools can conflict. Plesk does not document the UFW case: to be safe, keep only one of them.
- Keep an SSH session open for the whole operation.
- If UFW is active, disable it with
ufw disable. - Open Tools & Settings, then Firewall. Install the extension if it is missing.
- Enable Firewall protection.
- If SSH does not listen on port 22, first add a rule to allow your port.
- Limit the admin interface rule to
YOUR_IP, and close unused services. - Click Apply Changes, then Apply.
- From another terminal, check that SSH and the panel still respond before closing your session.
Docker containers running on this server are not subject to these rules: their published ports stay open. For Docker, see Configure the UFW Firewall.
Check Fail2Ban
Open Tools & Settings, then IP Address Banning (Fail2Ban). Check that Enable intrusion detection is ticked and that the jails, including plesk-panel and ssh, are active. Add your address to Trusted IP Addresses so you don't ban yourself.
Check the Result
On the server:
plesk version
plesk bin license -c && echo "License valid"
ss -ltnp | grep -E ':(80|443|8443|8880) 'From your computer:
curl -I https://panel.your-domain.com:8443This command must get an HTTP response, with no certificate error. From another IP address, for example a mobile hotspot, port 8443 must not respond, or the administrator login must be refused.
Update Plesk
By default, Plesk installs its updates automatically. This setting, and those for third-party components, are in Tools & Settings, Update Settings. Choosing a version at installation therefore does not block later updates.
To run updates manually:
plesk installer --select-release-latest --upgrade-installed-componentsSystem packages are managed in Tools & Settings, System Updates. Make a backup before any major version change, then follow the official upgrade procedure.
Back Up and Restore
From the interface, open Tools & Settings, then Backup Manager:
- Schedule schedules backups.
- Remote Storage Settings configures remote storage. Keep your backups there, so a server failure does not take them with it.
From the command line, this example creates a full backup in a single file. First check the available disk space:
plesk bin pleskbackup --server -output-file /root/plesk-$(date +%F).tar
chmod 600 /root/plesk-$(date +%F).tarTo check and then restore this file, replacing YYYY-MM-DD with its date:
plesk bin pleskrestore --check-backup /root/plesk-YYYY-MM-DD.tar
plesk bin pleskrestore --restore /root/plesk-YYYY-MM-DD.tar -level serverThe license key is not restored by default: add -license if needed. If the backup is password-protected, provide the password with -backup-password.
Troubleshooting
These commands give a first diagnosis:
plesk repair installation -n
plesk log panel.log
plesk log error_logERR_CONNECTION_TIMED_OUT on Port 8443
The port is filtered. Check UFW or the Plesk firewall, your instance's firewall and your current IP address. On the server, ss -ltnp | grep 8443 must show the service listening. If the port remains unreachable even though everything is correct, contact support from your client area.
ERR_CONNECTION_TIMED_OUT on the Updates Page
This page uses port 8447. Allow it from your address, or route the installer through the panel port:
plesk bin settings --set installerProxyMode=trueYou Lost the Administrator Password
Generate a new login link with plesk login, then change the password from your profile.
Access for administrator from address ... is restricted
Your address is no longer allowed. From SSH, as root, back up the Plesk database and remove the restrictions, then recreate them with the right address:
plesk db dump psa > /root/psa-backup.sql
plesk db "delete from cp_access"
plesk db "update misc set val='allow' where param='access_policy'"
service psa restartYou No Longer Have SSH Access After Enabling the Firewall
Open the VNC console from your client area, or contact support for a dedicated server, then fix the SSH rule in the firewall.
valid_hostname: numeric hostname or Hostname is not valid
The hostname is not a valid fully qualified name. Fix it with a name that contains letters and dots:
plesk bin server_pref --update -hostname panel.your-domain.comBefore installing Plesk, use hostnamectl set-hostname instead.
Plesk installation doesn't support 'Debian Backports...'
The installer rejects the Backports repository. Locate it, comment out the relevant lines, then restart the installation:
grep -rn backports /etc/apt/sources.list /etc/apt/sources.list.d/There are no products for your operating system
Your system or its architecture is not supported by this version. Compare the output of cat /etc/os-release and uname -m with the official requirements.
the following packages have unmet dependencies
APT is in an inconsistent state, often because of a third-party repository. Disable the repositories you added, check that apt update succeeds, then restart the installation.
Could not resolve host: ext.plesk.com or autoinstall.plesk.com
The server cannot resolve this name or reach the Internet. Test with dig +short autoinstall.plesk.com, then check /etc/resolv.conf and your outbound firewall rules.