• 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.

10.3.1 Updates

EinariH

New Pleskian
Hi!

I manually updated the Plesk 10.3.1 via "Tools&Utilities > Update" as it told me there was updates available. Now after "successful" update it still tells me so? What is the catch? My update_components.html page tells me this:

Below is a list of components for which updates are available. Select the components that you want to update.

Different Apache web server versions: Apache web server with SNI support
Different MySQL server versions: MySQL server support


These surely were checked when I updated first time. Should I keep trying or give up? All this is because I noticed that my httpd component version is 2.2.19-11072010 and there could be a newer one available maybe?

Thanks,
Eicca
 
Back
Top