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

Automatic Update does not take all builds

S

scheinzwerg@

Guest
I have just seen by coincidence (i saw that people here on the forums were talking about build numbers) that the plesk-version on my server was out of date. I controlled this by looking in the patches-section of the sw-soft site.

My question now is: is there a hidden key that I have to set so that my plesk recognizes when it is out of date not just by the version number w.x.y, but also by the build number w.x.y.zzzzzzzzz ?

Greetings!
- Jérôme
 
Use the Plesk Updater in the Plesk control panel. It will show you what is out of date and let you update from there.
 
Sorry, but: "Helloo Captain Obvious". I haven't said that I looked in the updater or at the bash because it seemed obvious to me that the information of my plesk being out of date must have come from somewhere ;).
 
Back
Top