Search results

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

Thank you, @se2e-dev . Lastly, could you please confirm the Imunify extension version that currently runs on the server? Thank you in advance.

Thank you for the report, @Duarte N . I was able to replicate the behavior and will further consult with our engineers. I will follow-up with more details as soon as possible.

Thank you for the update. The second workaround suggested is to modify the DMARC record of the recipient domain: Change "p=quarantine" or "p=reject" to "p=none" at Domains > example.com > DNS Settings. I hope that helps.

Looks like a PHP bug initially reported for version 5.2: PHP :: Bug #43591 :: strange value for sendmail_path if configure can't find sendmail There's a second report, so it could very likely affect version 7.0: PHP :: Bug #78757 :: Default sendmail_path gets populated incorrectly when...

Thank you for the update. From your Plesk panel, please navigate to Imunify > the cogwheel icon at the upper right corner > Notifications. You should be able to list each one individually and confirm which are enabled/disabled.

Hello, Markus. I attempted to reproduce the issue by updating a test Ubuntu 22.04 server from 18.0.69 to the latest Plesk build, but was unable to replicate the behavior (during file uploads). Thus, I wouldn't say the issue results from the PPPM-15094 fix. However, it might still be plausible...

Everyone, thank you for your suggestion. It has been brought to the attention of our team - it will be further discussed and evaluated internally. I will provide more details on the outcome when a decision is made.

Thank you for your cooperation. Usually, it logs into the /var/log/messages or /var/log/syslog files. Let's see if the email notification you get will contain more verbose error, if not, please take a look in the aforementioned files. Thanks in advance.

Thank you for the update. I can see that you are running the latest version of Plesk, hence, I don't have any other suggestions on what might be causing the issue. The most often reason is corruption, but since you already attempted to remove the leftover files and re-install the extensions, I...

@Jens Johansson , we have a registered bug with ID PPPM-7190 regarding the issue. However, adding the domain to IgnoreMailFrom should be a viable workaround. Could you please try running: postconf myhostname and add the value it returns into IgnoreMailFrom, if not already?