How to perform a dist-upgrade?
Warning: The dist-upgrade procedure is complex, hence you may want to consider migrating instead as explained in Plesk Migration and Transfer Guide.
Warning: The dist-upgrade procedure can not be performed in a containerized environment. If the environment is not known, contact the server provider in order to know if the server or the environment is a container
Warning: For servers running Plesk versions below 18.0.45, always use Plesk-Archive repository in sources.list file by replacing "autoinstall.plesk.com" with "autoinstall-archives.plesk.com" in the following instructions
The dist-upgrade procedure is supported for the following Plesk versions and operating systems:
| Supported for | Plesk version |
|---|---|
| Ubuntu 20 > Ubuntu 22 | Plesk Obsidian 18.0.44 and above |
| Ubuntu 20 on ARM > Ubuntu 22 on ARM | Plesk Obsidian 18.0.46 and above |
| Ubuntu 18 > Ubuntu 20 | Plesk Obsidian 18.0.33 and above |
| Ubuntu 16 > Ubuntu 18 | Plesk Obsidian 18.0.30 and above |
| Debian 10 > Debian 11 | Plesk Obsidian 18.0.42 and above |
| Debian 9 > Debian 10 | Plesk Obsidian 18.0.30 and above |
If you have never performed dist-upgrade before, it is recommended to test it first as follows:
-
Install the previous version of OS on a test server or inside a virtual machine. Upgrade it using the instructions provided in the documentation by the OS vendor:
-
Solve all potential problems and make sure Plesk is working after the upgrade before proceeding with the upgrade on the production server.
If you want or need Plesk to assist on this task or to do it on your behalf, place a request to Plesk Professional Services team here: Plesk Professional Services: Administrative Services
Ubuntu distributions
Dist-upgrade from Ubuntu 20 (Focal Fossa) to Ubuntu 22 (Jammy Jellyfish)
Warning: The dist-upgrade process from Ubuntu 20.04 to Ubuntu 22.04 on x64 CPUs is supported by Plesk Obsidian 18.0.44 version. The dist-upgrade process from Ubuntu 20.04 to Ubuntu 22.04 on ARM CPUs is supported by Plesk Obsidian 18.0.46 version.
Preparing server for upgrade
-
Create a full server backup. Before the upgrade, make a full server backup (which includes a full backup of all the databases). Also, notify the customers about upcoming downtime of one to three hours
-
Connect to the server via SSH
-
Change to root user by using the following command:
# sudo su -
-
Enable enhanced security mode:
# plesk bin passwords --encrypt
-
Uninstall the unsupported components mailman, ruby and PHP handlers below version 7.3:
# plesk installer remove --components php7.1 php7.2 php7.3 mailman gems-pre ruby
# apt-get purge $(dpkg -l | egrep "(plesk-ruby2|plesk-rbenv)" | awk '{print $2}')
-
Remove packages which were installed by dependencies but are not required:
# apt-get autoremove
-
Execute the command below to be sure that system is up-to-date:
# plesk sbin pum --update
-
Run the command to make Plesk up-to-date:
# plesk installer update
-
Install aptitude:
# apt-get install aptitude
-
Remove repository lists that are related to Plesk:
# rm -f /etc/apt/sources.list.d/plesk*.list
Performing the dist-upgrade
-
Replace focal sources lists with jammy sources lists in
/etc/apt/sources.listand/etc/apt/sources.list.d/*.list:# sed -i "s/focal/jammy/g" /etc/apt/sources.list
Note: below is the example for
/etc…
with