• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:

    https://pt-research.typeform.com/to/AmZvSXkx
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Plesk 12.5.30 to 12.5.31

Thanks, Igor. The commands worked perfectly.

At first I tried and I got an error stating that an updater lock file prevented a duplicate installation process from running and it exited without updating (even though in top I couldn't see anything installing).
So, I restarted the server and tried it again and it flew right through updating everything to MU#32.

Interesting thing — I have two of these servers on completely different machines through my provider and the same thing happened on each one.
 
Just ask your provider.

You might as well have a closer look at the output of the command:

plesk installer --select-release-current --reinstall-patch --upgrade-installed-components

... because it shows the actual used source as well. :D If the source is not "http://autoinstall.plesk.com/", then a mirror is used, which may delay actual releases.
 
Back
Top