Search results

@Zalem Citizen As previously mentioned, CloudLinux is are aware of the issue and working on fixing it. However, I cannot provide any ETA on when that will be fixed. At this time, you can safely ignore the warnings. @Tjerk Visser the issue you are reporting about Dr Web's update is significantly...

Hello, @Michael.P . Imunify360 is a third-party product and it is maintained by CloudLinux. The warnings you get are related to their repositories. As previously mentioned, they are aware of the issue and working on fixing it. However, I cannot provide any ETA on when that will be fixed. At this...

Thank you for the clarification. Could you please confirm if the subscription you are testing belongs to a regular user or to an administrator? I ran a few additional tests (including on Debian 11) and unless the subscriber was changed to a regular customer, running the repair utility made no...

Hello, @yohanr . From what I can see the error you are getting is related to CloudLinux's repository. They are aware of the issue and a fix should be introduced soon. You may apply the workaround mentioned previously:

@B_P Apologies for any possible confusion caused. You are right. Our team applied the upstream patch for RoundCube 1.16, and updated it in order to be compatible with 1.14.x. I edited my previous reply to clarify that.

Thank you for your update. In this case, it's safe to conclude that it was due to temporary connectivity issue on Dr. Web's servers.

Essentially, yes. MySQL will listen for connections on all network interfaces.

Yes, this is in reference to the "Hosting performance settings management" permission only.

Thanks for testing that, Kaspar. I discussed the case with our team and according to them if there were no changes on the settings after the upgrade to version 18.0.70, the configuration likely wasn't regenerated. @Hangover2 , please run the repair utility for domain names you are testing. In...

I just want to confirm that along with Plesk Obsidian 18.0.70 Update 1 our team applied the upstream patch for Roundcube 1.4.15 and 1.6.10 to fix the CVE-2025-49113 vulnerability. It should be automatically updated on Plesk Obsidian 18.0.69 and 18.0.70. If you are running an older Plesk...

It shouldn't matter whether it is a dedicated application or not as long as it is PHP-FPM. I am able to reproduce the behavior following the steps from your initial report. I will double-check with our team in case I misunderstood something with that last update.

Thank you for the update, @Goncharenko . I attempted to reproduce the issue on a test Ubuntu 24.04 environment, but when running the update task manually doesn't produce the said error. Could you please give it a go and let me know:

Sorry about that. I did not notice the faulty formatting. Thanks for pointing that out. I edited my reply.

Could you please try fetching and installing the key: wget -q -O - http://autoinstall.plesk.com/plesk.gpg | gpg --dearmor > /etc/apt/keyrings/plesk-ext-grafana.gpg

Thank you for the update. Could you please try fetching and installing the key: wget -q -O - http://autoinstall.plesk.com/plesk.gpg | gpg --dearmor > /etc/apt/keyrings/plesk-ext-grafana.gpg

Everyone, the issues with PHP 7.4 and PHP 8.0 and the signing keys should be sorted. Our team released an update: Please let us know if you continue encountering any errors/warnings.

Everyone, the issues with Grafana, PHP 7.4 and PHP 8.0 and the signing keys should be sorted. Our team released an update: Please let us know if you continue encountering any errors/warnings. I cannot provide any ETA for CloudLinux's repositories, at this point.

The issue with Grafana should be sorted out now. Please do let us know if you continue encountering any errors or warnings.

Hello, @paolotrombini25 . The issue could be due to a corruption of the Fail2Ban component. Could you please re-installing it by applying these steps: https://support.plesk.com/hc/en-us/articles/27658444801943-Cannot-open-IP-Address-Banning-Fail2Ban-in-Plesk-panel-No-section

There is no built-in feature that allows you to configure a forwarder on a per-domain level that will allow you to forward emails from the corresponding mailboxes, i.e from mail1@example1domain.com to mail1@example2domain.com. There's an open request you can vote for here. As a workaround, the...