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

Plesk 8.0 on FreeBSD 5.3: possible?

E

_ender@

Guest
Greetings,

I'm of course going to be attempting this today on one of my development machines, but I thought I would throw the question out here as well, to see if any fellow FreeBSD users could offer some insight.

I've been running Plesk since 1.0, and find myself in a position where I'm interested in upgrading to 8.0, but the download versions indicate FreeBSD 5.4 as the base O/S version required.

Has anyone installed Plesk 8.0 on FreeBSD 5.3 successfully, and did you have any notable issues? My main concern is that I Have production boxes that I really can't afford downtime on, in order to upgrade the O/S one version point. Of course, Plesk 7.5.4 is working just fine on them, so I don't have to upgrade, but new features are alway nice.

Any fellow FreeBSD users out there?
 
I have plesk8 running on freebsd5.4 without issues atm,
upgrade was a lil tough at first because of
/usr/local/psa/apache/bin/apachectl
/usr/local/psa/apache/bin/apxs
/usr/local/psa/qmail/sendmail
all being protected by schg
I had to chflags noschg eachfile and then the upgrade went fine.
 
Back
Top