Recent content by Sebahat.hadzhi

@TomBoB , please try the following workaround instead: 1. Enable DMARC reject at SMTP by executing the following command: plesk bin settings -s mail_dmarc_reject_at_smtp=true 2. Execute the following command in order to apply the change to all domains plesk repair mail -y

@Jeroen Bl , thank you for your patience. We have a registered bug with ID PPPM-10046. At this point, I cannot provide an ETA for the fix or suggest a workaround. I will follow up with more details when there's an update on this case. You can also monitor the changelog here.

Thank you for the report, @uniauto . We have a registered bug for the behavior identified with ID PPPM-12524. At this point, I cannot provide an ETA for the fix. It is worth to mention that considering the users share the same UID, no major side effects concerning the site, FTP, File Manager...

Could you guys who encountered the Internal Server Error confirm what ruleset are you using? It seems the issue appears with Apache ModSecurity 2.9/Comodo (free), but our team wants to gather more information. Thanks in advance.

@Azurel , @Bitpalast , I created an internal case for the behavior to be further evaluated by our team. I will follow-up with more details as soon as possible.

Hi, @Dmytro . Please temporarily enable debug mode in Plesk, reproduce the issue one again and double-check what has been logged to /var/log/plesk/panel.log.

Assuming that you are referring to CVE-2026-42945, our team is already working on validating the impact on Nginx versions distributed with Plesk. I cannot yet provide any affirmation on an ETA for an official patch.

@safemoon , I am out of suggestions on what might be causing the issue on that particular server. I would recommend opening a ticket with Plesk support for further investigation on your server.

Hi, Peter. Could you please try adding SecResponseBodyLimit 268435456 in Tools & settings > Web Application Firewall (ModSecurity) > Settings > Custom directives?

Customizing the port is not officially supported and can lead to issues with Plesk components that rely on it. Instead, the recommended approach is to configure an additional MySQL/MariaDB server with the desired port...

Hi, Peter. I am not sure if that's related to the connectivity issue to the CloudLinux repo, but it seems like there's an issue with Rustbolit 33.3.8 itself. Could you please give a try to the workaround suggested here: https://imunify360.statuspage.io/incidents/kvvfcw1xzs40

PPP-71520 is supposed to be fixed as well. I will double-check that further with our team. Apologies for the inconvenience in the meantime.

Just wanted to follow-up and confirm that as of Joomla! Toolkit 3.0.13, the PHP version used by the host domain is selected by default instead of the latest available PHP version.

Hi, Jan. Plesk Obsidian 18.0.78 was released today with a fix for the bug: If you have automatic updates enabled, the same should be installed overnight.

Thank you for the confirmation. Unfortunately, I am also out of suggestions. I would suggest opening a ticket with Plesk support for further investigation on your server.