• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Issue Using atomic corp rules for modsecurity but updating page via elementor doesn't work and gives internal server error.

hamza-24

Basic Pleskian
Server operating system version
centOS 7
Plesk version and microupdate number
18.0.56 #4
Hey everyone
i have enabled modesecurity for my website using atomic corp rules.
but when I update something on website using elementor keeping modsec on it gives me internal server error.
if I turn off modsec and update it works fine.
but I want to resolve this with modsec on.
your help will be highly regarded
 
When ModSecurity steps in, it logs a 403 error to the error_log of the domain. Such an entry looks similar to
Code:
[client <IP Adresse>] ModSecurity: [file /etc/httpd/conf/modsecurity.d/rules/tortix/modsec/50_plesk_basic_asl_rules.conf"] [line "258"] [id "33350147"] [rev "143"] [msg "Protected by Atomicorp.com Basic Non-Realtime WAF Rules: Potentially Untrusted Web Content Detected"] [data ""] [severity "CRITICAL"] Access denied with code 403 (phase 2). Match of "rx ((?:submit(?:\\\\+| )?(request)?(?:\\\\+| )?>+|<<(?:\\\\+| )remove|(?:sign ?in|log ?(?:in|out)|next|modifier|envoyer|add|continue|weiter|account|results|select)?(?:\\\\+| )?>+)$|^< ?\\\\??(?: |\\\\+)?xml|^<samlp|^>> ?$)" against "ARGS:actions" required. [hostname "<Domain>"] [uri "/wp-admin/admin-ajax.php"] [unique_id "YGd3IS-RaDMGEBt0BJbDcABAAAn"], referer: https:// <Domain>/wp-admin/post.php?post=24&action=elementor
You can see the
Code:
... ne "258"] [id "33350147"] [rev "1 ...
[id ...] section in that message. This is the id of a rule that is applied that leads to the 403 error. You can copy the rule id and add it as an exception to the "Web Application Firewall" exceptions. This way you can leave ModSecurity on while the rules that previously caused the permission ban error on your website won't apply any longer.
 
Back
Top