How to Update Plesk on Linux (CLI and GUI Methods)

May 31, 2026 Plesk on Linux
Summarize this article with:
Last update: May 31, 2026 • 6 min read

Overview

A Plesk update installs the latest Plesk Obsidian release, security patches, and component upgrades — things like PHP handlers, Nginx builds, and the Plesk updater itself. If you’re running an older Plesk version, you’re likely missing security fixes that Plesk publishes on a rolling basis.

Most users land here because they’ve seen an “Update Available” banner in the Plesk dashboard, received a Host & Tech server alert about an outdated panel version, or they’re troubleshooting an extension that requires a newer Plesk release to function. Either way, the process is the same.

This guide covers both the web UI and CLI methods. I’d recommend the CLI approach for anything running in production — it gives you real-time output and doesn’t time out the way a browser session can during a long upgrade.

Prerequisites

  • Root SSH access to your Linux server, or a sudo-enabled user
  • Plesk Obsidian 18.0.x installed (this guide does not cover migrating from Plesk Onyx or earlier — that’s a separate process)
  • At least 2 GB of free disk space in /tmp and on the root partition
  • A current backup of your server or Plesk subscription data — non-negotiable before any panel upgrade
  • Your server’s SSH port and login credentials handy, in case the web UI becomes unreachable mid-update
  • If you’re on a VPS SSD Hosting plan, confirm your plan has sufficient RAM — Plesk upgrades have been known to stall on instances with less than 1 GB available memory

Step-by-Step Instructions

Method 1: Update Plesk via the Command Line (Recommended)

  1. Connect to your server over SSH.

    ssh root@your-server-ip

    If your host uses a non-standard SSH port, add -p PORT to the command.

  2. Check your current Plesk version.

    plesk version

    This outputs your current Plesk release, build number, and OS. Note this down — you’ll want it if you need to roll back or open a support ticket.

  3. Run the Plesk installer to fetch the latest release.

    plesk installer update

    This is the main command. It contacts Plesk’s update servers, downloads any pending packages, and applies them. On a standard VPS, this typically takes 5–15 minutes depending on how many components need updating.

    📝 Note: plesk installer is a wrapper around /usr/local/psa/admin/bin/autoinstaller. If plesk installer isn’t found, run the autoinstaller directly:

    /usr/local/psa/admin/bin/autoinstaller --select-product-id plesk --select-release-current --upgrade-installed-components
  4. Watch the output carefully. The installer prints each component as it installs. If you see ERROR lines, don’t panic yet — some non-critical component warnings are normal. Critical failures will stop the process outright.
  5. After the update completes, verify the new version.

    plesk version

    Confirm the version number has changed. Also restart Plesk services to make sure everything initialized cleanly:

    plesk repair installation

    This command checks for broken or missing Plesk components and fixes them automatically — it’s a good habit to run it after any major update.

Method 2: Update Plesk via the Web Interface

This method works fine for minor patch updates. I wouldn’t use it for major version upgrades — browser sessions can time out and leave the upgrade in an undefined state.

  1. Log in to Plesk as admin.
  2. Go to Tools & Settings → Updates and Upgrades (under the “Plesk” section).
  3. Click Install or Upgrade Plesk.
  4. On the next screen, select Update to the Latest Version and click Continue.
  5. Plesk will show a progress screen. Do not close the browser tab during this process.
  6. Once done, Plesk will reload and display the updated version number in Tools & Settings → About Plesk.

⚠ Warning: If your session times out mid-update, SSH in immediately and check whether the autoinstaller process is still running:

ps aux | grep autoinstaller

If it’s still running, leave it alone. If it’s not running and Plesk is broken, proceed to the troubleshooting section below.

Updating Individual Plesk Components

Sometimes you don’t need a full Plesk upgrade — just a specific component like the Plesk firewall module, Imunify360 integration, or a PHP version. You can update individual components with:

plesk installer --select-product-id plesk --select-release-current --upgrade-installed-components

Or to add a specific PHP version that’s missing:

plesk installer add --components php8.3

📝 Note: Available component names vary by OS. Run plesk installer list --available-components to see what’s on offer for your platform.

Common Issues & Troubleshooting

Error: “Could not connect to Plesk update server”

