• Plesk Uservoice will be deprecated by October. Moving forward, all product feature requests and improvement suggestions will be managed through our new platform Plesk Productboard.
    To continue sharing your ideas and feedback, please visit features.plesk.com

Search results

  1. Y

    Issue Dr.Web Updater can not send HUP signal to Dr.Web daemon

    Hello, @Sebahat.hadzhi Thank you for your reply. The server was down from the evening of 8th November until the morning of 10th November. DrWeb was not work on the morning of 13th November. The log was too large, so I have extracted it. *****************/var/log/messages | grep drweb...
  2. Y

    Issue Dr.Web Updater can not send HUP signal to Dr.Web daemon

    Is this just a network common issue? For the past few days, I've been seeing this message. The error message is attached. Thanks.
  3. Y

    Resolved [extension/sslit] Failed to renew Panel certificate

    Resolved. Duplicate certificates were invalidated.
  4. 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?
  5. 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?
  6. 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...
  7. 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 --...
  8. 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
  9. 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.
  10. 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.
  11. 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.
  12. 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.
  13. 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.
  14. 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.
  15. Y

    Resolved about modsecurity in fail2ban log

    Thanks a lot. I understood.
  16. 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...
  17. Y

    Resolved Comodo failed to update

    This problem has been fixed. Thanks.
  18. Y

    Resolved Comodo failed to update

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

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

    I understand.
  20. 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