New in CWP Edge-LatestFree with every CWPpro licenceWebsites up to 300x faster

CWP now includes LSPHP, LSAPI-Cache and CWP Cage at no extra cost with all CWPpro licences. The LSAPI-Cache plugin is integrated into our WordPress and other script installers, and CWP Cage gives every user complete isolation. Available now in the CWP Edge-Latest version.

Get CWPpro ›

MOD SECURITY issue on new CWP PRO INSTALLATION

Started by zeejdeej, September 08, 2024, 05:49:43 PM

Previous topic - Next topic

zeejdeej

hello,

i have recently installed CWP pro on a new Almalinux 9,everything is working fine but when i install MOD Security all the websites goes down and give below error: when i uninstall MOD Security all sites start working fine. what could be wrong ? and how to fix it any suggestions plz

Unable to connect

An error occurred during a connection to 38.242.244.140.

The site could be temporarily unavailable or too busy. Try again in a few moments.
If you are unable to load any pages, check your computer's network connection.
If your computer or network is protected by a firewall or proxy, make sure that Firefox is permitted to access the web.


BeZazz

Does anything show up in the logs under Mod Security or your Apache log files?



zeejdeej

thanks a lot guys it worked after adding the following line :

LoadFile /usr/lib64/liblua-5.4.so

but now mod security is giving forbidden access to all the websites pages.

the main page is opened but when i click on any other link on website it triggers the mod security rule i am using comodo waf rules. how to fix forbidden access issue now . :) 

any suggestions

cyberspace

The simplest way is to disable mod_security :)

The correct way is to check mod_security logs, identify the blocking rule and disable it or modify according to the requirements of your site. Look here:
https://wiki.centos-webpanel.com/mod_security-for-cwp
to learn how to do this.

Starburst

Which ruleset are you using?

Comodo is at 1.241 that has fixes in it for WooCommerce.
The ones CWP installs are 1.240.

OWASP isn't bad, but isn't good either.
It seems to gives ALOT of false positives.

Starburst


zeejdeej

my cwp pro is stuck at comodo waf v 1.240 i tried many times to update to v 1.241 manually by replacing the waf rules files but it revert back to v. 1.240 most probably due to cwp automatic update cron job.

i tried to switch to OWASP latest but as you said it had too many false positives and even after fine tuning i am not able to keep my hosted website unblocked.

i want to try atomic crop free waf rules as i heard they are good and atleast updates once a month and have lesser false positives? have you tried it? any suggestions

zeejdeej

i think cwp should consider integrating atomic crop. free waf rules in cwp panel so everyone can benifit using it . manual installation and configuration have too many errors and conflicts as cwp got custom configuration only cwp panel admins knows best.