In MainWP plugin I have set “no schedule” in Vulnerability checker extension.
But in cronjob “mainwp_cron_vulner_recheck” runs every hour.
I have changed in cronjob to “no repeat” but it changes back to “hourly” check.
How can I disable automatic vulnerability checks in cron?
@alainL When you say you changed the cronjob to “no repeat” is this with this plugin ?WP Crontrol – WordPress plugin | WordPress.org
Can you please post the community system report from your MainWP Dashboard for review? The report is located in your Dashboard under Status → Server, on the top right of the page.
Be sure to use the button like the one below; this button hides all your private information:
Pressing the button auto-copies the report to your clipboard then just paste it in a reply here.
Yes sure:
### Server Info Required Detected Status ###
MainWP Dashboard
MainWP Dashboard Version 4.1.10.3 4.1.10.3 Pass
MainWP Upload Directory Writable Writable Pass
MainWP Extensions
Activity Log for MainWP 1.7.0
Advanced Uptime Monitor Extension 5.2 API License Active Pass
MainWP White Label Extension 4.1 API License Active Pass
MainWP Bulk Settings Manager Extension4.0.3 API License Active Pass
MainWP Clean and Lock Extension 4.0.1.1 API License Active Pass
MainWP Clone Extension 4.0.1 API License Active Pass
MainWP Comments Extension 4.0.3 API License Active Pass
MainWP File Uploader Extension 4.1 API License Active Pass
MainWP Google Analytics Extension 4.0.3.2 API License Active Pass
MainWP Maintenance Extension 4.1 API License Active Pass
MainWP Page Speed Extension 4.0.1.1 API License Active Pass
MainWP Pro Reports Extension 4.0.6 API License Active Pass
MainWP Rocket Extension 4.0.2 API License Active Pass
MainWP Staging Extension 4.0.1 API License Active Pass
MainWP UpdraftPlus Extension 4.0.4 API License Active Pass
MainWP Vulnerability Checker Extension4.1 API License Inactive Warning
MainWP WooCommerce Shortcuts Extension4.1.1 API License Active Pass
MainWP WooCommerce Status Extension4.0.6 API License Active Pass
MainWP Wordfence Extension 4.0.4 API License Active Pass
WordPress
WordPress Version >=3.6 5.8.2 Pass
WordPress Memory Limit >=64M 256M Pass
MultiSite Disabled =true true Pass
FileSystem Method = direct direct Pass
PHP
PHP Version >=7.0 7.4.26 Pass
PHP Safe Mode Disabled =true true Pass
PHP Max Execution Time >=30 seconds 120 Pass
PHP Max Input Time >=30 seconds 300 Pass
PHP Memory Limit >=128M 256M Pass
PCRE Backtracking Limit >=10000 1000000 Pass
PHP Upload Max Filesize >=2M 64M Pass
PHP Post Max Size >=2M 64M Pass
SSL Extension Enabled =true true Pass
SSL Warnings = empty Pass
cURL Extension Enabled =true true Pass
cURL Timeout >=300 seconds 300 Pass
cURL Version >=7.18.1 7.29.0 Pass
cURL SSL Version >=OpenSSL/1.1.0 NSS/3.53.1 Pass
PHP Allow URL fopen YES
PHP Exif Support YES ( V7.4.)
PHP IPTC Support YES
PHP XML Support YES
PHP Disabled Functions opcache_get_status,
PHP Loaded Extensions Core, PDO, PDO_ODBC, Phar, Reflection, SPL, SimpleXML, Zend OPcache, bcmath, bz2, calendar, cgi-fcgi, ctype, curl, date, dba, dom, enchant, exif, fileinfo, filter, ftp, gd, gettext, gmp, hash, i360, iconv, imagick, imap, intl, ionCube Loader, json, ldap, libxml, mbstring, mysqli, mysqlnd, odbc, openssl, pcre, pdo_mysql, pdo_pgsql, pdo_sqlite, pgsql, posix, pspell, redis, session, soap, sockets, sodium, sqlite3, standard, sysvmsg, sysvsem, sysvshm, tidy, tokenizer, xml, xmlreader, xmlrpc, xmlwriter, xsl, zip, zlib
MySQL
MySQL Version >=5.0 10.3.32-MariaDB Pass
MySQL Mode ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION
MySQL Client Encoding utf8
Server Info
Server Software Apache
Operating System Linux
Architecture 64 bit
Server Protocol HTTP/1.1
HTTPS ON
Server self connect Not expected HTTP response body:
User Agent Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/15.1 Safari/605.1.15
Gateway Interface CGI/1.1
Memory Usage 79.57 MB
Request Time 1638432717
Accept Content text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Charset Content N/A
MainWP Settings
Number Of Child Sites 43
Use WP-Cron Yes
Optimize for Shared Hosting or Big NetworksNo
Automatic Daily Update Install trusted updates
Abandoned Plugins/Themes Tolerance 365
Maximum number of posts to return 50
Maximum number of pages to return 50
Maximum Number of Comments 50
Primary Backup System MainWP UpdraftPlus Extension
Maximum simultaneous requests 4
Minimum delay between requests 200
Maximum simultaneous requests per ip1
Minimum delay between requests to the same ip1000
Maximum simultaneous sync requests
Maximum simultaneous install and update requests
Active Plugins
Activity Log 2.8.1 Active
Activity Log for MainWP 1.7.0 Active
MainWP Dashboard 4.1.10.3 Active
MainWP Key Maker 1.2 Active
UpdraftPlus - Backup/Restore 2.16.66.25 Active
Wordfence Security 7.5.7 Active
WP Crontrol 1.12.0 Active
@alainL Hey thanks for the info - Reading over it everything looks fine except I noticed that your API Key for the MainWP Vulnerability Checker is inactive - do you happen to have the latest v4.1 installed?
What plugin or means did you use to edit your cron jobs?
I am completely lost now. I am struggling from the beginning with this extension.
I filled in a new API key but still it says inactive. Why?
Yes I have version 4.1 and I use WP Crontrol to edit cronjobs.
@alainL OK - I understand your frustration. Please keep in mind that I am just trying to collect specific information from you & go through the normal process of elimination in order to figure out why.
During my testing changing the Cron Schedule via WP-Control doesn’t work because the MainWP Vulnerability plugin sets this internally.
Last dumb question - Have you tried to disable it via it’s settings page?
If that isn’t the cause then I would rather have you open a ticket so we may connect & check it for you? Feel free to do so here: Support - MainWP WordPress Management
Yes this is disabled. Now I created a new API key and I can’t activate this API key in the extension.
I checked the API key and its working when I do a wpscan in Linux. Only this extension is the problem.
@alainL I will alert the dev team that the disable function might not be functioning correctly.
As for the API Key - I just tested this and it works fine. Try again - there may have been an issue with WPScans servers.
I just tested in Linux and did a wpscan. Nothing wrong with their servers. It works in Linux.
Only this WPVulndb extension does not work. I can not activate my API key.
I am not able to replicate what you are describing.
I am sure they have more then one server to handle the load. It has also been reported that this fails at times.
Please open a ticket so that we can check your system further.
Yes I have send a ticket with necessary login details to investigate issues.
Today I could reconnect my API. That works again.
I did a new vulnerability scan and this works as well.
Only there are no API requests on my wpscan.com account after I did the scan.
I tried Force Recheck and it works again 
Not sure what was causing the issue but it seems to work again.
Now I will keep an eye if automatic scans stays disabled.
@alainL Glad things are working again - Like I said above:
This is known behavior that has been reported and unfortunately, there is nothing we can do about it on our side as we do not control their servers. This issues reported are also not replicable on our side.
If the auto scans do not stay “disabled” we will definitely be looking into why this is happening and provide a fix asap. Keep in mind during my testing I noticed that even though you have the Extension Settings set to Disabled WP-Control will still state that its set - I believe this is normal behavior as the cron job fires off the function that checks this WP_options setting and if disabled it should skip the scans.
Thank you very much for your patience and updated reporting - Please let us know how you make out.
This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.
