@sandeep I have just written the necessary data through your profile chat.
Hi @sandeep, I've got something else today, the server is running and working like a charm, but when I install ModSecurity and enable OWASP or COMODO rules, if I try to work in the site everything stops working properly... First 403, then Uploading files..., then database migration..., then wordpress...
What I did was to to white list some of the rules I was finding in ModSecurity log by its ID, for example:
SecRuleRemoveById 980130 SecRuleRemoveById 949110 SecRuleRemoveById 941100 SecRuleRemoveById 911100 SecRuleRemoveById 920350 SecRuleRemoveById 913100 SecRuleRemoveById 920280
I haven't even started to work full on the site, I'll I have been doing is setting it up and all these trouble......!!
My real question is how can I better handle ModSecurity, so all my sites don't get all these false positive?? is there a known false positive list, just to add and let it be?? Can I just white list IP's, my IP and the servers IP maybe??.
Thanks in advance.
PS (IT'S UNINSTALLED FOR NOW..!!)
We work with the rules of comodo and what we do is teach customers to disable rules that affect them. So far we have no problems and they are managing themselves
This Saturday we had a very serious problem due to "CWP's fault".
I create a package and a reseller account for customers who buy a VPS, from there they manage all their customers.
The problem comes from the fact that in the reseller section, the data of space used is not correct, the server was occupying about 250GB and in the reseller section it indicates that it was using about 150GB. This caused the server to run out of space and the customer did not have time to notify us to make an extension. All their clients' websites were down with all the negative repercussions that this has.
Do you have any workarounds while this is being corrected in CWP?
I opened the ticket: #776512
@sandeep Does this only apply to those who have already converted to centos 8 streams, or does it also apply to the normal centos 8?
nginx 1.18.xx is still latest and stable.
Yes yes, let's see... hahaha I make your manual and I update it well to 1.18.
But in the servers (I don't know the reason) by default it installs "I think" that the version 1.14 or something like that the clients comment me.
That is, to update it, you need my intervention. Shouldn't the latest version come by default?
Yes, this has been reported to head developer already, Probably after the bug fixes he will fix this.
I'll post the solution today in new forum topic or in blog post.
Some customers report to me that when they use a web site to test their web, it tells them that nginx is out of date.
Do you know when this will be fixed at the CWP level?
I've noticed that I don't get that error anymore, but it seems that the user level cron is not running on the server. Do you have any idea where the problem might be?
Now the log shows this:
Jan 5 11:05:01 centosweb CROND: (larrain) CMD (wget http://www.*************.com/modulos/PHPMailer/examples/backupmysql.php )
Selinux appears to me like this:
I see user references in these files:
But in this file:
I only see reference to 4 users on the server, root and three others. Is this normal? How should I fix it? I see the reference to a user and a kind of encrypted password.