Skip to main content

mod_security not working

Comments

7 comments

  • cPRex Jurassic Moderator
    Hey hey! Is it possible there just isn't anything noteworthy that is tripping ModSecurity? The only way to know for sure would be to send a request to the server that is specifically designed to trip a rule.
    0
  • cPRex Jurassic Moderator
    Try something like this with one of your domains to see if this trips a rule: curl -A 'paros' https://domain.com curl -s http://domain.com/?../../../../etc/passwd
    0
  • Jeff P.
    I did many times, nothing happened and our server gets plenty of traffic, but I have empty logs.
    0
  • cPRex Jurassic Moderator
    It definitely sounds like something is up then. Could you submit a ticket to our team so we can check this out?
    0
  • Jeff P.
    Will do, thx
    0
  • cPRex Jurassic Moderator
    If you're able to submit a ticket, please post the number here so I can follow along and post the solution once it is resolved.
    0
  • kdean
    On the off chance this helps. About a year ago, my ModSecurity that had been previously working all of a sudden stopped working. While investigating I discovered that /etc/apache2/conf.d/modsec/modsec2.cpanel.conf was empty and I was pretty sure it wasn't supposed to be empty and I never touched it. So, I went to WHM > Security Center > ModSecurity" Configuration. I figured maybe if I just resave the config here but Save is greyed out unless you make a change. So, I changed "Connections Engine" to "Process the rules" and saved and then set it back to "Do not process the rules" and saved. Now the modsec2.cpanel.conf had content in it again and my user rules and atomicorp rules started working and logging again. So check that particular file to make sure it's not empty just in case since it can stop the whole thing from working.
    0

Please sign in to leave a comment.