Hi artxlb,
It’s not just your host or just you. One of my clients has the same issue so I did some searching, found your thread here and a couple others around the web, and reported detailed info from my troubleshooting efforts in this other thread – https://ww.wp.xz.cn/support/topic/give-plugin-with-icomoon-triggers-modsecurity?replies=1
The actual ModSecurity rule ID being triggered at your host might be a different number but the issue itself is likely exactly what you’re running into.
Just figured you might want to know so that you don’t drive yourself crazy or do something drastic like move your site.
HI @artxlb
Can you confirm that you are also using ModSecurity? If not, then your issue might not be related.
If you are, then please track progress of this issue on the ticket @anotherdave created here:
https://ww.wp.xz.cn/support/topic/give-plugin-with-icomoon-triggers-modsecurity?replies=1
Let me know either way. Thanks!
Thread Starter
artxlb
(@artxlb)
@ Matt Cromwell
I am not using ModSecurity.
But I did share your previous post with my hosting service. They are suggesting that I move to one of their other servers with the latest PHP version. As a temporary fix they have whitelisted the security rule that was dropping my connection.
###Triggered rule###
220030 COMODO WAF: Vulnerability in PHP before 5.3.12 and 5.4.x before 5.4.2 (CVE-2012-1823)
###
Thanks,
@artxlb
“220030 COMODO WAF: Vulnerability in PHP before 5.3.12 and 5.4.x before 5.4.2 (CVE-2012-1823)”
Is a ModSecurity rule.