FYI: BackWPup conflict with Automattic plugin WP-Cron Control

  • Resolved Caleb

    (@crudhunter)


    8 years, 2 months ago

    Consistent/reproducible issue when pressing “Run now”..
    Scheduled jobs work fine, but when starting a job manually it hangs for a while, and then comes out with the famous “Job $s has started, but not responded for 10 seconds.” message..

    Checking the information link, I see the “Server Self Connect” status has the complaint “Not expected HTTP response:” with the HTTP content shown as “invalid secret string”.

    Checking around the WP code, I notice the following problem you might wanna remember or even fix as others might see it..

    Issue:

    “invalid secret string” is a response from the WP-Cron system, stating that the secret key for the back call to the server is using an invalid “secret”.

    As it turns out, this problem is caused because I have the plugin “WP-Cron Control” installed..

    One of the things “WP-Cron Control” does is mess with the secret key setup. For example, you can set a common secret key across a multi-site installation to be used on all sub-sites.. (The “Run now” failure is consistent, whether you use this feature or not.)

    As a test, I disabled the “WP-Cron Control” plugin, and BackWPUp’s “Run now” immediately started working. As in, the “secret key” used was suddenly deemed correct.

    Re-enable WP-Cron Control, and it fails again. Consistently.

    My 2-minute check around the code bases did not reveal 100% which plugin should actually be “blamed” and fixed for the conflict and failure. ??
    But since your’s is the one failing, you get the issue to play with for now. ??

Viewing 2 replies - 1 through 2 (of 2 total)
  • elseyadcock

    (@elseyadcock)

    If you are using WP-Cron Control it has a secret string to use in your cron script. You need to get the secret string used in WP-Cron Control then go to BackWPup Settings -> Network tab and select Query argument from the drop-down list for Authentication method. Then add the secret string in the Query arg key=value field. Save and your info page should indicate everything is OK. Hopefully. It worked for me.

    Thread Starter Caleb

    (@crudhunter)

    @elseyadcock, Yes, that is the solution..
    I did that later on, after looking at the code. Worked fine.
    My mistake that I forgot to update this FYI. Sorry.

    Maybe just adding a better error message or documentation pointer that people will understand would be a solution. ??

    Or, now that there is a “record” in these forums. ??

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘FYI: BackWPup conflict with Automattic plugin WP-Cron Control’ is closed to new replies.