Recent content by yaswaka

Hello, @Sebahat.hadzhi Thank you for the information regarding reinstalling Dr Web. But,it appears that restarting Dr Web has resolved the issue. I shall try it should I encounter the same again.

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

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

Resolved. Duplicate certificates were invalidated.

＊＊＊＊＊＊＊＊ [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?

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

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

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

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

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

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

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.

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.

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

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.