cPanel recently announced the latest version update v88 with a handful of features like MySQL 8 support. It is so nice to see the much-awaited MySQL 8 support in the test version, though they have updated their internal ClamAV package and it is started to conflict with ClamAV package that is installed into the Operation System.
This change is because they have started offering one one solution by default which needs ClamAV to function. We do not have more details but the update to v88 will be blocked if you have ClamAV is installed in your Operating System. This is going to affect so many scripts and software built on ClamAV integration and depending on the default ClamAV installation. Given below is the error that you may expect during v88 update.
Error: cpanel-clamav conflicts with clamav-0.102.2-4.el7.x86_64
Error: cpanel-clamav conflicts with clamav-lib-0.102.2-4.el7.x86_64
Error: cpanel-clamav conflicts with clamav-update-0.102.2-4.el7.x86_64
Error: cpanel-clamav conflicts with clamav-filesystem-0.102.2-4.el7.noarch
cPGuard is integrated to LibclamAV and thus need ClamAV packages to function. Since this change is inevitable, we are making updates in our code and from cPGuard version 3.20 we will use a different approach and comply with this change.
So if you have cPGuard version 3.20 installed on your server, you can safely uninstall ClamAV on your server and it will not affect cPGuard functioning as we will handle it internally during the health check. Please note that it will take a while to run the health check and fix it automatically,
If you need any clarification or if you have any questions, please contact support
WordPress comes with a default job scheduler which is actually a virtual cron job using file called wp-cron.php. This is used to schedule task in order to automate things like publishing scheduled posts, checking for plugin or theme updates, sending email notifications and more. So everytime the website get a hit and you have any scheduled task is present in that website, the task is to basically ask “is it time to do anything yet?”. This can be anything like
Publishing of the scheduled posts
Plugins or Theme updates check
Sending notifications
Taking backups
WordPress automatic updates etc
How it can be a problem for your server
Of course you need to run the wp-cron.php scheduler to do some important jobs on your website like updates check and backup. But if you leave the default virtual cron job enabled, this check will happen with every hit. On a server with some low traffic websites, this is perfectly fine. But when your site visits start to increase or you have so many WordPress websites with moderate hit such a scheduled tasks check for each website can be very inefficient and lead to resource usage problems for the server, this will in turn make your website load slower. We have had a situation where the CPU load on the server has doubled only due to wp-cron.php execution on all websites.
How cPGuard manage this issue?
We have certain jobs which is collecting all informtion about the WordPress websites on your server and it keeps updating the information. So we use this information and run some logic to disable the cron job in each WordPress websites, add a cron job under the user for each WordPress installation and configure each job to run multiple times intermittently a day and the run time for the users are synchronously distributed. We carefully calculate the run time for each WordPress wp-cron ( by assigning random hours and minutes ) and thus avoid the load due to running them all together. It is perfectly fine to run the job few times a day for moderate traffic website and if any of the user wants to change the scheduled time, they can update it from their control panel. This approach will help to reduce the server load due to wp-cron.php in a large scale and efficiently run them without any overhead to your website and server.
Is it useful for everyone?
You may not find it useful if you have low number of WordPress websites on your server or the websites get rare traffic. But if you have a handful of WordPress websites with moderate traffic, this will be a cool feature and it can save lot of your server resources.
How to enable this feature?
You can enable this simply by going to cPGuard >> Settings >> Additional Settings >> Enable “Override WordPress wp-cron.php” and select the “Interval for running wp-cron.php”.
Is it possible to revert this anytime?
Of course you can …cPGuard provide options to revert the configuration updates. To revert all the changes done by cPGuard to manage wp-cron jobs, , go to cPGuard >> Settings >> Additional Settings >> Disable “Override WordPress wp-cron.php” . Please note that it will take up to a few minutes to complete the changes.
Still need clarification?
Please feel free to contact our support team anytime and we are happy to answer your questions.
We are quite happy to announce the availability of cPGuard version 3.17 for cPanel today. The exciting part of this update is the improved version of cPanel plugin interface. The enhanced version of the end user plugin is much powerful to know the entire security threat happening against their account/domain which is detected by cPGuard. Given below are the few features of the new cPanel plugin
Attack Statistics :- The end user will get a quick overview of the total attacks against their account using graphs. The graphs are powerful enough to show the attacks separately and user can understand it easily
Automatic scanner logs :- This will display the files detected by cPGuard scanner engine and its information to the user . Users also has the option to take actions against them
WAF and Brute-Force Logs :- This will display web attacks against the user domains and are detected by cPGuard WAF
Manual Scanner :- User can initiate manual scan against their files in a few clicks…they can also view the report from UI and can download the report after the scanning is completed
Custom Actions and Blacklist and Whitelist Files :- Users can set their own preferred actions, whitelist and blacklist files for the manual scan they start. This setting is applicable only for the particular cPanel user.
Brand your Security Plugin :- Yes..you can brand the plugin and present it as yours to the end user! You can change the name of the cPanel plugin, icon showing in cPanel, logo in the plugin page and the title and other texts . READ MORE about the branding..
Given below are the few screenshots of the new plugin interface for cPanel
So what is the additional features that you plan to add to the cPanel Plugin?
Our team is working on the additional features for the cPanel plugin. We will soon add the outdated WordPress or additional CMS/Plugins in their account and add this as a warning. That will let the users know about the outdated component in their account and alarm them about the security risk.
Please contact us at sales[at]opsshield.com to get custom quotes for cPGuard!
OpsShield has released cPGuard version 3 for DirectAdmin servers with all features available for cPanel plugin with some extra features added. With the latest version the release tier which is version 3.16 is coming up with CentOS/RHEL/CloudLinux 8 support.
Some of the exciting features in new cPGuard version for DirectAdmin includes the following
Revamped UI with additional graphs
Refined WAF and scanner engine
Advanced captcha engine to stop brute-force attacks again
WordPress and Joomla [will support more CMS soon ]
Central RBL based rules in WAF to stop attacks from reported IPs
SRBL support
CentOS/RHEL/CLoudLinux 8 support
Nginx and OpenLiteSpeed support etc
OpsShield is now an official vendor of the extra plugins as well and we have the software listed in DirectAdmin website now.
We are offering exciting offers for the early plugin adopters for DirectAdmin and will provide offer upto 50% discount for bulk purchases.
Please refer PRICING page to know how much the plugin costs for you.
We will keep up the development pace as we always do and provide enhanced solutions in future as well. Thanks for all your support!
