Plesk Obsidian Installation on Linux: Step-by-Step Guide

Plesk Obsidian installation on Linux takes one command on a clean server, and the installer finishes in roughly 10 to 20 minutes depending on the components you pick. This guide covers requirements, the one-line installer, first-login configuration, adding a domain, issuing an SSL certificate, and how Plesk compares with cPanel.

Plesk Obsidian Requirements

Check these before you run anything. Plesk expects to own the server, so start from a fresh OS install.

Other things to confirm:

• Clean system. Do not install on a server that already runs Apache, nginx, or Postfix configs you care about. Plesk will rewrite them.
• Hostname. Set a real FQDN such as panel.example.com with an A record pointing to the server.
• SELinux and firewall. Leave them at the OS defaults. Plesk handles its own rules.
• Virtualization. Plesk runs well on a KVM or VMware-based VDS. Make sure you have full root and a real kernel, not a restricted container. On a BGP-enabled VDS from Nixcon Group you get a full virtual dedicated server with root access, which suits this kind of install.

Prepare the Server

Update the system and set the hostname first.

# Debian / Ubuntu
apt update && apt -y upgrade

# AlmaLinux / Rocky / RHEL
dnf -y upgrade

# Set the hostname
hostnamectl set-hostname panel.example.com
hostname -f

Confirm that DNS resolves and that the ports below are reachable from the internet.

Reboot if the kernel was updated, then continue.

One-Command Installation

Plesk provides a one-click installer script. Run it as root:

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

The script downloads the Plesk installer, installs the latest stable Obsidian release with the recommended preset, and starts the services. When it finishes, it prints a message that Plesk is installed and shows a login link.

Alternative: Installer With Custom Components

If you want control over components (for example, skipping mail or adding Fail2Ban), use the installer directly:

wget https://autoinstall.plesk.com/plesk-installer
chmod +x plesk-installer
./plesk-installer install plesk --preset Recommended

You can also start the web-based installer and pick components in a browser:

./plesk-installer --web-interface
# then open https://SERVER_IP:8447

Close port 8447 when you are finished.

First Login and Initial Configuration

Generate a one-time login link from the shell:

plesk login

Open the link in your browser. You will see a certificate warning on the first visit because the panel uses a self-signed certificate. That is expected until you secure the hostname in a later step.

If you prefer a fixed admin password, set one:

plesk bin admin --set-admin-password -passwd 'UseALongRandomPassword'

On first login, the setup wizard asks for:

1. Hostname. Use the FQDN you set earlier.
2. Default IP address. Choose the server's public IPv4. Mark it as shared unless you plan to use dedicated IPs per customer.
3. Admin contact and password.
4. License. You can start a trial, or install a purchased key.

To install a license key from the command line:

plesk bin license --install A00A00-AAAA00-AA0A00-A0A000-0A0000

The key above is a placeholder. Use the one you received from your license provider.

Recommended Settings to Change Right Away

• Enable two-factor authentication for the admin account under your profile.
• Secure the panel hostname. Go to Tools & Settings → SSL/TLS Certificates and use Let's Encrypt for the server hostname so the browser warning disappears.
• Turn on the Plesk Firewall extension and review the default rules. Allow SSH only from your own IPs if you can.
• Install Fail2Ban and ModSecurity from Tools & Settings → Updates if they were not part of your preset.
• Schedule backups to remote storage, not only to the local disk.
• Enable automatic updates under Tools & Settings → Update Settings.

Add Your First Domain

In the UI: Websites & Domains → Add Domain → Blank website (or WordPress). Enter the domain name, a system username, and a password.

Before you add it, create the DNS records at your registrar or DNS host:

example.com.        IN A     192.0.2.10
www.example.com.    IN CNAME example.com.

If Plesk will also be your DNS server, set your nameserver records to point at the server and keep the DNS service enabled.

You can create the same thing from the shell. This creates a subscription (a domain with hosting) under the default service plan:

plesk bin subscription --create example.com \
  -owner admin -service-plan "Default Domain" \
  -ip 192.0.2.10 -login siteuser -passwd 'AnotherLongPassword'

Upload files by SFTP or the File Manager into /var/www/vhosts/example.com/httpdocs. Pick the PHP version under PHP Settings for each domain, rather than relying on the global default.

Issue an SSL/TLS Certificate

The Let's Encrypt extension ships with the recommended preset.

In the UI:

1. Open Websites & Domains, then your domain.
2. Click SSL/TLS Certificates.
3. Choose Install a free basic certificate provided by Let's Encrypt.
4. Enter an email address, tick the www alias, and optionally the webmail alias.
5. Click Get it free.

CLI equivalent:

plesk bin extension --exec letsencrypt cli.php \
  -d example.com -d www.example.com -m admin@example.com

Then, under Hosting Settings, enable Permanent SEO-safe 301 redirect from HTTP to HTTPS. Plesk renews Let's Encrypt certificates automatically, usually about 30 days before expiry.

Common SSL Mistakes

• Validation fails with a timeout. Port 80 is blocked, or the A record points elsewhere. Check with dig +short example.com and test the port from outside.
• IPv6 AAAA record points to a different host. Let's Encrypt prefers IPv6 when available. Remove the AAAA record or point it at this server.
• Wildcard certificate fails. Wildcards need DNS-01 validation. Plesk can do it only when it hosts the DNS zone for that domain.
• Mixed content warnings. Update the site URL in WordPress or your CMS to https://.

Troubleshooting the Install

• Installer aborts on a "package conflict." The server was not clean. Reinstall the OS and run again.
• Cannot reach port 8443. Check the provider firewall and the Plesk Firewall. Run ss -tlnp | grep 8443 to confirm that the service is listening.
• Out-of-memory kills during install. Add swap or increase RAM.
• Mail is rejected by large providers. Set a PTR record for the server IP to match the hostname, and add SPF, DKIM, and DMARC for each domain.
• Check services and logs:

plesk repair installation
systemctl status sw-engine psa
tail -n 100 /var/log/plesk/install/plesk_17.x_installation.log

plesk repair installation checks file integrity and fixes many broken installs without a reinstall.

Plesk vs cPanel: How They Compare

Both are mature hosting panels. The right pick often depends on your OS, your customers, and your workflow.

In short: choose Plesk if you want Windows support, a single modern interface, or strong WordPress tooling. Choose cPanel if your customers already know it or your migration path is from another cPanel server. If you go the cPanel route, see our cPanel WHM installation guide for the setup process on AlmaLinux, Rocky, and Ubuntu.

Protect the Panel and the Server

A public hosting panel is a target. A few habits keep it safer:

• Restrict port 8443 and SSH to trusted IPs where practical.
• Keep Plesk and the OS updated.
• Use unique passwords and 2FA for every administrator.
• Watch for volumetric floods, since a web server with a public IP can be knocked offline even if the panel is perfectly configured. Our DDoS protection and firewall service filters attack traffic upstream, before it reaches your VDS.

Final Checklist

• [ ] Clean supported OS, FQDN set, DNS A record in place
• [ ] Plesk installed with the one-click installer
• [ ] Admin password and 2FA configured
• [ ] Panel hostname secured with Let's Encrypt
• [ ] Firewall, Fail2Ban, and ModSecurity reviewed
• [ ] First domain added, SSL issued, HTTPS redirect on
• [ ] Remote backups scheduled
• [ ] PTR, SPF, DKIM, DMARC set if you send mail