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

Search results

  1. N

    Forwarded to devs After upgrading to Plesk 18.0.30 apache stops randomly.

    This indeed fixes the issue for me and allows Plesk to restart the apache server again.
  2. N

    Forwarded to devs After upgrading to Plesk 18.0.30 apache stops randomly.

    I have the same issue, plesk simply doesn't seem to be able to start apache for some reason. I can restart apache via command line and everything seems to work as normal, only Plesk can't start apache. It sure can stop it though. I get the same error in the plesk repair tool, when trying to...
  3. N

    Resolved Plesk 18.0.30 and apache graceful restart

    I am not allowed to post there.. I guess we all are "new pleskians" so we all can't. The issue seems quite real though.
  4. N

    Resolved Plesk 18.0.30 and apache graceful restart

    Same issue for me, when trying to fix the installation using "plesk installer update --repatch" and "plesk repair installation" I get the same error when it tries to fix the web configurations. Ubuntu 16.04LTS, Plesk 18.0.30 Details: [2020-09-20 00:11:49.060] ERR [util_exec] proc_close()...
Back
Top