• 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

    Resolved. Duplicate certificates were invalidated.
  2. 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?
  3. Y

    Question Laravel 8 deployment on Plesk, Artisan and NPM command execution

    Hi, butterflythemes. Does the company that provides the server allow you to use the root account of the server?
  4. Y

    Resolved Unable to update plesk18.0.39

    It's resolved. ps aux | grep installer kill -9 PID-NUMBER-FROM-YOUR-PS-SEARCH-COMMAND The process was still there when it failed, so I killed it. *********panel.log*************** Result: {"code":4,"resultCode":2,"resultDesc":"cURL cannot communicate with license server...
  5. Y

    Resolved Unable to update plesk18.0.39

    Thank you VNick and Nik G. I will try VNick's advice later. Firewall settings. ************************* #iptables -nL ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:8447 ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:8443 ACCEPT tcp --...
  6. 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
  7. Y

    Input PSA: Plesk 18.0.36 should be avoided on CENTOS / Debian / ubuntu .

    I am running Plesk18.0.36 on CentOS 7.9.2009(core) without any problem so far.
  8. Y

    Forwarded to devs Grafana extension database rights too broad and cannot load unsigned backend plugin

    CentOS Linux release 7.9.2009 (Core) Plesk 18.0.35#Update2 grafana8.0 I have the same problem.
  9. Y

    Issue Strange Apache Log Entry

    plesk support This may be a workaround. However, I don't know because I haven't changed anything and I haven't seen any strange logs today.
  10. Y

    Issue Strange Apache Log Entry

    There is not the strange apache log today. I think there was something wrong with the ownership of the file. I didn't touch it, though. The ownership of the apache logs by domain today is "root:root". I remember that was not "root:root" when the strange logs were occurring.
  11. Y

    Issue Strange Apache Log Entry

    The log format of apache is "04/Jun", not "06-04". So I don't think it is wrong.
  12. Y

    Issue Strange Apache Log Entry

    I have the same problem. I am running two domains. Only one of the domains has strange logs. Also, when I search the logs in the terminal using the search word "04/Jun", no strange logs appear. I would like to solve this problem.
  13. Y

    Resolved about modsecurity in fail2ban log

    Thanks a lot. I understood.
  14. 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...
  15. Y

    Resolved Comodo failed to update

    This problem has been fixed. Thanks.
  16. Y

    Resolved Comodo failed to update

    Hello!! I have this problem,too. CentOS7.9.2009 plesk18.0.34Update2
  17. Y

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

    I understand.
  18. 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...
  19. Y

    Issue Issue with/etc/cron.daily/logrotate after 18.0.34 upd

    CentOS Linux release 7.9.2009 (Core) Plesk Obsidian18.0.34 I am not a native speaker of English. I have the same problem. Therefore, we are running the machine with the "SELINUX" status set to "Permissive". I am waiting for your solution.
Back
Top