WHM ModSecurity Scripts not working after upgrade

AM2015

• June 21, 2015 02:03

Upgraded to 11.50.0 (build 12) Now, in the Security Center, if I click links to "Mod Security Configuration", "ModSecurity Tools", or "Mod Security Vendors" -- I simply get a single line: Results of Your Request No other data or form interface is displayed. This is a problem because I need to be able to view the ModSecurity logs. ModSecurity function still seems to be fine (I can see logs via phpMyAdmin) -- but the logs and other tools do not showup in the CPanel interface.

• 

  quizknows

  • June 21, 2015 14:53

  I have the same version (11.50.0 (build 12)) and all the ModSecurity pages seem to be functioning. I would submit a ticket if I were you. Alternately you could try a "/scripts/upcp --force" to make sure everything is (re)installed correctly.

  0
• 

  AM2015

  • June 22, 2015 08:02

  Thanks -- I did try a force update and the problem remains. OS is CentOS 6.6 if that makes a difference. I've put in a support request with my hosting company for now. I also use the Comodo WAF plugin for mod security rules -- don't know whether that could creates some sort of conflict. (I am using the plugin rather than the vendor subscribe option, as there are more customization options available via the plugin). Just providing this info in case anyone else runs into similar problems.

  0
• 

  quizknows

  • June 22, 2015 18:45

  I hope they get it worked out for you. I use the Comodo rules off and on for testing, and haven't noticed it cause this issue, but thanks for providing the information.

  0
• 

  AM2015

  • June 24, 2015 04:43

  The problem is now resolved -- I submitted a support request to CPanel and am very impressed with the fast response I got. The problem appears to have been caused by the /root/.whmtheme file -- removing that file resolved the problem. (Posting in case anyone else runs into a similar issue)

  0
• 

  cPanelMichael

  • July 13, 2015 12:55

  The problem appears to have been caused by the /root/.whmtheme file -- removing that file resolved the problem.

  
  Hello :) I am happy to see this issue is now resolved. The /root/.whmtheme file defined an invalid theme name, so removing it addressed the issue by ensuring the use of the default WHM theme. Thank you.

  0

Please sign in to leave a comment.