Search results

The path to the file is /opt/drweb/update.pl.

@W4ru , to me it looks like the IP address is not present in the config file at all. What you can try is to add it manually: dhcp4: true addresses: - 2001:8d8:abcd:1234::2/64 (where 2001:8d8:abcd:1234::2/64 stands for your IP and mask ) However, if you already opened a...

I don't think the warning should be causing the issue you are describing, but you can disable OCSP stapling in domains > domain.com > SSL/TLS certificates. Have you tried matching the default values of Nginx caching settings?

Thank you for the confirmation. Please monitor the behavior and let us know if the issue continues.

Hello, @Pascal_Netenvie . Are your Nginx caching settings different than the default values? If yes, kindly try adjusting them for the sake of testing. Also, please check the syntax of Nginx's config by running the following command: nginx -t

Hello, @MariuszB . Could you please check the dovecot service status and let us know if you see any additional entries: systemctl status dovecot.service As far as I am aware, the issue could be related to the default_vsz_limit, thus, you might try increasing it according to the instructions...

@chris-design , I got an update from Dr.Web's team. They state that they see a timeout while downloading from update.geo.drweb.com (unfortunately, still don't have an exact IP address ). Considering that the preceding download operation from the same host appears to have completed successfully...

Thank you for the update. Do you have Firewall enabled on the server in question? If yes, could you please confirm the status of the "IPv6 Neighbor Discovery" rule? Additionally, could you please run the following command and provide us with the output: ip6tables -L -n -v

You are absolutely right. However, WP-Toolkit should not initiate the integrity check unless manually started. Regarding the backup process, it is recommended to have available local storage equal to the largest two subscriptions, because while the first backup is being transferred, the second...

Hello, @W4ru . Is the correct IP address selected in "Domains -> domain.com -> Hosting & DNS -> Web Hosting Access" for the website you are unable to access?

My personal guess is that the extension catalog got corrupted by some reason. However, since you already tried re-installing it and that did not solve the issue, unfortunately, I am out of suggestions what else you could try. It will be best to consider getting in touch with Plesk support for...

Hello, @jasperNL . No updates related to Monitoring/Grafana occurred in the past few days, as far as I am aware. My other guess was the issue might be related to the Cgroups service, but since the rest of the stats are shown that might not be issue. Nevertheless, I am glad to hear the issue is...

Thank you for the update, @chris-design . I forwarded the entries to our point of contact on Dr.Web's end. I will follow-up with more details as soon as we get an update on this matter.

Thank you for the report, @peterluit . WP-Toolkit should report the correct version of the plugin. I was able to replicate the issue and I will forward it to our team. I will confirm once we get an update from Patchstack the issue is sorted.

Hello, @jasperNL . Are you by any chance using LiteSpeed on the server in question?

Thank you for the update, @kenthan . There is no known issue with similar symptoms. For what is worth, I also cannot replicate the issue on a test environment, which suggests it is very likely something related to the local server environment. The best next option is to consider getting in touch...

Thank you for the update. Could you please also check if the correct IP address is selected according to this article: https://support.plesk.com/hc/en-us/articles/12378120882199-A-website-hosted-in-Plesk-uses-an-old-SSL-certificate-or-is-not-accessible-via-HTTPS-ERR-CONNECTION-RESET

Hello, our team is still reviewing the case. Unfortunately, I cannot yet provide an ETA.

Thank you for the update and confirmation. I spoke with the CloudLinux team and they informed me that the entry is likely logged due to the Imunify agent sending a generic notification, which is not supported by the current extension version. That will be introduced in the upcoming Imunify...

Hello, @B_P . Neither Plesk nor WP-Toolkit should interfere with the website files. You can temporarily detach the affected website(s) from WP-Toolkit to further monitor the situation. However, I doubt the issue is caused by it. The most common reason for such issues is website exploit. Do you...