• The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Problems with upgrading - support fee question

R

Rodorm

Guest
We use Plesk 8.6 and would like to upgrade to 9.0.0 and after that to any later versions.

We tried the upgrade on a cloned test server and it succeeded, but afterwards, the httpd binary was missing. We think that something might be broken. In January, we had to move our Plesk system to another server. We followed the procedure described in the manual, but afterwards, the users of the webs were mixed up, the files in /var/lib/mysql had the user drweb etc. We corrected all these errors, but maybe something broke in this process which makes it now impossible to upgrade. The first thing we recognized when we wanted to upgrade was that the user sw-cp-server was missing. After creating it, the upgrade started and didn't give any errors.

How much would it cost to repair and upgrade the installation to Plesk 9.2.2? This should happen on the cloned server first, and the production server should be upgraded later. Do you assume any liability if the upgrade fails?

In the future, we would like to use Plesk expand. Does the current version support Plesk 9.0.0? Would it be possible, to move all customers from the old server with the probably broken Plesk 8.6 to the new server with a fresh 9.x using expand?

Thanks in advance
 
Back
Top