• 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!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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. Y

    Resolved [extension/sslit] Failed to renew Panel certificate

    ＊＊＊＊＊＊＊＊ [2022-02-10 01:57:03.661] 7569:6203f25e022e3 ERR [extension/sslit] Failed to renew Panel certificate: Invalid response from https://acme-v02.api.letsencrypt.org/acme/new-order. ＊＊＊＊＊＊＊ After updating to plesk 18.0.41, these logs are recorded hourly. How can I fix this problem?
  2. Y

    Resolved Unable to update plesk18.0.39

    I was not able to be update from Plesk18.0.38Update#3 to Plesk18.0.39 using a browser. Looking at the log (/var/log/plesk/install/autoinstaller3.log), I found the error "Can't start build-in web-server". How can I solve this problem? CentOS7.9
  3. Y

    Resolved about modsecurity in fail2ban log

    After updating Plesk 18.0.35, I got a strange message about ModSecurity in the fail2ban log. However, it is not for all ModSecurity logs. Unfortunately,updating Plesk18.0.35 #Update1 dose not change. Is there any solution to this problem? ********For example***** 2021-05-09 12:22:55,456...
  4. Y

    Resolved I saw error logs in the web logs for the first time,after updating "Plesk18.0.34Update2".

    For example: ********************* [Wed Apr 07 11:04:47.536071 2021] [proxy_fcgi:error] [pid 8295:tid 140088344311552] [client ***.***.***.***:45130] AH01068: Got bogus version 51, referer: [Wed Apr 07 11:04:47.536196 2021][proxy_fcgi:error] [pid 8295:tid 140088344311552] (22)Invalid argument...
Back
Top