• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

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