Question Automatic plesk updates

[Bossman]

Server operating system version

Almalinux (newest)

Plesk version and microupdate number

18.0.74

1. System updates
2. Plesk updates
3. Extension updates

Do you guys have it all enabled in production enviroment ?,
Is it safe really ?,
I have disabled it and managing it by hand, is it good policy you think ?

Couple years ago there where option to update plesk with - with "tested, stable" updates, and you had also early updates. I dont see that option anymore.
Reason for asking this, i just not having HA and preventing one day, headake if something breaks after update.

 

[learning_curve]

~~
Do you guys have it all enabled in production enviroment ?,
~~

FWIW We do all manually and have done for some time now without issues.

~~
Couple years ago there where option to update plesk with - with "tested, stable" updates, and you had also early updates. I dont see that option anymore.
Reason for asking this, i just not having HA and preventing one day, headake if something breaks after update.

There are other posts about this ^ very subject if you run a search, albeit our view was; Do you really need this, if, all of your updates are manual not auto?

 

[Ahmet CAVUSOGLU]

Hi @Bossman

We generally perform Plesk and package updates manually when providing services to our customers.

There are several reasons for this:
1. Plesk version updates may or may not be stable. Because Plesk uses a large number of application packages, it takes some time for the latest versions to become stable and for problems to be identified. (We apply this policy not only to Plesk but to all Windows updates )
2. If the server becomes unresponsive, we skip an item from the checklist of possible causes because we know there is no update error.

Update Recommendation: Always test Plesk and package updates by setting up a test system (perhaps another VPS server) and testing it for a week. Observe developments such as email and web services. Also, be sure to follow the Plesk Forums after each update is released. Depending on the risk, you can skip a version and update to the next one. We have set up plugin updates automatically. In our long-term testing (on Ubuntu 24), we found that the solution we wrote was stable.
Don't forget to create a backup in one or two locations before updating!

If you have security concerns, you can follow the Plesk release lifecycle.: Plesk and Plesk Version Lifecycle Policy

Of course, these suggestions are based on our experience. More experienced users may, suggest different things. And if there's anything we've missed, please correct us

Have a nice day