How to Update Plesk Obsidian on VPS or Dedicated Server (Step-by-Step Guide)

Learn how to update Plesk Obsidian on a VPS or dedicated server using SSH. This step-by-step guide covers backups, upgrade commands, troubleshooting, and best practices for a safe Plesk update.

How to Update Plesk Obsidian on VPS or Dedicated Server

Keeping your Plesk Obsidian installation up to date is one of the most important tasks for maintaining a secure, stable, and high-performing hosting server. Every new Plesk update includes security patches, bug fixes, performance improvements, and compatibility updates for modern technologies such as PHP, MariaDB, MySQL, Apache, Nginx, and the WordPress Toolkit.

Whether you’re managing a VPS or a dedicated server, updating Plesk regularly helps prevent security vulnerabilities and ensures your hosting environment continues to run smoothly.

In this guide, you’ll learn how to safely update Plesk Obsidian using SSH, verify the update, and resolve common issues that may occur during the upgrade process.

Why Should You Update Plesk Obsidian?

Updating Plesk isn’t just about getting new features. It also helps improve your server’s overall health and security.

Benefits include:

• Latest security patches
• Bug fixes and stability improvements
• Better server performance
• Improved WordPress Toolkit
• Support for newer PHP versions
• Compatibility with updated Linux packages
• Enhanced email and database services
• Updated Plesk extensions
• Improved backup and restore functionality

Keeping Plesk updated is considered a best practice for every production server.

Prerequisites Before Updating

Before starting the update, ensure the following:

• Root SSH access
• A valid Plesk license
• A full server backup or VPS snapshot
• Stable internet connection
• At least 2–5 GB of free disk space
• No critical maintenance tasks running

Although Plesk updates are generally safe, creating a backup before any major update is always recommended.

Step 1: Connect to Your Server via SSH

Connect to your VPS or dedicated server using your preferred SSH client.

For Linux or macOS:

ssh root@your-server-ip

For Windows, you can use PuTTY or Windows Terminal.

Once connected, verify your current Plesk version.

Step 2: Check the Current Plesk Version

Run:

plesk version

Example output:

Product version: Plesk Obsidian 18.0.xx

Knowing the current version helps confirm that the update completed successfully later.

Step 3: Update the Plesk Installer

Before upgrading Plesk itself, update the installer.

plesk installer update

This downloads the latest installer files and update information.

Step 4: Upgrade Plesk Obsidian

Run the following command:

plesk installer --select-release-latest --upgrade-installed-components

This command will:

• Download the latest Plesk packages
• Upgrade the control panel
• Update installed components
• Install dependency updates
• Apply the latest fixes

Depending on your server and internet speed, the process may take between 10 and 30 minutes.

Step 5: Wait for the Upgrade to Finish

During the installation you may see messages similar to:

• Downloading packages
• Installing updates
• Updating components
• Configuring services
• Completing installation

Do not close the SSH session until the installer finishes successfully.

Step 6: Verify the Installed Version

After the upgrade completes, verify the installed version.

plesk version

You can also check:

cat /usr/local/psa/version

The displayed version should now reflect the latest installed release.

Step 7: Restart Plesk Services (Optional)

Most updates restart services automatically.

If necessary, restart them manually.

For systemd-based distributions:

systemctl restart psa

Or:

service psa restart

Step 8: Log in to the Plesk Panel

Open your browser and visit:

https://your-server-ip:8443

Log in and verify:

• Websites are online
• Email services are working
• Databases are accessible
• SSL certificates remain valid
• Scheduled backups are functioning
• Installed extensions load correctly

How to Check Available Updates

To see available Plesk releases:

plesk installer --show-releases

To display installed components:

plesk installer --show-components

These commands help you determine whether additional components require updating.

Common Update Errors and Solutions

1. License Error

If the installer reports a license issue:

• Verify your license is active.
• Refresh the license from the Plesk panel.
• Contact your license provider if necessary.

2. Insufficient Disk Space

Check available storage:

df -h

Delete unnecessary files, logs, or old backups before retrying the update.

3. Repository Errors

Refresh your package repositories.

For AlmaLinux, Rocky Linux, CentOS:

yum clean all
yum makecache

For Ubuntu or Debian:

apt update

4. Download Failed

Possible causes include:

• Firewall restrictions
• DNS issues
• Internet connectivity problems
• Proxy configuration

Verify your network settings before trying again.

5. Plesk Installer Stops Unexpectedly

Run:

plesk repair installation

This command checks and repairs common installation issues automatically.

Best Practices Before Updating

To reduce the risk of downtime:

• Create a complete server backup.
• Take a VPS snapshot if your provider supports it.
• Perform updates during low-traffic hours.
• Close unnecessary SSH sessions.
• Ensure enough free disk space.
• Keep your operating system updated.
• Test websites after the upgrade.

Frequently Asked Questions

Will updating Plesk delete my websites?

No. Updating Plesk does not remove your websites, databases, email accounts, or files. However, maintaining a recent backup is strongly recommended before any server update.

How long does the update take?

Most Plesk updates complete within 10 to 30 minutes, depending on the server hardware, installed components, and internet connection.

Can I update Plesk from the web interface?

Yes.

Navigate to:

Tools & Settings → Updates and Upgrades

However, SSH is generally preferred because it provides better visibility into the update process and makes troubleshooting easier if any errors occur.

Is a server reboot required?

Usually, no. A reboot is only recommended if the update includes operating system components that require restarting the kernel or other core services.

Is it safe to update Plesk on a production server?

Yes. Plesk updates are designed to preserve websites, databases, email accounts, and server configurations. Still, creating a backup before updating is considered a best practice.

Final Thoughts

Updating Plesk Obsidian on your VPS or dedicated server is an essential part of routine server maintenance. Regular updates improve security, fix software bugs, enhance compatibility with modern technologies, and ensure your hosting environment remains stable and reliable.

By following the steps in this guide, you can safely update your Plesk installation using SSH while minimizing downtime and protecting your hosted websites.

Make it a habit to check for new Plesk releases regularly and always create a backup before applying updates to a production server.

Helpful Links