Applicable to:
- Plesk for Linux
- Plesk for Windows
Question
How to upgrade Plesk to the next release?
Answer
Note: To find out if your operating system is supported by the next Plesk release, visit the Plesk Lifecycle Policy page.
Warning: To upgrade from Plesk Onyx 17.5 to Obsidian, first upgrade to 17.8.
Note: Make sure that port 8447 is opened in firewall. If it is closed and cannot be opened, use the command-line instructions.
-
Go to Tools & Settings and click Updates and Upgrades.
-
On the Updates and Upgrades page, click Install or Upgrade Product.
-
On the Install or Upgrade Product page, select a Plesk version from the drop-down list and click Continue to begin the upgrade procedure.
For detailed instructions, see:
-
Connect to a Plesk server via SSH (Linux) / RDP (Windows Server).
-
Start Plesk Installer:
-
on Linux, run the command:
# /usr/local/psa/admin/bin/autoinstaller
-
on Windows Server, start a command prompt as an Administrator and run the command:
C:\> "%plesk_bin%"\ai.exe --console
-
-
Follow the on-screen instructions. For details, see:
Additional Information
During the upgrade process:
- Plesk will be unavailable
- Websites will stay online
Comments
26 comments
What can I do if there's no update available?
@Alessandro Marengo
Hello!
Could you specify which version is currently installed?
Generally, please try to start Plesk Installer with the parameter --all-versions, for example:
"%plesk_bin%"\ai.exe --console --all-versions
Thanks Ivan for your reply.
What if, instead of using command line, I'd like to use Plesk Updates option?
@Alessandro, this option is available only in CLI version of Plesk installer. If you cannot see the desired version for the upgrade, it may mean that your OS does not meet all requirements.
Running /usr/local/psa/admin/bin/autoinstaller says that it should only be ran on clean install servers and that I should backup my data, so I am not sure I should proceed:
Hi @adrianTNT!
In case you are updating Plesk, the warning about clean server may be ignored, this is for new installations only.
As for backup, it is a general recommendation in case the update will fail (usually the process goes fine). You may make a server snapshot or backup Plesk domains.
Hi, I'm running Plesk Onyx on CentOS 7. "Install and Upgrade Product" is grayed out. In the "Update and Upgrade Settings", I have General Release selected. Is that the issue potentially? Thanks. - Ignore this got it running, how can I tell if the upgrade is stuck. Been running for 2 hours now still on 45/17something.
Hello @Michael,
Please check the last records in /var/log/plesk/install/autoinstaller3.log. If the file is not updated then the upgrade is stuck.
In this case please kill the existing installer process using the article:
https://support.plesk.com/hc/en-us/articles/213917525
After that, run Plesk upgrade using the command line:
# plesk installer
The solution regarding grayed out Install or Upgrade Product option is described below:
https://support.plesk.com/hc/en-us/articles/213914005
If you still face issues with Plesk upgrade, please contact support directly:
https://support.plesk.com/hc/en-us/requests/new
Plesk Onyx 17.8.11 on Centos7
Installation of 18.0.20 via web installer is not possible. Last error in the line of errors is: postfix3 meets postfix-2...
@Rainer Kraft
Looks like dependency issue with postfix package, please contact support directly:
https://support.plesk.com/hc/en-us/requests/new
@Lev lurev
That's not possible, 'cause I got Plesk from my Provider and it is not possible to get any more help, than this forum. Here are some lines from the log:
Package 2:postfix-2.10.1-7.el7.x86_64 already installed and latest version
PyYAML-3.10-11.el7.x86_64.rpm | 153 kB 00:00
libyaml-0.1.4-11.el7_0.x86_64.rpm | 55 kB 00:00
dejavu-sans-mono-fonts-2.33-6.el7.noarch.rpm | 433 kB 00:00
rrdtool-perl-1.4.8-9.el7.x86_64.rpm | 42 kB 00:00
rrdtool-1.4.8-9.el7.x86_64.rpm | 440 kB 00:00
postfix3-3.4.7-1.gf.el7.x86_64.rpm 0.0 B/s | 3.1 MB 00:00 postfix3-3.4.7-1.gf.el7.x86_64.rpm | 3.1 MB 00:04
Fatal error during packages installation:
Test Transaction Errors: file /usr/libexec/postfix/local from install of postfix3-2:3.4.7-1.gf.el7.x86_64 conflicts with file from package postfix-2:2.10.1-7.el7.x86_64
If I search for postfix-2, there is no result on the server
Warnung: Keine Übereinstimmung gefunden für: postfix-2.10.1-7.el7.x86_64
Perhaps it points someone in the right direction. I stopped the update for now.
Hi @Rainer Kraft,
It's hard to provide you with exact steps without taking a look at the issue.
As the license you own was purchased from our partner, you can buy a support subscription and contact Plesk Support Team directly.
Check this article for details: https://support.plesk.com/hc/en-us/articles/213953025-How-to-get-support-directly-from-Plesk-
First 30 days are free of charge.
> Note: Make sure that port 8447 is opened in firewall. If it is closed and cannot be opened, use the command-line instructions.
Can you please elaborate if the mentioned port 8447 is for outgoing (from Plesk to Internet) or incoming (from Internet to Plesk) connections? Or even both directions?
@Claudio incomming
Plesk hung on an update from 18.0.20-->18.0.21. Appears update was incomplete.
Server working fine, but no longer able to access Plesk control panel.
Error log indicates plesksrvstartuphandler.exe failed with error code 255, failed opening required "Loader.php."
When I examine the relevant folder (Plesk\admin\plib), it looks like the files in that folder are incomplete. The files there all show a date modified that matches the time of the upgrade, but the files are all alphabetically "A" through "E" and stop abruptly at "E". It appears any files "F" through "Z" are missing (including the indicated "Loader.php."
It seems the upgrade was interrupted and now I have a problem.
Attempts to reinstall the upgrade through command line seem successfull "you already have the latest version of the product and selected components installed, installation will not continue."
But not able to launch Plesk control panel :(
@Scott Saccenti,
it's hard to propose a solution on the fly, as such issues require direct investigation on the server.
Thus, I'd recommend contacting our Technical Support Team for assistance.
I have Plesk through a GoDaddy VSP, so I don't think your Tech Team will support me.
So I have to support myself. Got it fixed, running the following from a command prompt (admin):
C:\>plesk installer --select-release-current --reinstall-patch --upgrade-installed-components
This managed to rebuild the corrupted folder that I correctly described above (when I check it now, files exist from "A" to "Z."
Hopefully this helps the next poor sob.
Hello Scott Saccenti,
Thank you for sharing your experience. Indeed, this may help other Pleskians.
I decided to try and upgrade from Onyx to Obsidian (0.21) today. It took like 3 hours, with most of the time systemd (init -z) using 100% of the cpu. During these hours I couldn't access the control panel. Also the update log showed the following error message like 100 times: "Failed to list unit files: Connection timed out".
4 cores server with 4GB of RAM and SSD disk running Ubuntu 18.04.
One of the worst experiences I've had with a control panel.
Also apparently now my server is running Grafana for some reason. Like really, I have to run Grafana for a control panel. Is Plesk becoming the new Gitlab, where you will need a NASA computer to run it fast?
Hello,
3 hour is not normal for the upgrade, please create a support ticket to check why it took so long.
Graphana is a part of Advanced Monitoring extension added in Obsidian, if you don't want to run it you may remove it under Extensions catalog.
Hello
I have made an update to Plesk Obsidian and I have the following error:
ERROR while trying to check the hostname
Bootstrapper has finished action (exec time: 1 sec.): Parent_name = 'panel', sequence = 'prep', stage = 'execute', sequence_order = '0', operation = 'install', exec_cmd = '/ opt / psa /bootstrapper/pp18.0.25-bootstrapper/bootstrapper.sh prep-install BASE '', m_arch = '', output:
**** Product prep-install started.
Create user 'psaadm' and group 'psaadm'
Group 'psaadm' already exists
Checking for the user 'psaadm' ...
User 'psaadm' already exists
Create group swkey-data
Group 'swkey-data' already exists
Trying to add supplementary group 'swkey-data' for user 'psaadm' ... already there
Trying to got legacy variables ... done
Trying to save legacy variables ... done
Trying to resolve hostname 'sample.com' and validate its IP address ...
Can not bind a socket to address sample.com:715 - Cannot assign requested address
Please check your network configuration
ERROR while trying to check the hostname
***** problem report *****
ERROR while trying to check the hostname
[2020-03-26 09: 50: 10.384716] Bootstrapper has finished action (exec time: 0 sec.): Parent_name = 'PLESK_18_0_25', sequence = 'prep', stage = 'rollback', sequence_order = '1', operation = 'install', exec_cmd = 'rm -f /tmp/pp-bootstrapper-mode.flag; rm -f /var/lock/parallels-panel-maintenance-mode.flag; rm -f /var/lock/parallels-panel-upgrade-failure.flag; : '', m_arch = '', output: ~ empty
I have changed the real domain to "sample.com".
On the other hand, I have applied this KB: https://support.plesk.com/hc/en-us/articles/213941265-How-to-change-or-get-the-server-hostname-on-Plesk-server
But I continue with the problem. Can you help me?
Thanks!
Hi @Enrique Ruiz Millan,
Please apply the resolution steps from the article:
https://support.plesk.com/hc/en-us/articles/213396889-Plesk-upgrade-or-update-fails-ERROR-while-trying-to-check-the-hostname
If you face any further issues, please contact Plesk technical support for assistance:
https://support.plesk.com/hc/en-us/requests/new
Hello, Please help me.
I cannot upgrade Plesk 12.5.30 to Plesk 17.8.11.
I encountered an error, that I could not solve.
Please help me to solve this problem, and help guide me to successfully upgrade Plesk 12.5.30 to Plesk 17.8.11.
@มงคล รอดศรี
Please create a ticket to our support department.
Je ne peux pas mettre mon plesk à jour de la version 17.8.11 vers 18.0.3 , il me met cet erreur :
Hello Arnaud DEBRINCAT
As I can see, you've contacted Plesk support and it was found that the issue was caused by the Docker process failing to start.
Please sign in to leave a comment.