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

Two current versions of Plesk

M

mattearwicker

Guest
We had trouble upgrading to 8.1.0 from 8.0.1. After much searching on this site, we found how to change some of the database entries to fi spamfilter and massmailer settings. Everything appears to be working, except that we are left with two copies of Plesk. An update, for example, includes the following lines:

release PLESK_8_0_1 is actual
release PLESK_8_1_0 is actual

If I do:

rpm -q psa, then I see:

psa-8.0.1-fc4.build80060613.20
psa-8.1.0-fc4.build81061129.22

It happily updates psa 8.1.0 files each time, but as it only reads the first response to an rpm -q query, it thinks only the psa 8.0.1 files exist. Is there any way to change this? If I run:

rpm -e psa-8.0.1-fc4.build80060613.20

then I am warned that lots of hotfixes depend on this. I am hesitant to force an uninstall if this might crash an otherwise working system. Any ideas?
 
Back
Top