• Resolved lizzyh

    (@lizzyh)


    Hi.
    This message came up under Live trafic:
    Scan Engine Error: Wordfence could not start a scan because the cron key does not match the saved key. Saved: 4d600b80576a880dbd14ea4 Sent: da3ff2f87743d12a250bb1 Current unexploded: 1455885349,4d600b80576a880dbd14ea4

    What’s the problem?

    Thanks,
    Anders

    https://wordpress.org/plugins/wordfence/

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author WFMattR

    (@wfmattr)

    Anders,

    Near the bottom of the Wordfence options page, turn on “Disable config caching,” and save the options. On some hosts, the cache gets “stuck” and this should take care of it. Let us know if you have any other questions.

    -Matt R

    rodgonz

    (@rodgonz)

    Hi!

    Same problem as @lizzyh, tried solution of @wfmattr, still not working!

    What can be done?

    Thx!

    Plugin Author WFMattR

    (@wfmattr)

    @rodgonz: If the message still appears after attempting a new scan with config caching disabled, it is usually an issue on the server, or a problem with some other caching. If you’re using a “database cache” in another WordPress plugin, try disabling that.

    If you still have trouble and need more details, please make a new post using the form at the bottom of the Wordfence forum here. (The wordpress.org forum rules ask us to keep each person’s issues separate, and it also helps us keep track of open issues, so no one gets skipped when posts start getting longer.) Thanks!

    -Matt R

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Wordfence Live activity’ is closed to new replies.