Unable to upgrade/install Plesk on Ubuntu/Debian: the following packages have unmet dependencies

Follow

Comments

6 comments

  • Avatar
    Sam Smith

    Hi How can I do this in Debian 8?  Any solution please

    0
    Comment actions Permalink
  • Avatar
    Ivan Postnikov

    Hello Sam Smith

    In your case update doesn't work because Debian 8 has reached End-of-life.

    The recommendation is to perform migration to a server with a newer update: https://support.plesk.com/hc/en-us/articles/213912645

    Alternatively, perform dist-upgrade first: https://support.plesk.com/hc/en-us/articles/213410369.

    The 2nd option is considered as riskier and a server snapshot before upgrade is recommended.

    0
    Comment actions Permalink
  • Avatar
    Swapnil Wagh

    Hi @...,

    I am facing this error 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 enabled, then try again.
    Plesk pre-upgrade check
    FATAL_ERROR: Unable to find Plesk 17.x. Tool must be launched prior to upgrade to Plesk 18.0.31 for the purpose of getting a report on potential problems with the upgrade.
    =============

    Current Plesk version is Version 17.5.3. I am upgrading to "Plesk Obsidian 18.0.31".
     
    Would you or someone else please help?
    0
    Comment actions Permalink
  • Avatar
    Cees Velt

    What ever I do, I can not get Plesk installed on the right way on Ubuntu 20.04. The repositories don't work, the scripts don't work. I am getting very simple of just an install. Why is there not one single install that ever works on a Linux variant? Is there some one who is having Plesk running on Ubuntu 20.04 without problems and so, what did you do?

    0
    Comment actions Permalink
  • Avatar
    Yosef Chaim Yom Tov

    I have a similar problem in CENTOS

    0
    Comment actions Permalink
  • Avatar
    Stefan Yakubov

    Hello, @Yosef Chaim Yom Tov

    Since CentOS uses a completely different package manager, the the error will be non-identical. At this point, I'd recommend searching it against the KB or creating a support ticket.

    0
    Comment actions Permalink

Please sign in to leave a comment.

Have more questions? Submit a request