Search results

Update Plesk to the latest update then. This feature is only available on Plesk 18.0.52 and higher.

You need to choose DENY (DENEGAR) instead of ALLOW (PERMITIR) ;)

Take a look here: https://support.plesk.com/hc/en-us/articles/12377285410839-How-to-block-or-whitelist-specific-countries-through-Plesk-

With the Plesk firewall, you can block a bunch of countries using the ISO 3166 country codes , all ports (incoming) and place the deny rule at the top. This way, you will block incoming traffic for the websites and email.

The Workaround II work only for Websites, not email.

You need to use the Plesk Firewall. Yes, the Workaround I is not available anymore, as the extension is not available anymore. For more information regarding the Plesk Firewall: (Plesk for Linux) The Plesk Firewall

To install the Plesk Firewall, take a look here: https://support.plesk.com/hc/en-us/articles/12377540171799-How-to-install-Plesk-Firewall To block a country through the Plesk Firewall, take a look here...

Maybe because the Workaround II, it only blocks the access to the Website, not mail. You must use the Plesk firewall.

Try: MYSQL_PWD=`cat /etc/psa/.psa.shadow` mysql_upgrade -uadmin

I can confirm that the problem has been resolved by following the steps mentioned here: https://support.plesk.com/hc/en-us/articles/14193588345495 I can also confirm that I skipped step 7 and passed directly to the step 8, but I have executed only the first cmd: DELETE FROM Instances where...

Hello, You can close this thread. I'm using OWASP + ModSecurity 3.0 and it works fine at the moment.

I am attaching all the errors for you to better understand the problem. They are mainly linked to WP installations (temporary domain name), which no longer exist in Plesk.

Ok @Peter Debik I have tried this as mentionned, but I'm stuck in the step 7 When I copy/paste this cmd select instanceId from InstancesDomains where domainId=XXX; in order to get the instanceId, nothing happen (no output is showing). :/

Error messages: 0; Warnings: 0; Errors resolved: 0 Apparently there is no problem here.

Sure. In my case, I use WP as CMS. So, I added this on functions.php: // Send email via SMTP add_action('phpmailer_init', 'send_smtp_email'); function send_smtp_email( $phpmailer ) { $phpmailer->isSMTP(); $phpmailer->Host = SMTP_HOST; $phpmailer->SMTPAuth = SMTP_AUTH; $phpmailer->Port =...

@Peter Debik , sure. I have have enabled Modsecurity 3.0 and I'm using everytime PHP-FPM served by nginx, no problem at all. For the predefined set of values, I have choose FAST as the 2 others parameters cause a lot of troubles (false/positives)

Hello @IgorG , You can now mark this thread as resolved, thanks.

You can now mark this thread as resolved, thanks.

Hello @Maarten. , You can now mark this thread as resolved, thank you.

Thank you guys. You can now mark this thread as resolved, thanks.