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

CentOS Upgrades

H

hakkrdan

Guest
Hello, all -

I've been using Linux for quite a while, and know how to administer a server quite well. It's a daily practice for me.

I haven't touched my CentOS 3.3 server running Plesk 7.5.4, in quite a while. It's been my experience that Plesk is very very picky about the underlying operating system, and I've had upgrades of the system itself (Apache, BIND, etc etc) actually break Plesk.

I just wanted to know what everyone else thought about updating packages as part of the core system, and how PLesk should react. Ideally, of course, Plesk wouldn't react - it would simply do it's job independently, on top of what is already installed.

If anyone could provide me with some feedback and experiences, I would greatly appreciate it. Like I said, I really do know what I'm doing, but I'm extremely hesitant about updating this machine, for fear of breaing Plesk.

Thanks!
-dant
 
Back
Top