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

up2date, what to do

G

garsan

Guest
Hello everyone, im new with plesk, i recently updated my box to 7.5.3 via the updater icon.

I want to use up2date on my RHEL3 but i dont know if this is safe.

What packages cannot be upgraded via up2date?

There are a few post about this, but not a real response.

Thanks for your help.
 
I use up2date all the time and it is safe. You can always revert back to your previous environment if all hell breaks loose.

I mostly use A.R.T.'s repository at www.atomicrocketturtle.com which is like up2date on steriods!! :D
 
Hi, thanks for your answer.

httpd, quota, initscripts, bind, rpm, mod_* can be updated too?

I already updated all the other packages, and seems there are working fine.
 
Yeah, you should be able to update all you have listed just fine.
 
Back
Top