Cause: Your server can’t reach autoinstall.plesk.com — usually a firewall rule blocking outbound HTTPS, or a DNS resolution failure.

Fix: First, test connectivity manually:

curl -I https://autoinstall.plesk.com

If that times out, check your firewall for outbound rules blocking port 443. On servers with CSF:

csf -a autoinstall.plesk.com

Also confirm DNS is resolving correctly:

dig autoinstall.plesk.com

Update Stalls or Hangs Indefinitely

Cause: Almost always a disk space problem or a locked RPM/dpkg database. The installer quietly waits for a lock to release instead of throwing a clear error — which is genuinely frustrating.

Fix: Check free disk space first:

df -h

If disk is fine, check for a stale package manager lock:

# For RPM-based systems (CentOS, AlmaLinux, Rocky)
rm -f /var/lib/rpm/.rpm.lock

# For Debian/Ubuntu
rm -f /var/lib/dpkg/lock-frontend /var/lib/dpkg/lock
dpkg --configure -a

Then rerun plesk installer update.

Plesk Web Interface Returns 500 Error After Update

Cause: A Plesk service didn’t restart cleanly after the upgrade — typically sw-cp-server or psa.

Fix:

service sw-cp-server restart
service psa restart
plesk repair installation

If the 500 persists, check the Plesk panel log:

tail -100 /var/log/sw-cp-server/error_log

“Package Conflicts” or Dependency Errors on AlmaLinux / Rocky Linux

Cause: Third-party RPM repos (EPEL, Remi, etc.) sometimes conflict with Plesk’s bundled packages. This is more common than Plesk’s own documentation acknowledges.

Fix: Temporarily disable third-party repos during the update:

dnf update --disablerepo=epel --disablerepo=remi plesk*

Re-enable them after the Plesk update completes. In some cases you may need to identify the conflicting package:

dnf install --best --allowerasing plesk-core

Update Completed But Plesk Still Shows Old Version

Cause: Browser cache, or the Plesk panel session is holding a cached version string. Not actually broken — just cosmetic.

Fix: Hard refresh your browser (Ctrl+Shift+R), then re-check via CLI:

plesk version

If the CLI shows the new version but the UI doesn’t, the UI will catch up after a full logout/login cycle.

FAQ

Frequently Asked Questions

How often should I update Plesk?

Plesk releases security patches and component updates on a rolling basis. I’d suggest checking for updates at least once a month, or enabling Plesk’s automatic minor update notifications so you’re alerted when patches drop. Major version upgrades are less frequent and worth testing on a staging server first if you’re running a busy environment.

Will updating Plesk take my websites offline?

For most minor updates, websites stay online throughout the process — Apache or Nginx might restart briefly, causing a second or two of downtime. Major component upgrades can take web services down for 2–5 minutes. Schedule updates during low-traffic periods and give your clients a heads-up if SLA matters.

Can I roll back a Plesk update if something breaks?

Not easily. Plesk doesn’t ship a native rollback tool for panel version upgrades. Your best protection is a full server snapshot taken before the upgrade — if something goes badly wrong, you restore the snapshot. This is exactly why the backup prerequisite in this guide isn’t optional.

What's the difference between 'plesk installer update' and 'plesk installer upgrade'?

‘update’ applies patches and component updates within your current Plesk release line. ‘upgrade’ moves you to a newer major release (for example, from an older Obsidian build to a current one). For day-to-day maintenance, ‘update’ is what you want. The ‘upgrade’ path requires more planning and testing.

Do I need to update Plesk on a managed hosting plan?

If you’re on a managed VPS or dedicated server with Host & Tech, Plesk panel updates are typically handled as part of the managed service — check your plan details or open a support ticket to confirm. On unmanaged VPS plans, Plesk updates are your responsibility, which is why this guide exists.

Related Articles

Plesk Nginx Failed to Start: How to Diagnose and Fix the Error How to Manage PHP Versions in Plesk (Per Domain and Server-Wide) How to Create a Website in Plesk: Domain Setup and Hosting Configuration

SHARE THIS ARTICLE

Need help with your hosting?

Host & Tech provides 24/7 support for all VPS, dedicated, and shared hosting customers.

Contact Support View Plans
Scroll to Top