• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • 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.

Recent content by swagh

  1. S

    Issue FATAL_ERROR: Unable to find Plesk 17.x. Tool must be launched prior to upgrade to Plesk 18.0.31

    Thank you. I'll let you know how it goes!
  2. S

    Issue FATAL_ERROR: Unable to find Plesk 17.x. Tool must be launched prior to upgrade to Plesk 18.0.31

    Thank you! I will schedule this during off hours and let you know. I guess below command should be sufficient to restore the dump? plesk bin pleskrestore --restore "Backup-file" So, in my case, it would be: plesk bin pleskrestore --restore mysql.preupgrade.12.5.30-17.0.17.20170424-223743.dump.gz
  3. S

    Issue FATAL_ERROR: Unable to find Plesk 17.x. Tool must be launched prior to upgrade to Plesk 18.0.31

    Thanks again, @IgorG! Really helpful! I have only a couple of questions now: 1. Will this cause any downtime? 2. Do I still need to restore dump of database from 12.5 version before performing the upgrade? If yes, then I guess I should use the dump file named like...
  4. S

    Issue FATAL_ERROR: Unable to find Plesk 17.x. Tool must be launched prior to upgrade to Plesk 18.0.31

    Thank you very much, @IgorG! How can I manually upgrade to 17.5? When I try to update through GUI, it gives the option to upgrade to Obsidian 18.0.31 only. The plesk control panel also shows that the version is: Product Plesk Onyx...
  5. S

    Issue FATAL_ERROR: Unable to find Plesk 17.x. Tool must be launched prior to upgrade to Plesk 18.0.31

    Thank you, @IgorG! There seems to be a problem. ======== #cat /usr/local/psa/version 12.5.30 Debian 7.0 1205160608.10 ======== #plesk version Product version: Plesk Onyx 12.5.30 Build date: 2016/06/08 10:00 OS version: Debian 9.13 Revision...
  6. S

    Issue FATAL_ERROR: Unable to find Plesk 17.x. Tool must be launched prior to upgrade to Plesk 18.0.31

    I have fixed: ========= Plesk installation requires 'Debian/stretch/main' OS repository to be enabled. Make sure it is available and enabled, then try again. ========= by updating /etc/apt/sources.list.d/plesk-migrator.list but below error is still there: ========= Plesk pre-upgrade check...
  7. S

    Issue FATAL_ERROR: Unable to find Plesk 17.x. Tool must be launched prior to upgrade to Plesk 18.0.31

    Thanks, @IgorG, unfortunately, it is still throwing the same error.
  8. S

    Issue FATAL_ERROR: Unable to find Plesk 17.x. Tool must be launched prior to upgrade to Plesk 18.0.31

    Hi, I am facing below error while trying to upgrade from onyx 17.5.3 to "Plesk Obsidian 18.0.31 even after correcting the sources.list file: =============== Enabled repositories check Plesk installation requires 'Debian/stretch/main' OS repository to be enabled. Make sure it is available and...
See more
Back
Top