• Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Upgrade Method - ssh vs control panel

bradz

Regular Pleskian
Hi, In the past, I have always used the Plesk Control Panel to run updates, however this last time, 9.5 to 10.2, it did not work and based on a post, I tried it using ssh which work! Is it safer or better to run updates using ssh? Pros or Cons?
Thanks!
Brad
 
For updating via interface make sure that you have not firewalled port 8447.
I think that more experienced Plesk users uses autoinstaller CLI command. I think that it allow to control upgrade process much more effectively.
 
I would never do it via the GUI; you can't see what went wrong when it breaks, which is half the time, and additionally, if you do it from command line, you can type:

Code:
export PLESK_QUOTACHECK_OFF=1

before running autoinstaller and that will prevent it from calculating the mailbox quota on every single mail account on the server, which can make the upgrade take hours longer if it's a big server.
 
Back
Top