Known issue with Comodo ModSecurity updates

rscalover

• December 08, 2020 02:11

Hello, Received an email " cPanel & WHM update failure in upcp script " upon investigation i found in the last cPanel / whm updatelog this [2020-12-08 00:56:16 +0100] - Processing command `/usr/local/cpanel/scripts/modsec_vendor update --auto` [2020-12-08 00:58:27 +0100] [/usr/local/cpanel/scripts/modsec_vendor] The system failed to update the vendor from the URL "https://waf.comodo.com/doc/meta_comodo_apache.yaml": The system could not download the file "https://waf.comodo.com/doc/meta_comodo_apache.yaml": curl: (7) Failed connect to waf.comodo.com:443; Connection timed out [2020-12-08 00:58:27 +0100] [/usr/local/cpanel/scripts/modsec_vendor] [2020-12-08 00:58:27 +0100] E [/usr/local/cpanel/scripts/modsec_vendor] The "/usr/local/cpanel/scripts/modsec_vendor update --auto" command (process 21511) reported error number 1 when it ended. [2020-12-08 00:58:27 +0100] The Administrator will be notified to review this output when this script completes [2020-12-08 00:58:27 +0100] - Finished command `/usr/local/cpanel/scripts/modsec_vendor update --auto` in 130.523 seconds
as i understand that error message cPanel is innocent here it looks like that commodo service is down correct or ...... ?.

• 

  JamasWise

  • December 08, 2020 13:32

  I am seeing the same thing. It looks like the Comodo website is offline again. This happened a few years back for a few days. At the time there was concern that this free rule set was being removed due to a change of ownership. It resolved itself at that time in a few days. I hope this will be the case this time.

  0
• 

  cPRex Jurassic Moderator

  • December 08, 2020 13:34

  Hey there! Currently there is an issue with the ModSecurity provider's update servers that is outside of cPanel's control. We're tracking this on our end and I'll be sure to post a message here as soon as we receive an update.

  0
• 

  cPRex Jurassic Moderator

  • December 09, 2020 12:35

  Alright - Comodo has resolved this issue so you shouldn't see updates fail with the same problem at this point. If you still see problems I'd recommend forcing an update with the "/scripts/upcp --force" command.

  0

Please sign in to leave a comment.