Hi @nokao,
In order for us to get some context could you tell me if this started to happen right after you updated Wordfence? Or maybe another component?
If you go to the Wordfence –> Tools –> Diagnostics page do you see “wordfence_start_scheduled_scan” jobs in the Cron Jobs section?
-
This reply was modified 6 years, 5 months ago by
wfyann. Reason: Misspelling
Yes, this massively-happened after updating the plugin.
Like if the option of “not scheduling scans” or “not scanning” was lost somehow.
We don’t like that because we have to run a massively “empy and delete Wordfence saved data” with the “Wordfence assistant plugin” when this happens, because there is no need for this data to be stored because we do Scans elsewhere.
Of course we like and love Wordfence, but we use it “in a different way” than others.
This is what you asked:
Tue, 14 Nov 2017 13:30:00 +0000 wordfence_start_scheduled_scan
Fri, 17 Nov 2017 13:30:00 +0000 wordfence_start_scheduled_scan
This is in our log… is it related ?
– – 13/Nov/2017:12:35:20 +0100 “POST /wp-cron.php?doing_wp_cron=1510572920.7127110958099365234375” 200 []wp-cron.php 395.474 41984 83.44%
Can you confirm that if I do again all configurations with “auto scan” = false,
this choice will be mantained in al future releases ?
I will then re-configure all websites and truncate al tables content again …
Hi @nokao,
Sorry about the delayed response.
I wasn’t able to reproduce the issue you described; on my test site, if “Enable automatic scheduled scans” was off, updating Wordfence didn’t cause the option to switch on (on its own).
I will discuss this further with the development team.
In the meantime, what I suggest (once you disabled the feature) is to install the WP Crontrol plugin in order to delete all “wordfence_start_scheduled_scan“ cron jobs.
Please make sure not to delete any other jobs than those specific ones.
This is happening again !!!
- I started from scratch
- I activated and imported this options that have scheduled scans disabled: d160e753200a52eba09773de533654f89b2eefd6a538c6238a18f9423ea79603a9fa408941e42eba2a303952727017b8c2a2f05fcf746623cad5a0477b4bb11f
- After 3 days I find again the websites scanning
- I also find scheduled scans in the backend:
Mon, 27 Nov 2017 21:30:01 +0000 wordfence_start_scheduled_scan
Tue, 28 Nov 2017 08:00:00 +0000 wordfence_start_scheduled_scan
Thu, 30 Nov 2017 21:30:01 +0000 wordfence_start_scheduled_scan
Please help me to understand how to install Wordfence in a brand-new website,
import a working options token,
and to NOT have a scheduled scan running after a few days filling my tables.
I want to use Wordfence, but I don’t want tables to fill with Wordfence data.
I’m scanning with another installation of Wordfence elsewhere (+scan files outside wordpress option) and also with server-side malware scanners.
This is terrible, scheduled scans are enabled by default !!!
I self-DDoS-ed myself by performing 200 Wordfence Scans toghether today,
a whole server went offline !
Please give us a way to massively-activate Wordfence with:
– delete tables and previous saved content
– specific token or options
Hi @nokao,
After discussing this case further with my colleagues, it appears that it could actually be related to a known issue where Quick scans will sometimes run even when scans have been disabled.
Our development team is currently looking into it. For reference, the internal request is: #FB6311)
I have 250 websites doing Scans in loop,
killing our servers performances ever 24 hours.
Where can I send you my full options / logs / debug ?
This is Wordfence -> Toola -> Cron copy+paste:
Cron Jobs
Fri, 01 Dec 2017 10:18:48 +0000 wordfence_hourly_cron
Fri, 01 Dec 2017 12:20:00 +0000 wordfence_start_scheduled_scan
Fri, 01 Dec 2017 13:10:00 +0000 wordfence_start_scheduled_scan
Fri, 01 Dec 2017 15:53:16 +0000 wp_scheduled_auto_draft_delete
Fri, 01 Dec 2017 16:10:55 +0000 wp_version_check
Fri, 01 Dec 2017 16:10:55 +0000 wp_update_plugins
Fri, 01 Dec 2017 16:10:55 +0000 wp_update_themes
Fri, 01 Dec 2017 16:13:03 +0000 wp_scheduled_delete
Fri, 01 Dec 2017 20:18:48 +0000 wordfence_daily_cron
Mon, 04 Dec 2017 12:20:00 +0000 wordfence_start_scheduled_scan
Mon, 04 Dec 2017 13:10:00 +0000 wordfence_start_scheduled_scan
Mon, 04 Dec 2017 15:00:00 +0000 wordfence_email_activity_report
Thu, 07 Dec 2017 12:20:00 +0000 wordfence_start_scheduled_scan
I updated Wordfence,
Scanning is DISABLED,
yet I have infinite cron scheduling loops.
However,
I think that you should prompt to schedule a scan after plugin activation,
rather than forcing anyone who activate your plugin to do it.
I love Wordfence but I use it in another way, I don’t want scans expecially scheduled ones !
It’s a month we are under DDoS attack by ourselves and Wordfence …
We are abandoning your plugin. Keep us updated on bugfixes.
Can you please specify the URL where you’re discussing bug #FB6311 ?
We could help supporting developement team or giving access to our data.
Bye,
Alvise
I checked/discovered with WP Crontrol,
that every time I save Wordfence options,
1 wordfence_start_scheduled_scan appear in the cron table.
Even if “Enable automatic scheduled scans” = Disable
Why ?
Can you kindly explain me where you are discussing this problem ?
I would like to help. It’s URGENT.
I repeat: we are under severe attack by Wordfence, we are self-Dossing ourselves with your plugin.
Our 3 servers reduced their capacity by 80% because of daily, buggy loopy Wordfence Scans.
I am receiving 1800 emails / day about your scans on 300 websites.
No more answers ?
To who else this happens ?
Why ?
Moderator
Jan Dembowski
(@jdembowski)
Forum Moderator and Brute Squad
@nokao I’ve archived your identical topics, please do not create multiple topics for the same thing.
The plugin author’s have replied to you and explained. You’re making identical topics about the same thing isn’t helping or useful.
@jdembowski : please tell me where I can continue this discussion.
It seems you closed this for public view:
https://wordpress.org/support/topic/wordfence-behaviour-is-dangerous-scheduled-scans-on-by-default-pay-to-stop/#post-9884741
And I think this is a mistake.
At least I could have saved it’s content for internal use, I collected there a lot of useful informations for us and for the plugin owner.
The problem is not solved,
the plugin owner declared that he can’t assist us because we don’t pay for the Pro version,
but the problem occurs with the Free version of the plugin that is in your official repository.
I still think this problem may become a lot bigger in the future,
and I think many websites are experiencing this problem without still knowing it.
-
This reply was modified 6 years, 2 months ago by
ELAN42///.
-
This reply was modified 6 years, 2 months ago by ELAN42///.
