• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
    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.

Recent content by M.P.C.

  1. M

    Self-update failed, now can't connect to control panel at all - 404

    I ran the following... dpkg --get-selections | grep hold And there are no held packages on the system at all! I have no idea what is going on.
  2. M

    Self-update failed, now can't connect to control panel at all - 404

    I tried running the following as suggested... /opt/psa/admin/sbin/autoinstaller And received the following error... E: Unable to correct problems, you have held broken packages. ---X--- `apt-get` output --------------------- Reading package lists... Building dependency tree...
  3. M

    Self-update failed, now can't connect to control panel at all - 404

    Does anybody know how this can be fixed please?
  4. M

    Self-update failed, now can't connect to control panel at all - 404

    I tried the following as suggested (http://kb.parallels.com/116078)... /opt/psa/bootstrapper/pp11.0.9-bootstrapper/bootstrapper.sh repair Which failed, and I found this at the bottom of the '/tmp/plesk_11.0.9_installation.log' file... ***** problem report ***** ERROR while trying to...
  5. M

    Self-update failed, now can't connect to control panel at all - 404

    We have a Plesk install running on a server that attempted a self-update at some point, which appears to have failed. We currently have no way of accessing the Plesk Control Panel now, all we get is a 404. Please help!
Back
Top