• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • 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.

Updating via ssh

L

Lehman

Guest
Hello,

I was trying to install ImageMagick and used the wrogn command to change permissions, so now my Plesk is not inicializing. I cannot access the panel. I was wondering if running the autoinstaller via ssh would delete all of my sites data and mysql database information, or just update the plesk installation without touching the files from my ftp and my mysql databases.

Thanks in advance.
 
Thank you.

The installation says the following:

Downloading the file PSA_8.3.0/plesk_getkeyinfo.sh: 100% done.
Exchanging information with licensing server.base
Warning: your license key for the base component cannot be upgraded.

Continuing with the upgrade without having an appropriate product license
will result in the installation of a default license with limited
functionality. Administrators are advised to first acquire the appropriate
license before continuing with the product upgrade.

Do you want to continue?

Do I continue? Would I be able to enter the correct key on the installation via the control panel?
 
Oh my... now it says:

Plesk and operating system packages will be downloaded and saved to the
directory '/root/swsoft'.

Required disk space: 6.09 Mb.

Available disk space: 0.00 Mb.

An there is space indeed. :S
 
I found that when I tried this it worked on one machine and failed on another becuase I didnt have port 5224 open - (tcp egress -> plesk-license-update), although it only really failed when sitebuilder was involved.
 
Back
Top