Search results

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

Hello, @WSNHosting . You can disable access to Plesk for the root user following the instructions from this article: https://support.plesk.com/hc/en-us/articles/12377737115287-How-to-disable-access-to-Plesk-for-root-or-administrator-users Do you have File2Ban installed with IP address banning...

Hello, @Gerardo Fernandez . Could you please try running the following command to repair the SSL configuration of the domain: plesk repair web -sslcerts domain.com Afterward, to make sure you are not seeing cached results, please try testing with another browser or using the incognito/private...

I am not entirely sure what specific event would trigger the execution of the file, but since it belongs to ext-notifier that would be something related to Plesk's notification system. The file in question is present on all Plesk Installations. Therefore, I can confidently confirm, it is not an...

Hello, @hypmen . It is legitime file part of Plesk modules (ext-notifier extension) and it is related to the Juicy Potato vulnerability...

Thank you for the report, @Fullscreen . The behavior is confirmed as a bug with ID EXTGIT-350. At this point, I cannot provide a workaround or an ETA for the fix. I will follow-up with more details as soon as possible.

Re-installation on a production server is not recommended. What you can try is the repair utility: plesk repair installation OR plesk repair all If you got your license from a reseller, you can raise the inquiry with them and they can forward it to our team for further investigation over SSH...

Thank you for your proposal. I am not an expect, but to me it sounds like that will require significant rework and I doubt that our team will agree to change the whole logic for a bug that can be qualified as cosmetic. Nevertheless, I forwarded your suggestion.

Hello, @Fullscreen . Could you please confirm if your setup is the same - Windows-based server + AzureDevops? Thank you in advance.

@Dmytro , does that happen independently of the issue with the disk exclusion? If yes, could I please bother you to submit it as a new bug report?

Thank you for the update, @kenthan . This doesn't sound like an issue with the extension version itself. To me, it looks like the extension catalog might be corrupted. Could you please try updating it following the instructions from this guide...