• 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 and PLESK

A

akucharski

Guest
I noticed on some posts that some updates to the OS or apps have caused some users issues.

One recent post I read that caused some problems was an upgrade from MySQL 3.x to 4.x. My question is; have you experienced any problems running up2date on RH ES3 outside of PLESK?

Also, have upgrades supported by ES3 ever affected PLESK apps?

Thanks for your experienced insight feedback.
 
I also run RHEL3.0 Update 4. I've been able to run update with the ignore *psa* and *spam* just to be on the safe side. Plesk has been like a champ to me with that since psa6.
 
Originally posted by atomicturtle
But when you do that, you dont have an excuse to sing the Doom Song.

Don't worry with the dvd's I hear the doom song all the time!
 
Back
Top